Search Results

Search results 1-20 of 1,000. There are more results available, please enhance your search parameters.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hello, Thank you for your inquiry. J-Link Commander is meant to be used as a troubleshooting and quick start tool. It is not supposed to be used for automation which is why some commands might not work as expected in this context. For automation purposes we recommend using the J-Link SDK and creating your custom application that fits your needs without workarounds: segger.com/products/debug-prob…nk/technology/j-link-sdk/ Regarding 1: There is no exec available for this, but it can be achieved wi…

  • Hello, Thank you for your inquiry. The Flash you are using is a CFI compatible Flash. In that case no extra Flash loader is needed. All you have to do is to init the memory controller of the MCIMX6 and configure J-Link to use that Flash as explained here: wiki.segger.com/CFI_Flash We recommend using a J-Link Plus or higher or a Flasher if you just need a programmer. Best regards, Nino

  • Hello Kevin, Thank you for your inquiry. Such an issue is not known to us. Does the example project from our Wiki work on your board? Did you follow all steps? It has been tested with the EVK so it should be working: wiki.segger.com/i.MXRT1050#QSPI_Flash_2 Did you power cycle the eval board after a failed session? iMX devices are prone to get stuck if something went wrong and only a power on reset clears the device from that state. Best regards, Nino

  • Hello, Thank you for your inquiry. The reported behaviour is reproducible and should be fixed with the next Ozone version. Best regards, Nino

  • Hello Paolo, Thank you for your inquiry. For the mass erase to work the reset pin of the target device must be connected to J-Link, is this the case on your hardware as well? Best regards, Nino

  • Hello, Thank you for your inquiry. The reported behaviour is reproducible. We are currently working on a fix. Sorry for any inconveniences caused. To stay up to date with Ozone releases you can subscribe here: segger.com/notification/subscribe.php?prodid=178,7 Best regards, Nino

  • Hello, Thank you for sharing the additional information. So as suspected reset is the issue. Are the reset lines shared between the devices or does each device have a separate reset? Is the M4 interconnected to the FPGAs in any other way? I assume that once reset is triggered for the TM4C either the FPGAs get reset which leads to follow up issues or the reset of the M4 triggers some behaviour in the FPGAs that is unexpected. Please understand that the reported issue most likely stems from your c…

  • Unlock for MSP432

    SEGGER - Nino - - J-Link/Flasher related

    Post

    Hello Germain, Thank you for your inquiry. The approach might work if the sequence is not timing dependent. We have a weak Pulldown on TMS on J-Link side so make sure TMS has a pullup on targetside so it stays high. Best regards, Nino

  • Hello, Quote from Sysmop226: “For opening and supporting a new device, I need a flash loader, which flash loader can I use? STMF7 flash loader would match? ” STM32F7 is not compatible to STM32H7. You would need to write a new Flash loader as explained in the Wiki. Or we can do it for your for NREs. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. We gave it a try on an BRD4181A Evalboard on a PCB4001 base board and everything is working as expected with J-Link software V6.50b. Could you try the latest J-Link software version? Could you check if you see the same behaviour with an eval board? If not we recommend using the eval board design as base for your custom board design. Best regards, Nino

  • Hello ranran, Thank you for your inquiry. The S29GL is currently not supported: segger.com/products/debug-prob…es/supported-spi-flashes/ We will try to get some chip samples and add them to the list. Just for clarification, which STM32 are you using exactly and is it on an eval board? For this setup to work a Flash loader must be available for the external interface of that MCU. If it is not available it must be created first via our open Flash loader interface: wiki.segger.com/Open_Flashloader#…

  • Hello, Thank you for your inquiry. How to port projects from ld to SEGGER Linker is explained in the ES user manual: studio.segger.com/segger_linker.htm Best regards, Nino

  • Hello, Thank you for your inquiry. The display change in the debug terminal is intended and will stay that way. There was a bug in the Nordic SDK which will be adjusted in future versions. See here for more information. [SOLVED] RTT Viewer not show log Best regards, Nino

  • CPU Support

    SEGGER - Nino - - SEGGER Embedded Studio related

    Post

    Hello Normand, Thank you for your inquiry. Current efforts to add support for the LS10xx series has been halted due to low demand and high complexity of the devices. Complexity here means that the LS10xx series differs from some usual ARM standard debug and programming implementations which would need a rework of parts of our generic modules that work fine for more than 9000 other target devices. However you can always add support for new devices yourself: wiki.segger.com/Open_Flashloader#Adding…

  • Hello, Thank you for your inquiry. We suggest contacting Nordic Semiconductor support in this regard as the Nordic SDK is not our software. Alternatively simply create a default Cortex-M sample and select the Nordic device without using the CPU package. Then a SEGGER Linker will be created automatically. Best regards, Nino

  • Hello, Quote from awneil: “except to say that it would be nice for the log file to be (optionally) timestamped ” This is already on our wish list. This thread will be closed now as requested. Best regards, Nino

  • Hello, Thank you for your inquiry. This is currently not available but we will add it to our wish list. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. What OS are you running on? Do you see the same behaviour on another OS? Could you provide an example project for reproduction purposes? Best regards, Nino

  • Hello Thomas, Thank you for your inquiry. The reported issue was reproducible. In other cases ES will jump to the corresponding error message and mark it red. This does not seem to be the case here. We will investigate further and see if such a case can be also displayed as usual. Sorry for the inconvenience caused. If you are looking for a more verbose output we recommend switching the output view from Tasks to Output. Best regards, Nino

  • Hello Thomas, Thank you for your inquiry. Such an issue is not known to us. The debugspeed of both debuggers should be identical as they use the same J-Link API. Do you see any unexpected CPU load spikes when debugging with ES? Does that happen with any project or only a specific one? Could you provide an example project for reproduction purposes? Best regards, Nino