- This topic has 12 个回复, 9 个参与人, and was last updated 4 months, 3 weeks 前 by
xgncrusher.
-
作者帖子
-
八月 3, 2019 - 3:15 下午 #1858
zetalog
参与者整个文档和视频演示就没有说明调试器如何连接J17。
完全按照演示操作就会误以为FREELINK USB改完驱动后就可以连接ri5cy核。然后USB连接FREELINK USB,执行演示命令就得到这个:
C:\eclipse>openocd -f C:\eclipse\rv32m1_sdk_riscv\boards\rv32m1_vega\rv32m1_ri5cy.cfg
Open On-Chip Debugger 0.10.0+dev-00433-g849f49ca (2019-01-04-07:48)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 1000 kHz
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
Info : mohor tap selected
Info : adv debug unit selected
Info : Option 1 is passed to adv debug unit
Info : core 0 selected
Info : add flash_bank rv32m1 rv32m1.flash0
Info : add flash_bank rv32m1 rv32m1.flash1
Info : J-Link LPCXpresso V2 compiled Sep 23 2016 12:14:15
Info : Hardware version: 1.00
Info : VTarget = 3.300 V
Info : clock speed 1000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway…
Error: rv32m1.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : adv debug unit is configured with option ADBG_USE_HISPEED
Warn : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
Warn : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff查看NXP手册和SCHEME文档看到板载的FREELINK默认是接CortexM0核的。
它可以直接调试ri5cy核吗?
如果可以,是要通过J14和J17相连吗?或者要如何跳线?如果不行是不是要我们自备JLink了?
八月 3, 2019 - 10:06 下午 #1859whik
参与者你好,可以直接使用板载FreeLink调试器来直接调试RISC-V核的,由于板载FreeLink固件默认是CMSIS-DAP固件,需要升级为Jlink固件才可以。
- 1.断开默认连接的跳线帽J6/J8/J9/J12
- 2.板载默认为CMSIS-DAP固件,不支持调试RISC-V核调试,需要升级为Jlink固件
- 3.更新PC上的Jlink驱动程序
- 4.使用1.25->2.54mm的杜邦线,把J6/J8/J9/J12的左边和J17对应连接
- (5.开发板默认是从RI5CY核启动,所以不需要更改启动模式,如果已经修改了需要更改为从RI5CY核或ZERO核启动)
具体可参考:
九月 6, 2019 - 3:19 下午 #1897ElaineSS
参与者十一月 8, 2019 - 3:58 下午 #1974ElaineSS
参与者API手册参考NXP芯片的资料,这里的没有
七月 26, 2020 - 8:25 下午 #2048fforever
参与者按照上述方法,运行不出来,希望能得到解决,错误如下:
Open On-Chip Debugger 0.10.0+dev-00433-g849f49ca (2019-01-04-07:48)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 1000 kHz
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
Info : mohor tap selected
Info : adv debug unit selected
Info : Option 1 is passed to adv debug unit
Info : core 0 selected
Info : add flash_bank rv32m1 rv32m1.flash0
Info : add flash_bank rv32m1 rv32m1.flash1
Info : J-Link LPCXpresso V2 compiled Sep 23 2016 12:14:15
Info : Hardware version: 1.00
Info : VTarget = 3.300 V
Info : clock speed 1000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway…
Error: rv32m1.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : adv debug unit is configured with option ADBG_USE_HISPEED
Warn : Burst read timed out
Warn : Burst read timed out
Error: Burst read failed
Error: Couldn’t read the CPU state
Warn : Burst read timed out
Warn : Burst read timed out
Error: Burst read failed
Warn : Debug IF CPU control reg read failure.
Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
Info : adv debug unit is configured with option ADBG_USE_HISPEED
Warn : …attempt 1 of 5
Warn : Burst read timed out
Warn : Burst read timed out
Error: Burst read failed
Warn : Debug IF CPU control reg read failure.
Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
Info : adv debug unit is configured with option ADBG_USE_HISPEED
Warn : …attempt 2 of 5
Warn : Burst read timed out
Warn : Burst read timed out
Error: Burst read failed
Warn : Debug IF CPU control reg read failure.
Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
Info : adv debug unit is configured with option ADBG_USE_HISPEED
Warn : …attempt 3 of 5
Warn : Burst read timed out
Warn : Burst read timed out
Error: Burst read failed
Warn : Debug IF CPU control reg read failure.
Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
Info : adv debug unit is configured with option ADBG_USE_HISPEED
Warn : …attempt 4 of 5
Warn : Burst read timed out
Warn : Burst read timed out
Error: Burst read failed
Warn : Debug IF CPU control reg read failure.
Warn : Resetting JTAG TAP state and reconnectiong to debug IF.
Info : adv debug unit is configured with option ADBG_USE_HISPEED
Warn : …attempt 5 of 5
Error: Could not re-establish communication with target
Error: Error while calling rv32m1_is_cpu_running
Polling target rv32m1.cpu failed, trying to reexamine -
作者帖子
- 抱歉,回复话题必需登录。