• State Not Answered
  • Locked Locked
  • Replies 0 replies
  • Subscribers 19 subscribers
  • Views 665 views
  • Users 0 members are here
Options
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Memory test utility port from Tasking to Keil

Pierre Roth

Hi,

We were using Tasking EDE and we moved to Keil µVision3 and I am trying to port (from tasking to keil) Memory test utility which can be found here : www.tasking.com/.../AN019-12_v8.ZIP

I made the code assemble but my target does not start anymore.

Some explanations :
A _mem_test assembly routine (see my memtest_keil.a66 which can be downloaded here : www.biarn.org/.../memtest_keil.a66 ) is called from startup code (see attached START167.a66, which can be downloaded here : www.biarn.org/.../START167.A66) to test RAM memory locations. When complete, this test stores the result code into _error_code and returns to startup normal path.

Note that _error_code will be later accessed from C (Since _error_code is declared as const in my C file, startup ram clear won't affect it).

What happens :
- If my _mem_test call is commented in my START167.a66 file, my target starts as usual without any problem.
- If I uncomment _mem_test call in my START167.a66 file, my target does not start or seems to reset.

I can't understand because I :
- added some push/pop before/after my mem_test call in my START167.a66
- Saved DDP2 register and configured it (DPP2 = 60) to access _error_code variable that I forced to be located at 0xF0000 (page 60)
- refreshed my software WDOG regularly in my mem_test routine

Perhaps, I forgot something...

My START167.A66 and memtest_keil.a66 files are available for download. For TASKING original files, you will find them here : www.tasking.com/.../AN019-12_v8.ZIP

Any help from an St10 expert will be appreciated...

Thanks for your time !

Pierre

PS : My platform is an ST10276 home based mainboard.

0