that I am attempting to use an Econ Denebola board which has a
Cypress CX3 cpu with a JLink Pro debugger and eclipse debugging.
( Cypress CX3 =ARM926EJ-S core) (The Denebola board is powerd via an
external 5V power supply )
[1] The Denebola board has a number of boot modi which you can select via dip switches, if i select the default 'boot from spi flash' boot option i cannot connect with the debugger in Eclipse. The JLinkGDBServerCL console output says:
Display All
I did quite a lot of experimenting in this mode, one of the more strange observations is that if i start Jlink.exe from the command line, run 'connect' (a command which does not seem to have an explanation in the help for some reason ?) and enter ARM9/JTAG/autodetect/1000khz the connect fails. If i run 'usb' it also fails. But if I then press the reset button on the denebola board, and then run 'usb' again then it succeeds in connecting for a while, but if i keep entering 'i' i see that after a few seconds the connection fails again (note that connect never seems to works but usb does, what is the difference ??) .
Output:
Display All
[Here i reset the board]
Display All
Not sure what to think of that, is the connection 'unstable', does the chip makes itself 'unavailable' somehow over JTAG, ... ?
[2] With that last idea in mind i changed to bootmode to start in USB boot mode (so normal application SW will not be started). Using Jlink.exe with the steps above pressing i now the connection seems to be stable(r) when using the USB command (pressing i keeps working it seems).
And if I try connecting in Eclipse it also works a "little bit". By that i mean i reach the initial breakpoint in main, i can single step there, but as soon as i step over something or press Resume (F8), 95% of the time it will not work and i will get an error:
Starting target CPU...
ERROR: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 2) @ Off 0x5.
Any suggestions what might cause that?
In attachment screen shots of the eclipse debug attempt and the jlink
log file corresponding to that attempt....
Cypress CX3 cpu with a JLink Pro debugger and eclipse debugging.
( Cypress CX3 =ARM926EJ-S core) (The Denebola board is powerd via an
external 5V power supply )
[1] The Denebola board has a number of boot modi which you can select via dip switches, if i select the default 'boot from spi flash' boot option i cannot connect with the debugger in Eclipse. The JLinkGDBServerCL console output says:
Source Code
- SEGGER J-Link GDB Server V6.12g Command Line Version
- JLinkARM.dll V6.12g (DLL compiled Jan 27 2017 18:18:51)
- -----GDB Server start settings-----
- GDBInit file: none
- GDB Server Listening port: 2331
- SWO raw output listening port: 2332
- Terminal I/O
- port: 2333
- Accept remote connection: localhost only
- Generate logfile: off
- Verify download: on
- Init regs on
- start: on
- Silent mode: off
- Single run mode: on
- Target connection timeout: 0 ms
- ------J-Link related settings------
- J-Link Host interface: USB
- J-Link script: none
- J-Link settings file: none
- ------Target related settings------
- Target device: ARM9
- Target interface: JTAG
- Target interface speed: 1000kHz
- Target endian: little
- Connecting to J-Link...
- J-Link is connected.
- Firmware: J-Link Pro V4 compiled Jan 25 2017 15:46:53
- Hardware: V4.00
- S/N: 174300742
- Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
- Checking target voltage...
- Target voltage: 3.28 V
- Listening on TCP/IP port 2331
- Connecting to target...ERROR: Could not connect to target.
- Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
- Shutting down...
- Could not connect to target.
- Please check power, connection and settings.
I did quite a lot of experimenting in this mode, one of the more strange observations is that if i start Jlink.exe from the command line, run 'connect' (a command which does not seem to have an explanation in the help for some reason ?) and enter ARM9/JTAG/autodetect/1000khz the connect fails. If i run 'usb' it also fails. But if I then press the reset button on the denebola board, and then run 'usb' again then it succeeds in connecting for a while, but if i keep entering 'i' i see that after a few seconds the connection fails again (note that connect never seems to works but usb does, what is the difference ??) .
Output:
Source Code
- C:\Program Files (x86)\SEGGER\JLink_V612g>jlink
- SEGGER J-Link Commander V6.12g (Compiled Jan 27 2017 18:19:20)
- DLL version V6.12g, compiled Jan 27 2017 18:18:51
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link Pro V4 compiled Jan 25 2017 15:46:53
- Hardware version: V4.00
- S/N: 174300742
- License(s): RDI, FlashBP, FlashDL, JFlash, GDB
- IP-Addr: DHCP (no addr. received yet)
- VTref = 3.279V
- Type "connect" to establish a target connection, '?' for help
- J-Link>usb
- Disconnecting from J-Link...O.K.
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link Pro V4 compiled Jan 25 2017 15:46:53
- Hardware version: V4.00
- S/N: 174300742
- License(s): RDI, FlashBP, FlashDL, JFlash, GDB
- IP-Addr: DHCP (no addr. received yet)
- VTref = 3.279V
- J-Link>connect
- Please specify device / core. : ARM9
- Type '?' for selection dialog
- Device>ARM9
- Please specify target interface:
- J) JTAG (Default)
- TIF>
- Device position in JTAG chain (IRPre,DRPre) : -1,-1 => Auto-detect
- JTAGConf>
- Specify target interface speed [kHz]. : 4000 kHz
- Speed>1000
- Device "ARM9" selected.
- TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
- TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
- Cannot connect to target.
- J-Link>usb
- Disconnecting from J-Link...O.K.
- Disconnecting from J-Link...O.K.
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link Pro V4 compiled Jan 25 2017 15:46:53
- Hardware version: V4.00
- S/N: 174300742
- License(s): RDI, FlashBP, FlashDL, JFlash, GDB
- IP-Addr: DHCP (no addr. received yet)
- VTref = 3.279V
- Device "ARM9" selected.
- TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
- TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
- Cannot connect to target.
[Here i reset the board]
Source Code
- J-Link>usb
- Disconnecting from J-Link...O.K.
- Disconnecting from J-Link...O.K.
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link Pro V4 compiled Jan 25 2017 15:46:53
- Hardware version: V4.00
- S/N: 174300742
- License(s): RDI, FlashBP, FlashDL, JFlash, GDB
- IP-Addr: DHCP (no addr. received yet)
- VTref = 3.279V
- Device "ARM9" selected.
- TotalIRLen = 4, IRPrint = 0x01
- CP15.0.0: 0x41069265: ARM, Architecure 5TEJ
- CP15.0.1: 0x1D112112: ICache: 8kB (4*64*32), DCache: 8kB (4*64*32)
- Cache type: Separate, Write-back, Format C (WT supported)
- Found 1 JTAG device, Total IRLen = 4:
- #0 Id: 0x07926069, IRLen: 04, IRPrint: 0x1, ARM926EJ-S Core
- ARM9 identified.
- J-Link>i
- JTAG Id: 0x00000000: INVALID
- J-Link>i
- JTAG Id: 0x00000000: INVALID
- J-Link>i
- JTAG Id: 0x00000000: INVALID
- J-Link>usb
- Disconnecting from J-Link...O.K.
- Disconnecting from J-Link...O.K.
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link Pro V4 compiled Jan 25 2017 15:46:53
- Hardware version: V4.00
- S/N: 174300742
- License(s): RDI, FlashBP, FlashDL, JFlash, GDB
- IP-Addr: DHCP (no addr. received yet)
- VTref = 3.280V
- Device "ARM9" selected.
- TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
- TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
- Cannot connect to target.
- J-Link>usb
- Disconnecting from J-Link...O.K.
- Disconnecting from J-Link...O.K.
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link Pro V4 compiled Jan 25 2017 15:46:53
- Hardware version: V4.00
- S/N: 174300742
- License(s): RDI, FlashBP, FlashDL, JFlash, GDB
- IP-Addr: DHCP (no addr. received yet)
- VTref = 3.280V
- Device "ARM9" selected.
- TotalIRLen = 4, IRPrint = 0x01
- CP15.0.0: 0x41069265: ARM, Architecure 5TEJ
- CP15.0.1: 0x1D112112: ICache: 8kB (4*64*32), DCache: 8kB (4*64*32)
- Cache type: Separate, Write-back, Format C (WT supported)
- Found 1 JTAG device, Total IRLen = 4:
- #0 Id: 0x07926069, IRLen: 04, IRPrint: 0x1, ARM926EJ-S Core
- ARM9 identified.
- J-Link>i
- JTAG Id: 0x07926069 Version: 0x0 Part no: 0x7926 Man. Id: 0034
- J-Link>i
- JTAG Id: 0x07926069 Version: 0x0 Part no: 0x7926 Man. Id: 0034
- J-Link>i
- JTAG Id: 0x07926069 Version: 0x0 Part no: 0x7926 Man. Id: 0034
- J-Link>i
- JTAG Id: 0x07926069 Version: 0x0 Part no: 0x7926 Man. Id: 0034
- J-Link>i
- JTAG Id: 0x07926069 Version: 0x0 Part no: 0x7926 Man. Id: 0034
- J-Link>i
- JTAG Id: 0x00000000: INVALID
- J-Link>i
- JTAG Id: 0x00000000: INVALID
- J-Link>
Not sure what to think of that, is the connection 'unstable', does the chip makes itself 'unavailable' somehow over JTAG, ... ?
[2] With that last idea in mind i changed to bootmode to start in USB boot mode (so normal application SW will not be started). Using Jlink.exe with the steps above pressing i now the connection seems to be stable(r) when using the USB command (pressing i keeps working it seems).
And if I try connecting in Eclipse it also works a "little bit". By that i mean i reach the initial breakpoint in main, i can single step there, but as soon as i step over something or press Resume (F8), 95% of the time it will not work and i will get an error:
Starting target CPU...
ERROR: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 2) @ Off 0x5.
Any suggestions what might cause that?
In attachment screen shots of the eclipse debug attempt and the jlink
log file corresponding to that attempt....
The post was edited 1 time, last by BramPeeters ().