Monday, May 21st 2018, 5:16am UTC+2

You are not logged in.

  • Login
  • Register

Search results

Search results 1-20 of 24.

Friday, May 18th 2018, 6:20pm

Author: Veit_Kannegieser

IAR J-Link SAMA5D2 Undefined Instruction Exception

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

Thursday, May 17th 2018, 6:42pm

Author: Veit_Kannegieser

J-Link script compiler or interpreter errors

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/C++ Source code 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71...

Wednesday, May 16th 2018, 3:28pm

Author: Veit_Kannegieser

J-Link scripts for Cypress FCR4 no longer work

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/C++ Source code 1 2 3 4 5 6 7 8 9 10 11 12 13 unsigned int _WriteAPDPReg(unsigned int u32RegIndex, unsigned int u32Data) { unsigned __int64 u64Value; // We need 35 bits: 32 data, 2 bit addr, 1 bit RnW unsigned int u32BitPosData; // Write 35 bits (32 bits data, 2 bits addr, 1 bit R...

Tuesday, March 15th 2016, 6:08pm

Author: Veit_Kannegieser

Cypress S6J326CK support?

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.

Monday, January 25th 2016, 7:20pm

Author: Veit_Kannegieser

RAMCode

tried again with a code jump table of Source code 1 2 3 4 5 6 7 8 9 10 11 12 _RAMCode_Breakpoint: BKPT #0 RAMCODE_ASM_CHECKRAM: BKPT #0 ;//b RAMCODE_ASM_CHECKRAM RAMCODE_ASM_CHECKBLANK: b RAMCODE_ASM_CHECKBLANK RAMCODE_ASM_CALCCRC: b RAMCODE_ASM_CALCCRC RAMCODE_ASM_GETDESC: b RAMCODE_ASM_GETDESC RAMCODE_ASM_READ: b RAMCODE_ASM_READ RAMCODE_ASM_PROGRAM: b RAMCODE_ASM_PROGRAM RAMCODE_ASM_ERASE: b RAMCODE_ASM_ERASE RAMCODE_ASM_PREPARE: b RAMCODE_ASM_PREPARE RAMCODE_ASM_RESTORE: b RAMCODE_ASM_RESTOR...

Saturday, January 16th 2016, 10:20pm

Author: Veit_Kannegieser

[SOLVED] V5.10g - Type "connect" to establish a target connection - new

try Source code 1 JLinkExe -if swd -device nrf51 -AutoConnect 1 -CommanderScript (your_file_name.jlink) 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?

Wednesday, January 13th 2016, 9:41pm

Author: Veit_Kannegieser

RAMCode

Hello Erik, the Ramcode SDK here has in the linker configuration file: Source code 1 place at address mem:0x00000000 { readonly section .intvec }; where the .intvec symbol is implemented in Specific_ARM_ASM_LE.o, when looking with an disassembler looks like: Source code 1 2 3 4 5 6 7 8 9 10 11 12 .intvec:00000000 ; Segment type: Pure code .intvec:00000000 AREA .intvec, CODE, READWRITE .intvec:00000000 CODE32 .intvec:00000000 EXPORT _RAMCode_Entry .intvec:00000000 _RAMCode_Entry DCW FLASH_GetDesc...

Wednesday, January 13th 2016, 7:36pm

Author: Veit_Kannegieser

[SOLVED] Target Device settings lists Fujitsu MB9EF226 as having no flash/RAM

I have installed JLink_V510g, and Source code 1 JLink.exe -If JTAG -Speed 25000 -Device MB9EF226 -JTAGConf 0,0 -AutoConnect 1 -JLinkScriptFile .... -CommanderScript ... works very well now, and does no longer prompt for any device or JTAG position. Many Thanks!

Monday, December 14th 2015, 8:28pm

Author: Veit_Kannegieser

[SOLVED] Target Device settings lists Fujitsu MB9EF226 as having no flash/RAM

no not solved. It seems i can not avoid the JTAGConf> prompt, even when doing "config 0,0". Source code 1 2 3 4 5 6 si JTAG speed 25000 exec Device CORTEX-.. config 0,0 Device CORTEX-.. connect results in Source code 1 2 3 4 Cortex-.. identified. Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect JTAGConf>

Thursday, December 10th 2015, 4:13pm

Author: Veit_Kannegieser

[SOLVED] Target Device settings lists Fujitsu MB9EF226 as having no flash/RAM

Hello Nikla, thanks for the explanation. Official support for this Titan device is very welcome. So far there were no problems with the internal flash programming. The question just showed up with J-Link 5.10+ software because our scripts did not give the device in the expected order and the "Unspecified" -> please select.. appeared, both with MB9DF125 and MB9EF226. When beeing in "C:\Program Files\SEGGER\JLink_V510c" and running Source code 1 2 3 4 5 6 JLink.exe -If JTAG -Speed 25000 -Device MB...

Tuesday, December 8th 2015, 8:51pm

Author: Veit_Kannegieser

RAMCode

We also got the Ramcode SDK free of charge (=without support), and somehow the 'rules' used by SDK do not match what can be seen by JFlash. when using Cortex R4/A9 processors. For example i would expect that JFlash first sets the PC to where FLASH_Prepare offset points to. Seen here is that PC = RAM start+2.

Wednesday, November 11th 2015, 2:48pm

Author: Veit_Kannegieser

[SOLVED] J-Link debugger: option to use J-Link settings file

Hello Alex, yes the exec function would be helpful. Now i have added SEGGER SystemView sources into our Cortex-R4 (Fujitsu..) based board with an Microsar(Vector) OSEK. Without an script like C:\Program Files\SEGGER\JLink_V502i\Samples\JFlash\ProjectFiles\Fujitsu\MB9DF125.JLinkScript SystemViewer.exe has no way to connect. Temporary workaround is to use j-link commander in parallel. So please add a settings file also to SystemViewer.

Thursday, November 5th 2015, 4:08pm

Author: Veit_Kannegieser

[SOLVED] J-Link debugger: option to use J-Link settings file

Hello, it woud be nice to the J-Link Debugger to pass a settings file name (.jlink) instead of "Not specified" in the J-Link control panel. Possible uses - the .jlink file can reference a JLinkScript needed for the Fujitsu/Spansion/Cypress FCR4 - the .jlink can contain settings for CFI flash (open problem) suggestion would be path and name of the .jdebug project file, just the extension changed to .jlink.

Thursday, October 15th 2015, 9:04pm

Author: Veit_Kannegieser

[SOLVED] J-Link Debugger crashes when loading GHS .elf file

Hello Niklas, i have asked our Green Hills support, and the interfaces are not public. Also from support point - who is in responsible in case of problems: user, GHS, Segger, chip manufacturer,.. and i guess also from buisiness view there is no reason for GHS.

Sunday, October 11th 2015, 1:25pm

Author: Veit_Kannegieser

[SOLVED] J-Link Debugger crashes when loading GHS .elf file

One more comment: the GHS compiler and IDE works with the GHS probes (price it a lot higher then a J-Link) and you need a license to use the probes. GHS multi has support for other probes too (MACRAIGOR, HP), but RDI support seem to be gone now. The interface of the multi debug probe interface (like rtserv.exe) is not public documented. Would be a dream to have GHS multi working with J-Link!

Sunday, October 11th 2015, 1:17pm

Author: Veit_Kannegieser

[SOLVED] J-Link Debugger crashes when loading GHS .elf file

the P2VAR and similar macros come from the AUTOSAR world, it is resolved in an compiler abstraction header and P2VAR(uint32, AUTOMATIC, FLS_APPL_DATA) should result in uint32 * possibly in data section defined by FLS_APPL_DATA, which i guess as a flash driver variable. We use GHS and IAR and i had to write tools to convert GHS compiled obect files to be linkable and running with IAR. My understanding is that GHS has a different opionion about reloactions, ABI markup..

Wednesday, September 23rd 2015, 12:47pm

Author: Veit_Kannegieser

J-Link commander CFI Flash

Tried yesterday with 5.02d, and after some playing with the J-Link Control panel "Override device selection"..., page settings i found that the changes are not persistent for next call of jlink.exe, i added the -SettingsFile bla.jlink to the command line. This alone does not help, however when doing any change, like "Modify breakpoints during execution" to "Do not allow", the changes done by commands exec setcfiflash 0xE0000000 - 0xE1FFFFFF exec setworkram 0x00100000 - 0x00107FFF result in bla.j...

Tuesday, September 8th 2015, 6:30pm

Author: Veit_Kannegieser

Flashloader, Flash visible twice

Hello Erik, Quoted from "SEGGER - Erik" Can you please specify what target device you are using? We are using the "Atlas-L" MB9DF125 and "Titan" MB9EF226 currently. Quoted Wouldn't be changing the linker file an option for you? This would still allow you to use the SEGGER flash loader. We changed from AXI to to tighly coupled memory interface in the hope running with with zero waits, but of course we can change that for a debug configuration. Quoted Anyhow, we will check if we can add the mirror...