开发板串口输出信息: couldn't read CPU state

Home 论坛 一般性讨论 开发板串口输出信息: couldn't read CPU state

正在查看 3 帖子:1-3 (共 3 个帖子)
  • 作者
    帖子
  • #1642
    fangdbfangdb
    参与者

    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 : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
    Warn : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
    Warn : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
    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 : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
    Warn : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
    Warn : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
    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
    Warn : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
    Warn : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
    Warn : CRC ERROR! Computed 0x00000000, read CRC 0xffffffff
    Error: Burst read failed
    Error: Couldn’t read the CPU state
    Examination failed, GDB will be halted. Polling again in 6300ms

     

    是 OPENOCD  驱动问题还是板子 问题呢 ?

    大家不要申请了板子就 放在那里睡觉了 ,否则就是毫无意义。

    作为社区来说没有进步,作为 nxp方来说,文档写的语焉不详,也没有人提意见,失去了进步动力

    整个生态前进步伐很慢

    #1643
    fangdbfangdb
    参与者

    说明一下:    看过文档,仔细看了一下文档,原来RV32M1芯片默认从RISC-V核启动,所以使用的指令:

     

     

    按照这份链接  step by step

    https://open-isa.cn/community/topic/%E7%BB%87%E5%A5%B3%E6%98%9F%E5%BC%80%E5%8F%91%E7%89%88%E5%90%AF%E5%8A%A8%E6%A8%A1%E5%BC%8F%E4%BF%AE%E6%94%B9-%E4%BB%8Earm-m4%E6%A0%B8%E5%90%AF%E5%8A%A8/

    #1645
    fangdbfangdb
    参与者

    自己找到原因。发现了 jlink 连接不好。。。

正在查看 3 帖子:1-3 (共 3 个帖子)
  • 抱歉,回复话题必需登录。