Search Results

Hello, Unfortunately, we do not have experience debugging with the NXP S32 Development Studio either. Below is a link to a list of supported IDEs and instructions on how to set them up for debugging with Jlink: Supported IDEs Best regards, Simon

Hello, I looked at your project and noticed that you are using the STM32F446ZC. The STM32F446ZC has a flash memory range from 0x8000000 to 0x803FFFF (256KB). This means that the address 0x8060000 you are trying to program is not valid. This might explain why the Jlink is not programming the data. However, I don't understand why the Stlink is able to flash this data correctly. Could it be that you meant to select the STM32F446xE, which has 512KB of flash memory? Best regards, Simon

Hello, I apologize if I have expressed myself unclearly. SuppressGUI is an J-link Command string not an command for the J-Link Commander. However, you can execute J-link Command string in the commander with the exec command, so in your case you need to write: exec SuppressGUI. Not only SuppressGUI. wiki.segger.com/J-Link_Command…ng_J-Link_Command_Strings Best regards, Simon

Hello, You can change the reset strategy used by the J-Link in the J-Link Commander with SetResetType. In your case, to switch to a software reset, it should be: exec SetResetType = 6 For more information, please refer to: SetResetType J-Link Reset Strategies Best regards, Simon

Hello, Try exec SuppressGUI in your .jlink file. Best regards, Simon

Hello, I noticed that you are using different interfaces with the GDB-Server: SWD, and with Ozone: JTAG. Could you please try selecting the SWD interface in Ozone? Best regards, Simon

Hello, You can prevent such popups with the command string SuppressGUI. For more details, please refer to the SuppressGUI Command String. Best regards, Simon

Hello, Thank you for reaching out. Does the problem also occur with the latest version, V7.96k? If the problem still occurs, could you please create and send one J-Link log file of the failing scenario as well as one of the good case? How to enable: Enable J-Link Log File Best regards, Simon

Hello, On startup, the GDB Server connects with our update server to check for updates. Best regards, Simon

Hello, The -delrange command only affects the data file and not the chip itself. To delete only a specific sector via the J-Flash command line application, follow these steps: 1. Select the sectors in the J-Flash GUI application (currently not possible via commands). J-Flash Flash Settings 2. Save the project. 3. Open the project via the J-Flash command line application with -openprj <FILENAME>. 4. Use the -erasesectors command.Only the previously selected sectors are erased. For more details, p…

Hello, The cause of the issue you are referring to is that the J-Link erases the whole sector before programming it. To resolve this issue, you can either: 1. Combine the data of the two .elf files into one data file and then flash this single file.Or 2. Set the RMW threshold to 64KB via "exec SetFlashDLNoRMWThreshold 0x10000", then program the larger .elf file first and the smaller one afterward. For more details, please refer to SetFlashDLNoRMWThreshold . Best regards, Simon

Hello, You can check the JTAG functionality by connecting to the MCU via the J-Link Commander: SEGGER J-Link Commander The available device names we have for the MIMX8ML8 family are: - MIMX8ML8_A53_0 - MIMX8ML8_A53_1 - MIMX8ML8_A53_2 - MIMX8ML8_A53_3 Best regards, Simon

Hello, Quote from mastupristi: “Reads take place byte by byte ” I took a quick look at the sources of our flashloader and did not see any issues that could lead to this. Quote from mastupristi: “At the end QE bit remains at 0 ” Our flashloaders restore the previous state of the MCU, so if the QE was set to 0 before the J-Link operation, it is set back to 0 afterward. Regarding the dummy cycles and address bytes, the J-Link will use the factory default. Quote from mastupristi: “Is it possible to …

Hello, Unfortunately, we also have no experience using the NXP S32 Development Studio, so we recommend getting in touch with NXP about this. Here you can find a list of supported IDEs and how to use them with J-Link: wiki.segger.com/Supported_IDEs Best regards, Simon

Hello, I just updated the wiki accordingly. The description of the command can be found here: wiki.segger.com/J-Link_Command_Strings#SetSkipL1Verify Best regards, Simon

Hello, As long as the reset pin of the EDU Mini is correctly connected to the TRST of the evaluation board, you should be able to pull the TRST line high. Best regards, Simon

Hello, The regs command is only supported for the ARMv8 AArch32 architecture. Since the Cortex-A55 is ARMv8 AArch64, GDB responds with "unsupported CPU." Best regards, Simon

Hello, When a new version of a J-Link is published, the old version usually continues receiving firmware updates for a few years. After this life cycle, the firmware updates are no longer developed, and therefore you can't update them anymore. You can find the changelog of our firmware here: Release Notes - J-Link Best regards, Simon

Hello, I tried to reproduce the behavior with the J-Link Commander without success. Did you make sure that the file "seggerdemo.bin" exists at the path "C:\demo"? Here you can find more information and examples of the loadfile command: wiki.segger.com/J-Link_Commander#LoadFile Best regards, Simon

Hello, The device is already supported. See the link below: SEGGER Supported Devices - ST Best regards, Simon