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

DSTREAM unable to connect to custom freescale vybrid platform

My client has provided a DSTREAM and professional edition of DS5. I am new to DSTREAM. We are working on freescale vybrid.  When I tried to debug my application in DS-5 using vybrid tower and DSTREAM it is able to debug. But when I tried on our custom board based on vybrid it is failing to connect and shows

Unable to connect to USB:003604

Failed to read 4 bytes from AP 0 @ 0x40001020 on DAP

Bad argument to command.

Unable to connect to USB:003604

Can any one tell me what is this error?

Also When I do auto config in debug hardware configuration tool come with ARM DS-5 bundle, it shows ' auto configure failed check debug hardware connection with the target or try using lower fixed frequency'

Even when I try to select platform, there is no vybrid platform available.

Do I need to do any specific configuration for detecting my custom board?

Please see the attachment also.

5145.zip
  • Hi,

    Which version of DS-5 are you using? 5.17.1 is the latest release.

    It looks like the read to determine the secondary core is failing. There are a few reasons why this might have happened:

    1. The configurations in the DS-5 configdb assume that there's only a DAP in the scan chain, so it won't work if there are other devices in the chain.

    2. The debug might be locked out. This can be unlocked using the DTSL "Secure Debug" options.

    3. It might be that the Vybrid doesn't have a secondary core, so it's worth checking that you have chosen the right target (though I see from your screenshot that the only options listed are i.MXx parts). Are you using an off-the-shelf Vybrid SoC?

    4. Is there definitely enough power going to the Vybrid?

    My colleague ronans put together a blog a few months ago on new platform bring-up using DS-5, so it might be worth reading through - New Platform Bring-Up with DS-5.

    I suggest skipping to the section "but what if things go wrong?" which explains custom debug configurations using DTSL scripting.

    Hope this helps,

    Joe