RISC-V MCU中文社区

【求助】 采用rs232-hs下载程序时出现错误

发表于 开源蜂鸟E203 2024-08-27 17:41:09
0
625
0

新人第一次做项目,在利用Nuclei Studio进行下载的时候出现了问题,确认了引脚和电源接线,因为是下载bitstgream用的线,应该没有问题,双cpu的idcode也都可以找到,但是auto.tap里好像存在部分问题,现在不确定是哪的问题,网上查阅了很久好像也没找到相类似的问题,有没有大佬讲讲,以下是问题:
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Info : no device found, trying D2xx driver
Info : D2xx device count: 2
Info : Connecting to “Dual RS232-HS A” using D2xx mode…
Info : clock speed 1000 kHz
Info : JTAG tap: riscv.cpu tap/device found: 0x40400211 (mfg: 0x108 (Ardent Technologies), part: 0x0400, ver: 0x4)
Info : JTAG tap: riscv1.cpu tap/device found: 0x924a5549 (mfg: 0x2a4 (Emulex), part: 0x24a5, ver: 0x9)
Info : TAP auto0.tap does not have valid IDCODE (idcode=0x4a492248)
Info : TAP auto1.tap does not have valid IDCODE (idcode=0x25249124)
Info : TAP auto2.tap does not have valid IDCODE (idcode=0x92924892)
Info : JTAG tap: auto3.tap tap/device found: 0x49492449 (mfg: 0x224 (Raza Microelectronics), part: 0x9492, ver: 0x4)
Info : TAP auto4.tap does not have valid IDCODE (idcode=0x92492492)
Info : JTAG tap: auto5.tap tap/device found: 0x49249249 (mfg: 0x124 (Peregrine Semiconductor), part: 0x9249, ver: 0x4)
Info : TAP auto6.tap does not have valid IDCODE (idcode=0x92492492)
Info : JTAG tap: auto7.tap tap/device found: 0x49249249 (mfg: 0x124 (Peregrine Semiconductor), part: 0x9249, ver: 0x4)
Info : TAP auto8.tap does not have valid IDCODE (idcode=0x92492492)
Info : JTAG tap: auto9.tap tap/device found: 0x49249249 (mfg: 0x124 (Peregrine Semiconductor), part: 0x9249, ver: 0x4)
Info : TAP auto10.tap does not have valid IDCODE (idcode=0x92492492)
Info : JTAG tap: auto11.tap tap/device found: 0x49249249 (mfg: 0x124 (Peregrine Semiconductor), part: 0x9249, ver: 0x4)
Info : TAP auto12.tap does not have valid IDCODE (idcode=0x92492492)
Info : JTAG tap: auto13.tap tap/device found: 0x49249249 (mfg: 0x124 (Peregrine Semiconductor), part: 0x9249, ver: 0x4)
Info : TAP auto14.tap does not have valid IDCODE (idcode=0x92492492)
Info : JTAG tap: auto15.tap tap/device found: 0x49249249 (mfg: 0x124 (Peregrine Semiconductor), part: 0x9249, ver: 0x4)
Info : TAP auto16.tap does not have valid IDCODE (idcode=0x92492492)
Info : JTAG tap: auto17.tap tap/device found: 0x49249249 (mfg: 0x124 (Peregrine Semiconductor), part: 0x9249, ver: 0x4)
Info : TAP auto18.tap does not have valid IDCODE (idcode=0x92492492)
Warn : Unexpected idcode after end of chain: 331 0x49249249
Warn : Unexpected idcode after end of chain: 363 0x92492492
Warn : Unexpected idcode after end of chain: 395 0x24924924
Warn : Unexpected idcode after end of chain: 427 0x49249249
Warn : Unexpected idcode after end of chain: 459 0x92492492
Warn : Unexpected idcode after end of chain: 491 0x24924924
Warn : Unexpected idcode after end of chain: 523 0x49249249
Warn : Unexpected idcode after end of chain: 555 0x92492492
Warn : Unexpected idcode after end of chain: 587 0x24924924
Warn : Unexpected idcode after end of chain: 619 0x49249249
Error: double-check your JTAG setup (interface, speed, …)
Error: Trying to use configured scan chain anyway…
Error: riscv1.cpu: IR capture error; saw 0x14 not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: dtmcontrol is 0. Check JTAG connectivity/board power.
Warn : target riscv.cpu examination failed
Error: dtmcontrol is 0. Check JTAG connectivity/board power.
Warn : target riscv1.cpu examination failed
Info : starting gdb server for riscv.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for riscv1.cpu on 3334
Info : Listening on port 3334 for gdb connections
Error: Target not examined yet

以下是openocd:
adapter speed 1000

adapter driver ftdi

ftdi_device_desc “Dual RS232-HS”
ftdi_vid_pid 0x0403 0x6010
ftdi_oscan1_mode on

transport select jtag

ftdi_layout_init 0x0008 0x001b
ftdi_layout_signal nSRST -oe 0x0020 -data 0x0020
ftdi_layout_signal TCK -data 0x0001
ftdi_layout_signal TDI -data 0x0002
ftdi_layout_signal TDO -input 0x0004
ftdi_layout_signal TMS -data 0x0008
ftdi_layout_signal JTAG_SEL -data 0x0100 -oe 0x0100

set _CHIPNAME riscv
set _CHIPNAME1 riscv1

jtag newtap $_CHIPNAME cpu -irlen 5
jtag newtap $_CHIPNAME1 cpu -irlen 5

set _TARGETNAME $_CHIPNAME.cpu
set _TARGETNAME1 $_CHIPNAME1.cpu

target create $_TARGETNAME riscv -chain-position $_TARGETNAME -coreid 0
target create $_TARGETNAME1 riscv -chain-position $_TARGETNAME1 -coreid 0

tcl_port disabled
telnet_port disabled
gdb_port 3333

init
if {[ info exists pulse_srst]} {
ftdi_set_signal nSRST 0
ftdi_set_signal nSRST z
}
halt
echo “Ready for Remote Connections”

喜欢0
用户评论
befer

befer 实名认证

懒的都不写签名

积分
问答
粉丝
关注
  • RV-STAR 开发板
  • RISC-V处理器设计系列课程
  • 培养RISC-V大学土壤 共建RISC-V教育生态
RV-STAR 开发板