Search Results

Search results 1-20 of 38.

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

  • 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…

  • Quote from v01d: “But it is a little odd, as I don't think I ever saw other such tool which would loose these breakpoints.” IAR seem to try to keep it, Green Hills in the default setting would clear all breakpoints. In some situations it may look a easy, in others it may be very hard for a program: function renamed and line moved, or code moved unchanged to a sub function.

  • Maybe it is a valid instruction, but maybe not for the active processor mode: privilege; thumb/arm mode..

  • Hello, for trying to get the FCR4 scripts working with J-Link software V632c, i found that the code is compiled or interpreted wrong. It can observed that when using function results directly, garbage is returned. Workaround seem to be using temporary variables for the results. C Source Code (98 lines) output on V612i is: Source Code (17 lines) output on V632c is: Source Code (17 lines)

  • For the __int64 removal [SOLVED] Error while compiling J-Link script file, the *.JlinkScript files for FCR4 and others have been changed. example: JLink_V612i\Samples\JFlash\ProjectFiles\Spansion\MB9DF125.JLinkScript C Source Code (13 lines) JLink_V632c\Samples\JFlash\ProjectFiles\Spansion\MB9DF125.JLinkScript C Source Code (15 lines) however, this make the script no longer working. case 6.12i: --- FSEU script --- OK: Debug port powered up ... --- FSEU script --- MCU reset --- FSEU script --- OK…

  • Hello, is the Cypress Traveo family of devices like the S6J326CK planned to be supported regarding internal flash loading by debuggers, J-Link commander and J-Flash? Currently we got sample projects with quite complicated GHS and IAR scripts+flashloaders.

  • RAMCode

    Veit_Kannegieser - - J-Link/Flasher related

    Post

    tried again with a code jump table of Source Code (12 lines) Output of JFlash: Brainfuck Source Code (17 lines) corresponding J-Link log file Source Code (23 lines) So it seems that assembler code is needed to prepare a stack and and call a C function with registers in R0/R1/R2.. Also in the example is no implementation of RAM check. Newest file in RAMCode_SDK.zip is readme.txt from 2010-08-31. Is there a newer RAMCode SDK that has an example of for example RAMCODE_CMD_CHECKRAM implemented?

  • try Source Code (1 line) I think the change was to know what special handling is needed befor probing for connection. The config option/command should not apply to SWD?