• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 1562 views
  • Users 0 members are here
Options
Related
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

donwload program with ulink2

JeanMarc Rouxel

Hello,

I'm working on a luminary LM3s9b92 with Keil µVision4.
With the C1 revision of the part, I donwloaded my program with the "In-Circuit Debug Interface" board of the EKK-LM3S9B92 evaluation kit. I had no problem.

With the C3 revision, KEIL4 + EKK : impossible to program the part.

Now, since yesterday, I have a Keil Ulink2 Debug Adapter. With this and my version of µVision4 (4.12) : impossible to program the part.
I donwloaded the latest version (4.13a) of Keil yesterday.
Now, I can flash the part, but it remains some of questions:

in the Debug sheet of the "Cortex-M Target Driver Setup" and in the "Download Options" group :
- if "Verify Code Download" is unselected and "Download to Flash" is unselected too :I can donwload my program and debug it.

- if "Verify Code Download" is selected and "Download to Flash" is selected too :I can donwload my program but not debug it. Here is the error message : "Ulink - Cortex-M Error"
Memory Missmatch ! Address = 0x00000000 Value = 0x00 Expected = 0xC8

- if "Verify Code Download" is unselected and "Download to Flash" is selected : I can donwload my program and launch the debug but without breakpoints !

Any suggestions for these problems ?
Regards,
Jean-Marc Rouxel

Parents
  • 0 in reply to Dragi Pandeliev

    Hello,
    I had the same problem and after contacting the support, I got the following message:

    "Due to an errata item, Tempest C3 devices require special considerations when programming and
    debugging using JTAG or SWD. The debugger must be configured to use a core reset (VECTRESET)
    instead of a system reset (SYSRESETREQ). In addition, each peripheral block must be reset by the
    debugger. Refer to the chip errata description for full details.
    This document provides a work-around for current versions of Keil RVMDK. To use Tempest C3 devices,
    some target settings must be changed and a simple script added to the initialization process. Only use this
    process for ULINK debuggers. For Stellaris ICDI a DLL driver update is required (lmidk-agdi.dll).
    This work-around was tested with RealView MDK-ARM Version 4.11. A future RVMDK release will
    implement the workaround internally."

    If you have further problems in this case the best solution is to contact the support!

    Mike

Reply
  • 0 in reply to Dragi Pandeliev

    Hello,
    I had the same problem and after contacting the support, I got the following message:

    "Due to an errata item, Tempest C3 devices require special considerations when programming and
    debugging using JTAG or SWD. The debugger must be configured to use a core reset (VECTRESET)
    instead of a system reset (SYSRESETREQ). In addition, each peripheral block must be reset by the
    debugger. Refer to the chip errata description for full details.
    This document provides a work-around for current versions of Keil RVMDK. To use Tempest C3 devices,
    some target settings must be changed and a simple script added to the initialization process. Only use this
    process for ULINK debuggers. For Stellaris ICDI a DLL driver update is required (lmidk-agdi.dll).
    This work-around was tested with RealView MDK-ARM Version 4.11. A future RVMDK release will
    implement the workaround internally."

    If you have further problems in this case the best solution is to contact the support!

    Mike

Children