Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Panel | ||||
---|---|---|---|---|
| ||||
How to debug netX 90 application side with J-Link debug probe from SEGGER? |
Panel | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
Hilscher provides netX Studio CDT IDE (Integrated Development Environment) for customers for developing application software for the netX 90 SoC. The main goal is to provide an out-of-the-box working solution for building and debugging applications for the netX SoC. netX Studio CDT is provided to customers free of charge and aims to make it easy for them to evaluate netX as a platform for their custom designs. The software (https://kb.hilscher.com/display/NDT) and Documentation are available on Hilscher Knowledgebase(https://kb.hilscher.com/). SEGGER's J-Link supports a wide range of CPUs and is very popular with some netX customers. Since SEGGER added support for netX 90, which allows customers to use the tools from the J-Link Software and Documentation Pack and the Ozone J-Link Debugger, we provide here a step-by-step guide for debugging the netX 90 application side with J-Link. PrerequisitesPlease use J-Link Software and Documentation Pack v7.60 or later. The v7.60 release includes the following fixes for netX 90:
For use case B and use case C with an external SQI flash, please use J-Link Software and Documentation Pack v7.86c or later. The v7.86c release includes the following new feature for netX 90:
J-Link support in netX Studio CDTCurrently, netX Studio CDT supports debugging with J-Link in one of the following two ways:
Using J-Link with OpenOCDIn general, it is possible to use J-Link with OpenOCD, but it's not recommended due to the following main reason:
Please see further limitations and support from SEGGE: https://wiki.segger.com/OpenOCD Using J-Link with GDB ServernetX Studio CDT supports debugging with a different GDB server backend than OpenOCD, e.g. SEGGER J-Link GDB Server. (Please refer to the attached example project, which has ready-to-use batch scripts for programming the flash and starting the gdb server etc by calling the batch file in the Terminal of netX Studio CDT.) It's not recommended as well, since to use the full feature of J-Link Debugger, Ozone is supposed to be used. If you still want to use netX Studio CDT as a frontend, please note the following:
Using J-Link with J-Link Debugger (Ozone)Generally, debug elf file: 1. sdram 2. flash download manual. Before debugging, the netX 90 internal flash needs to be programmed with the required files. See Using J-Flash to set up the netX 90 internal flash above. Please refer to the project files "pns_simpleconfig_iflash.jdebug" and "pns_simpleconfig_sdram.jdebug" in the attached Ozone_example. References |
Panel | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...