• State Accepted Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 350 subscribers
  • Views 6185 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Fail to connect with CM0DSEvel

RickyChen

I have tryed to make SWD connect to Cortex-M0 DesignStart Eval by STLink2, but it was unsuccessful.

The SW Device showed information as this picture.

I chose  AHB_ROM_FPGA_SRAM_MODEL and AHB_RAM_FPGA_SRAM_MODEL be the MYM_TYPE

Parents
  • 0 in reply to Joseph Yiu

    I've checked these settings.

    First, I uesed cmsdk_mcu_pin_mux module that has Tristate buffers.

    Then, the timing report doesn't show Timing violation.

    Finnaly, the I/O standard's is sitted to 3.3V LVTTL model. By the way I've connected CM3Eval to Keil by STLINK2 successfully，that FPGA's I/O standard has setted the same model.

    I've viewed some question（community.arm.com/.../fail-to-add-jtag-swd-debug-into-cortex-m0）, and there was developer said that CM0Eval did not have Debug function. Is this the reason why I can not find core-sight？

    I am looking forward to your reply.

    Best Wishes!

Reply
  • 0 in reply to Joseph Yiu

    I've checked these settings.

    First, I uesed cmsdk_mcu_pin_mux module that has Tristate buffers.

    Then, the timing report doesn't show Timing violation.

    Finnaly, the I/O standard's is sitted to 3.3V LVTTL model. By the way I've connected CM3Eval to Keil by STLINK2 successfully，that FPGA's I/O standard has setted the same model.

    I've viewed some question（community.arm.com/.../fail-to-add-jtag-swd-debug-into-cortex-m0）, and there was developer said that CM0Eval did not have Debug function. Is this the reason why I can not find core-sight？

    I am looking forward to your reply.

    Best Wishes!

Children
  • +1 Arm Employee Badge in reply to RickyChen

    There are two releases of Cortex-M0 DesignStart

    - August 2010: this version does not have debug

    - 2017 version (r2p0-00rel0) has debug

    (Update: Serial wire only. See http://infocenter.arm.com/help/topic/com.arm.doc.dui0926b/ch01s03s02.html for limitations)

    I will try have a closer look later this week. Meanwhile, if you do have access to another debug probe it worth trying as well. The DAP module used on Cortex-M3 and Cortex-M0 were different and I wonder if this is due to old version of STLink firmware not able to detect the Cortex-M0 DAP correctly.

    regards,

    Joseph

  • 0 in reply to Joseph Yiu

    Thank you so much~

    I solved it.

    The siganl connection is different from M3Eval.

    I'v changed the connection, that was mcu_sys's SWDIOTMS via pin_mux's SWDIOTMS direct connect. I connected CDBGPWRUPREQ to CDBGPWRUPACK.

    Finally, I got the SW-DP with ID 0x0BB11477 with DEBUG function!

    There are something worng with DEBUG, but I got it at least.

    Thanks for your help!

    The best wishes!