![]() ![]() I had cases where the RTT was assuming the wrong RAM memory map. maybe the RTT fails to detect that signatur. does your SEGGER RTT variable have the same string at the beginning as in my screenshot? Because the RTT is checking for that signature (and not for the variable name). 81, buy best ft2232d jtag usb rv debugger for lichee tang risc-v. In any case, make sure you are compiling and using and executing all the same SEGGER versions. This seems fairly clear to me at present, but work on that is on hold to start with. SEGGER recently changed the installation procedure to combine everything into a single installation folder, so this might be the issue. Its important to note that the download will not include the bootloader. What I have seen (at least on Windows) is the problem of mixing different J-Link versions. This can have different reasons as for example the application does disable the debug interface, re-configures the debug pins, enters some kind of low-power-mode or the security of the device is activated. You might try to connect to your board with RTT from a Windows host to check if the problem is really on the Linux side. Check the quality of the debug signals using an oscilloscope After programming the target device, J-Link is no longer able to establish a connection. The IDE really has nothing to do with the RTT, except that the SEGGER_RTT variable might be optimized be the linker (which you confirm is not the case). Any other adapter will do the job as well, such as (for example) a CMSIS-DAP.I believe this is more a problem of Linux and SEGGER than MCUXpresso. If the J-Link is functional, you should see that the J-Link Commander reports USB connection O.K. I might have mentioned ST-Link more than a few times here, but that's just because they're very easy to get a hold of. First, verify that the connection between the J-Link and PC is functional and J-Link Commander can communicate with the J-Link successfully: Connect J-Link via USB to the PC. As long as they are Cortex-M with an SWD port (or JTAG for that matter), it'll work. You can use it to flash NXP, Nordic, Atmel, etc, etc. Oh, and in case you don't already know, the ST-Links (as all SWD DAPs) will work just fine with other vendors chips. Second: Their RTOS integration in the GDBserver is actually pretty convenient. ![]() First one: The time it takes to flash is slightly shorter, as they read out the flash, compare and then only writes the changed pages to flash. Right now, I can only find two good things to say about the Seggers (when they work). Hint: The SEGGER_RTT.c files have no atomic functions or locking in place. I would expect the break at main () to automatically bring up the C. As expected when opening a debug session the project builds and loads to the target, but the debugger does not display any C source files. As in, their logging-system _looses_ messages. I can build the project, but if I click on Debug (using the default Simplicity Studio Debugger configuration) the behavior is not correct. Some people get hung up on Seggers "RTT" functionality, which on a powerpoint level looks great. Even if you disregard the softwares lack of documentation, idiotic arguments to the commands (which the debugger could have figured out itself), and other idiosyncrasies, there's very, very little value-add to a JLink compared to a $20 ST-Link, or even a $2 clone of a ST-Link. At least the command-line stuff is, as I haven't tested their IDE integration. The hardware seems alright, but their software is utter crap. Yea, I've had the misfortune of recently being introduced to the Segger J-Links (not the EDU version, the bigger ones). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |