Search Results

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

Hello, Thank you for reaching out. At present, the data type you inquired about is not supported. We have added this to our Todo. However, as this is the first issue of its kind, we are unable to provide an estimated timeline for implementation. We appreciate your understanding. Best regards, Simon

Hello, Normally, J-Scope should be able to match the variable. I just checked myself and could not see any issues. For further investigation, could you please create a ticket for this issue: segger.com/support/technical-support/ The ticket should contain the following information: - Serial number of your J-Link - Used hardware - Software version used - Simplified example project - Detailed reproducer Once the issue is resolved, we will update this case accordingly. Best regards, Simon

Hello, I can not see any possible issues in your picture. For further investigation, could you please create a ticket for this issue: segger.com/support/technical-support/ The ticket should contain the following information: 1. Serial number of your J-Link 2. Used Hardware 3. Software Version used 4. Simplified example project to reproduce the issue Once the issue is resolved, we will update this case accordingly. Best regards, Simon

Hello, I am not able to see your screenshot. Could you please try to re-upload it? Best regards, Simon

Hello, Sorry for the delay in response. Thank you for your inquiry. Could you please create a ticket for this issue: segger.com/support/technical-support/ The ticket should contain the following information: - Serial number of your J-Link - Used Hardware - Software Version used - Description of the current state of this issue Once the issue is resolved, we will update the ticket accordingly. Best regards, Simon

Hello, Yes, we are currently working on supporting the ST STM32H7R/S series. However, we are not able to provide a specific timeframe at this moment. Best regards, Simon

Hello, I apologize for the delay in response. Did you follow the J-Scope RTT guide? You can find it here: J-Scope RTT Guide Best regards, Simon

Hi, Sorry for the delay in response. This issue has been fixed with version V7.96c. Best regards, Simon