Search Results

Is the 11th function on some special address? Try moving it by adding and calling other functions before it. Is the problem cache related? Disable instruction and data cache.

Hello, Quote from SEGGER - Nino: “This should be already possible for most setups. Just make sure your debug session is active before connecting with SystemView. ” having an active debug session, JLinkRTTViewer allows that option, and automatically reconnects, while SystemView at the same time does not. Quote from SEGGER - Nino: “The only setups where this will currently not work is where the Connect issued by SystemView might reset the target device as part of some target specific connect seque…

On connect, there seem to be a cosmetic problem, likely caused by copy&paste. Source Code (13 lines) Line 9 should likely read "Iterating through AP map to find APB-AP to use"

The ".icf" extension sounds like the IAR linker (ilinkarm.exe) file. you would see define region sysram_region = mem:[from sysram_start to sysram_end ]; place in sysram_region { block sysram_block, }; GCC (and Green Hills) use ".ld" file (linker definition). You would recognize them by seeing syntax like: MEMORY { RAM (wx) : ORIGIN = 0x00200000, LENGTH = 0x00010000 FLASH (rx) : ORIGIN = 0x00100000, LENGTH = 0x00040000 }

This is solved now. For the Cortex-A9 (Fujitsu/Socionext Emerald-L), the support for Japan confirmed that AHB-AP does not work, only Triton an later will do it correctly. For the Cortex-R4 (Fujitsu/Spansion/Cypress FCR4), problem was that the jlinkscript was developed before RTT was in mind. adding a ConfigTargetSettings function C Source Code (13 lines) and calling JLINK_ExecCommand("SetRTTSearchRanges 0x00000000 0x10000, 0x01A00000 0xC000, 0xB0638000 0x4000"); (for MB9DF125) or JLINK_ExecComma…

Hello Nino, Quote from SEGGER - Nino: “In the next release version of SystemView it is planned to have a CL option to set a specific JLinkScript file. ” Thank you, looking forward for it. Could you please also consider allowing using existing session like JLinkRTTViewer ( ) USB ( ) TCP/IP (*) Existing Session [v] Auto Reconnect

65 s sounds like 65536 milliseconds, so maybe wait for a 16 bit timer value that is in the past.

Hello, trying to get SystemView working on our targets, we are missing a way to specify a J-Link settings file (and following that a log file, and .JLinkScript file). Using a Default.JLinkScript in J-Link directory can help in emergencies, but it is impractical for multiple different targets. It found 'ProjectFile = ' inside SystemView.exe, but no way to trigger it. Alternatively, the connection dialog has a grayed out "Existing Session" radio button field. Having an Link Commander session open …

Yes, on recent versions there is a web interface, Windows versions have a Tray icon, allowing to open a control panel, on the first "General" page, Target interface kind and speed should be visible (and adjustable). Works only when connected. Any tool, including the Commander.

<localhost:19080/general.htm> in the target interface line?

So i guess the Ultra+ V1.2 implements "Legacy stop mode", the Ultra+ V4.4 can do "Stop mode", and in some situations it should be possible to use "Background mode" on that hardware.

Hello Nino, thank you for the examples. Source Code (6 lines) the zones work nicely. For the background memory access, i like to hint for a contradicting wiki link: wiki.segger.com/RTT I have measured background memory access. once i used an Ultra+ V1.2 (yes i know), and a Ultra+ V4.4. Enabled a periodic CAN message, and measured cylce time in CANoe. The script is Source Code (9 lines)so connect (includes a reset), wait 5 seconds read 256 KiB Flash using AHB wait 5 seconds read 256 KiB Flash usi…

for __aeabi_uldivmod, if there is no compiler option to inline the division operation, linking the standard library would likely not a problem, since that part is small, and does not need initialization.

Hello, any ideas? With question 1 i meant J-Link Manual (UM08001) V6.42f Quote from UM08001_JLink.pdf V6.42f: “ 3.2.1.22 mem The command reads memory from the target system. If necessary, the target CPU is halted in order to read memory. Syntax mem [<Zone>:]<Addr>, <NumBytes> (hex) Parameter Meaning Zone Name of memory zone to access. Addr Start address. Numbytes Number of bytes to read. Maximum is 0x100000 . Example mem 0, 100 ” The word "zone" is only used in chapters 3.2.1.22 to 3.2.1.51. No …

Hello, i am trying to get RTT working with our devices, which have Cortex-A9 and Cortex-R4 based controllers on them again. jlink.exe showsSource Code (4 lines) for both. Questions: 1) are the "zone"s of jlink.exe memory commands that zones?, if yes, how could the be used? for exampleSource Code (2 lines) but trying to use a zoneSource Code (11 lines) fails for the interesting cases. What is the correct syntax here? And examle in the manual would be nice too. 2) How to use background access? Sou…

could you please think about a breakpoint/semihosting function that hints for the RTT address?

Hello Nino, official support sounds very promising. Maybe would make it working more stable in Ozone and Embedded Studio too. Looking forward for this! We will likely keep some extended variant of the script to analyze field return cases, where JTAG debug access is not permitted, but read access to some registers like GPREG1. They indicate the protection/error state of the device, and the step in bootup and kind of exception, as a private extension.

Hello Nino, i should have added, that the issue is visible for different targets, i tried the MB9DF125, but using the script on a Corex-A9 gives same results. Currently a lot of J-Links devices here seem to have developed wings, i currently only have access to a J-Link Ultra+ V1.2 for my daily work.

It seem to be a compiler problem in JLinkARM.dll, i have looked with a debugger, and found that for the indirect function result usage it generates: Source Code (11 lines) so the result travels R0 -> R1 -> [SP] -> R12 -> push. however for direct case: Source Code (6 lines) the function result in R0 gets ignored and the string address gets pushed in both R11 and R12.

Hello Nino, thank you for the answers regarding __constant, and documentantion. Quote from SEGGER - Nino: “ In J-Link software version V6.32b a Scriptfile timeout has been added to make sure that Scriptfiles can't get stuck in endless loops as some get executed on J-Link hardware. Could you try the FCR4 script with V6.32a and see if the behaviour changes?” A script timeout is very reasonable. However in this case the problem is that the script should not reach the timeout. Reason for this is tha…