SEGGER - Alex Administrator

It has been some time when I have had the UltraScale+ on my desk. Getting access to the Cortex-R5 on it was no fun...Never worked on the Cortex-A cores of that chip. (That time ago we did not even have support for the Cortex-A53) Quote from…

Hi, Quote from ddbug: “ The customer says they never had any issue with flashing. Just drop a file to it and it does its magic. ” If it works for your customer, I recommend to get in touch with them first, making sure that you are using identical…

Hi, You may want to try with the current version first, as your version of GDB Server is V4.98e which is from May 2015 and so already 7 years old... BR Alex

Hi, Your specific MCU may or may not provide memory-mapped special function register that allow identification of the particular device model etc. I recommend to get your hands on the J-Link SDK and add do a sequence like…

Hi, Hard to say what is going wrong without knowing your target device. SetupTarget() definitely looks wrong. The JLINK_MEM_Write() calls write memory *through* the core which actually halts the core before the write-call. So it is nonesense to halt…

Hi, This might be due to the fact that J-Link issues a reset when connecting to XMC4xx series devices: wiki.segger.com/XMC4xxx_series#Attach_to_running_application This reset causes the ROM bootloader of the device to run which might use certain RAM…

Hi, You are on your own here. Daisy-chaining with 2 targets that use different I/O voltages is out of spec. Both targets either need to use the same I/O voltage to make things work, you you need level shifters at several points. For example the CPLD…

Can you please send us the S/N of your J-Link? You can also send it via PM, if preferred.

Hi, Sorry to say but this thread makes zero sense so far... 1) *.S files are assembler files. They have *nothing* to do with J-Link but are of interest for the IDE (compiler + assembler) only. 2) J-Link does not even know about the existence of an *.S…

Hi Dan, Instead of hacking around in the J-Flash project file in a text editor (which can easily brick your project), you could have simply used the GUI to activate the J-Link script file usage... forum.segger.com/index.php/Att…120fd6f577e4663a20aea3f32…

Hi, A S/N is not designed to be changed by the user. Can you please send a screenshot of J-Link Commander when using the OB on your board? There are several different OBs out there, so this screenshot would give us an idea what OB you have and if there…

Customer already contacted us via ticket system & J-Link PLUS. Thread closed.

Hi, There is no official support from SEGGER at this point but you can add support on your own: wiki.segger.com/Open_Flashloader There may also be an open flash loader implementation from Indiemicro at this point, we simply do not know, as they could…

Hi, If you are entitled for support, we recommend to go through the regular support channel, as there is no guarantee to receive any answer from SEGGER employees here in the forum. We only guarantee that our flash loaders are able to program the flash…

Just to be precise / correct on Fabian‘s latest statement: Most RISC-V cores implement the short connect sequence. The short sequence is NOT standard compliant. The long sequence is standard compliant. Therefore, the long one is used by default, if…

The Commander is more a getting started / verification utility for supported cores. What you are probably looking for is JTAGLoad: wiki.segger.com/JTAGLoad It‘s part of the J-Link software package.