SEGGER - Alex Administrator

Hi, If I am not mistaken, the SAME54 has this „reset extension“ feature which means that the chip samples SWCLK and/or SWDIO on reset release (not only reset pin release but also WDT reset etc.) and if they have a certain level, the application is…

According to the log file, connecting to the core seems to work fine. No idea why the chips throws an error when J-Link triggers an erase… To analyze that, we would need to know what has been programmed into the flash (e.g. you could use the…

Hi, I assume that you have connected the reset pin of the MCU to the reset pin of J-Link, correct? Without this, connect under reset will not work. In general, it is not smart to disable the debug pins while still developing on a device… Most MCUs do…

What J-Flash shows there is the max. size it supports for the flash bank. The actual flash + size is detected at runtime. Note that the pinout from the NXP eval board is assumed, so your flash has to be connected in the same way, to make things working…

How about to get to the vendor? It is a feature specified by ARM: developer.arm.com/documentatio…ulti-drop-support?lang=en developer.arm.com/documentation/ka001195/latest The tricky part: It is an option, the device vendor MAY license, so you need to…

We will close this thread then. PS: No, there was never any heuristics be used in older versions, to detect pinout. There was a fixed pinout assumed. BR Alex

1) The screenshot from the wiki article IS from the control panel. I NEVER wrote that the screenshot shows the settings for YOUR actual device. It is a generic article, so SOME device was used to create the screenshot. So your statement is just…

The forum language is English. Can you please rephrase your post in English language?

Hi, ELF files generated by Greenhills are not supported by Ozone and neither they are by J-Flash. They might work but no guarantees given. Reason is that Greenhills uses a proprietary format (at least for the debug info) by default but even with the…

Yes, it is available. The only option for loader selection in EWARM is the J-Link control panel: wiki.segger.com/J-Link_Multipl…#J-Link_web_control_panel

This chip is currently not supported by J-Link. You may add support on your own: wiki.segger.com/dsk

segger.com/products/debug-probes/j-link/tools/j-run/ wiki.segger.com/J-Run Or you use the SDK and write all the semihosting logic on your own and integrate it directly in your test environment.

It does not end abruptly. Disabling the IAR flash loader is all that needs to be done. The one from J-Link will automatically take over. There is NO extra menu in IAR to „enable“ the J-Link flash loader…

wiki.segger.com/J-Link_Device_Support_Kit#DSK_availability If performance does not matter and you do not need examples + support, you may go with the CMSIS alternative that is also mentioned there.

@sharon Good to hear that you are up and running @mwb1100 It is not really an unusual requirement of "SEGGER's command line utility" but more a J-Flash specific thing. We are in the process of changing that to make it more standard but at the same time…