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?
The µVision IDE does not generate the JLinkSettings.ini file. This file must have been generated by the J-Link driver itself or maybe you used a J-Link commander from Segger. I would just delete this file and see what happens. This file will be re-generated next time you use J-Link.
Did ou select the right Flash programming algorithm in uVision? You can see that the Flash 'Erase' failed.
Deleting the JLink settings file seems to have helped. Now I get the following error below.
Here are my flashing settings. Do these look correct?
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:
Unfortunately, I don't have such a board to make some tests.
It sounds like you are using this boardwww.keil.arm.com/.../
There are CMSIS-PACK examples for the ADUCCM355 Series. I would test one of those examples and see if it works better for you.
Open the Pack installer, C:\Keil_v5\uv4\PackInstaller.exe
- On the top left of the window, for "Search", type "ADUCCM355" - the list below gets filtered. - Select the device (entry with a green icon) from the list below – on the right side of the dialog updates with Software Packs relevant to this device.- For the "Packs" tab, install the AnalogDevices:ADUCCM355_DFP pack (if necessary).- On the top right of the screen, select the yellow "Examples" tab.- On the "M355_Flash(Eval-ADuCM355QSPZ)" row, click the "copy" button - a dialog pops up.- Pick a directory, click both the check boxes, and press OK - a new Keil µVision session opens with the example.- Build the project, Connect a USB cable to the board and start the debugger.
======
This article might help with J-Link script files developer.arm.com/.../If so, this may be useful: wiki.segger.com/Analog_ADuCM355
Finally, on the Project -> Options For Target ->Debug tab, make sure the radio button "Use Simulator" is NOT selected.