SukkoPera wrote: 01 Dec 2018 23:03
Actually I have tf530_2018_11_17_beta.
The last change i made was to adjust the delays so that 25Mhz worked. If you're past 33Mhz i recommend giving the 4th Nov a go.
Could you start a thread in the TF530 section and we can track this type of issue and i'll see if any clues pop up in the discussion?
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
So unfortunately I was able to reproduce this issue now.
It is very insidious, while memcheck doesn't find any issues with the RAM, SysTest fails during round 1.4 in the 0xd0000-0xd7ffff range. So it seems it only manifests itself in certain conditions. And yes, certain WHDLoad games fail but not all, probably depending if they are allocating data in the incriminating region. I missed all of this before, but now I can confirm it... I did all this at 25 mhz using the latest firmware.
The memory itself is identified correctly, allocated between $C00000-$D7FFFF.
alenppc wrote: 01 Dec 2018 23:14
So unfortunately I was able to reproduce this issue now.
It is very insidious, while memcheck doesn't find any issues with the RAM, SysTest fails during round 1.4 in the 0xd0000-0xd7ffff range. So it seems it only manifests itself in certain conditions. And yes, certain WHDLoad games fail but not all, probably depending if they are allocating data in the incriminating region. I missed all of this before, but now I can confirm it... I did all this at 25 mhz using the latest firmware.
The memory itself is identified correctly, allocated between $C00000-$D7FFFF.
25Mhz is the low end of the operating range for the TF530. What is your CPU rated to?
If all bits fail then there is definitely something funny going on.
I wonder if AlenPPC can reproduce with SysTest. I know he prefers MemCheck1.2
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
alenppc wrote: 01 Dec 2018 23:14
So unfortunately I was able to reproduce this issue now.
It is very insidious, while memcheck doesn't find any issues with the RAM, SysTest fails during round 1.4 in the 0xd0000-0xd7ffff range. So it seems it only manifests itself in certain conditions. And yes, certain WHDLoad games fail but not all, probably depending if they are allocating data in the incriminating region. I missed all of this before, but now I can confirm it... I did all this at 25 mhz using the latest firmware.
The memory itself is identified correctly, allocated between $C00000-$D7FFFF.
25Mhz is the low end of the operating range for the TF530. What is your CPU rated to?
If all bits fail then there is definitely something funny going on.
I wonder if AlenPPC can reproduce with SysTest. I know he prefers MemCheck1.2
Hi Stephen, I was the one who wrote this :-)
I guess from now on I should check RAM with both memcheck AND SysTest as apparently they do different tests and catch different issues.
alenppc wrote: 02 Dec 2018 00:28
Hi Stephen, I was the one who wrote this :-)
I guess from now on I should check RAM with both memcheck AND SysTest as apparently they do different tests and catch different issues.
Blimey i think im going senile. Juggling too many things. Ok. If you're seeing this on the slow ram then i have an issue. Unfortunately no way to reproduce at my end.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Best thing for SukkoPera to send you a working expansion board - I meant to do this but then a batch of boards I ordered from JLCPCB turned up unusbale so I never managed to build it
I'd be happy to contribute to the development of this board, if you just need a PCB (and components) I can send it straight away, if you want an assembled board I will try to put one together today.
On the other hand, I think this can also remain as a reasonable limitation. 1 MB works, and more than that does not make much sense when you have fast ram anyway.
You do not have the required permissions to view the files attached to this post.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
