STM32F2 Cannot find debug component in ROM Table

Comments

2 comments

  • Avatar
    Gordon Scott

    Boot0 and Boot1 are both low on this board, which is the same as my own-designed boards that do program OK.

     

    Apparently the Olimex board multiplexes some JTAG pins. Pressing the WKUP button is supposed to stop that, though it hasn't solved my problem.

    0
    Comment actions Permalink
  • Avatar
    Gordon Scott

    Does anyone have any advice on this?

    I still can't get this to connect properly with the ARM-USB-OCD-H JTAG connection.

    After reducing the JTAG clock speed to half, the problem has changed from "cannot set debug register" to "Cannot find debug component in ROM Table", which sounds rather like a Crossworks problem to me.


    I've tried pressing the WKUP, pressing and holding the WKUP and the other boot0/boot1 settings. In the other boot settings Crossworks recognises the board OK, but fails to erase or program, which I think is expected.

    With boot0 high I connect OK and see the device type reported on the status line.
    If I try to erase I get a 'Loader verify failed", which I think is as expected. I get similar results however boot1 is set. I've now reverted to boot0 low as I think that's the right setting.

    0
    Comment actions Permalink

Please sign in to leave a comment.