• State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 22 subscribers
  • Views 1638 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

Keil J-tag Automatically Generated ini Syntax Error

Dolphindalt

Hello kind forum user,

I am trying to debug an ADUCM355 over a J-link using serial wire debug in Keil. The following is produced in the console.

Is the debugging failing due to the syntax error in the JLinkSettings.ini file? This file was generated by the IDE. Any work arounds for this?

Parents
  • 0 Arm Employee Badge in reply to Dolphindalt

    I can't tell you why this "error 65: access violation at 0xFFFFFFF4" comes from. Did you locate any const data of your application to this address?

    However, I see some strange settings in your screen captures:

    • You wrote that you use a ADUCM355. This device usually has a 128K Flash. Why did you select the Flash algorithm for a ADUCM356 with twice the size (256K)?
    • You must have corrected the Address Range of the Flash algorithm. It states a size of 256, but the address range is set to 0x00000000 - 0x0001FFFF (which is 128K)
    • You selected 'Do not Erase' in your first dialog. You usually need to erase a Flash before you re-program it.

    Unfortunately, I don't have such a board to make some tests.

Reply
  • 0 Arm Employee Badge in reply to Dolphindalt

    I can't tell you why this "error 65: access violation at 0xFFFFFFF4" comes from. Did you locate any const data of your application to this address?

    However, I see some strange settings in your screen captures:

    • You wrote that you use a ADUCM355. This device usually has a 128K Flash. Why did you select the Flash algorithm for a ADUCM356 with twice the size (256K)?
    • You must have corrected the Address Range of the Flash algorithm. It states a size of 256, but the address range is set to 0x00000000 - 0x0001FFFF (which is 128K)
    • You selected 'Do not Erase' in your first dialog. You usually need to erase a Flash before you re-program it.

    Unfortunately, I don't have such a board to make some tests.

Children
No data