Search Results

In addition i also often see this prompt ( attached): Probe led is red in this situation. Restarting debug session makes it work again.

Hi Fabian My setup is: Windows 10, Eclipse 2019-09 R (4.13.0). SEGGER V6.80 MIMXRT1064 on custom board Below is output from eclipse console, and og files for succesful and not successful attempt attached. SEGGER J-Link GDB Server V6.80b Command Line Version JLinkARM.dll V6.80b (DLL compiled Jun 5 2020 17:40:22) Command line: -select usb=600102036 -if swd -device MIMXRT1064xxx5A -endian little -speed 8000 -port 2331 -swoport 2332 -telnetport 2333 -vd -noir -localhostonly 1 -singlerun -strict -tim…

Hi I experience flash erase timeout approx. 50% of the times when i try to start debug session on a iMxRT1064 "internal" flash. Repeating the process normally results in success. Any idea why this happens. It used to work in the past but an update top either my setup og Jlink install seems to have affected the stability. Currently on SEGGER V6.80 Comparing flash [....................] Done. Erasing flash [....................] Done. ERROR: Timeout while erasing sectors, RAMCode did not respond i…

Hi Nino Thank you for the response. Since i want to enable SDRAM interface by writing to registers, i would expect that this need to be done after reset. ( Like you indicated in your answer to the linked thread) Do you instead suggest using Target Actions ( ie. Target.WriteU32) direct inside the jdebug script to perform SDRAM init, in the AfterReset handler ? Best regards Anders

I am trying to init SDRAM via jlinkscript as suggested in this thread: forum.segger.com/index.php/Thr…-jlinkscripts-with-Ozone/ However when i move the Project.SetJLinkScript("sdram_init.jlinkscript"); to "AfterReset", i get the following output "Project.SetJLinkScript: Command disabled" Script seems to be executed successfully during debug start if inserted into OnProjectLoad, but as target is reset afterwards this is not working Best regards Anders

Hi Nino Thank you for your answer. I was not able to read from the ST documentation that internal SRAM was not accessible by AHB. However if this is the case it might make sense if you change the default search range for this chip family to search in the DTCM area. I manage to setup the search range with the GDB server command "monitor exec SetRTTSearchRanges 0x20000000 0x1FFFF" and it now seem to work as expected. Best regards Anders

Hi I am struggling getting a stable RTT channel up and running on i STM32H7xx chip ( Cortex M7) The RTT block auto search function seems to search for the RTT block starting in address 0x24000000, but although the block is located in this area, it is not found by the server. If I configure the RTT block address manually in the Control Panel, it seems to be able to locate the block but no data is received. If I instead move the RTT block to DTCM area (starting at 0x20000000), and specify block ad…