• Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 532 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

(Error -1203 @ 0x3D5B) upon reconnecting to CortexA8 (BeagleBone white)

akarapatis
Prodigy 160 points

Other Parts Discussed in Thread: CODECOMPOSER

I am using:

CodeComposer  Version: 5.5.0.00077 ( fully updated)
Host: Linux 64bit (Ubuntu 12.04.3 updated) 
BeagleBone white rev A6a
XDS100v2  Emulator
Configuration file: 
0741.thanasis.ccxml.zip 

The problem I am facing is that whenever I try to reconnect to the beaglebone white :

Error connecting to the target:
(Error -1203 @ 0x3D5B)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 5.1.320.0)

The sequence to reproduce the problem is:
1. Launch target configuration
2. Connect to beaglebone
3. Disconnect
4. Connect again -> error !! 

How I solve it at the moment: 
In order to be able to connect again, I have to unplug the beaglebone from the USB and from any power source.

I have tried using different gel files ( as I am using the one from StarterWare, but still it is not working)
I also tried reinstalling the software but no luck there too.  

  • TI__Guru**** 171819 points

    Hi,

    Despite I do not have a Rev A6 BBone white, I can connect/reconnect to my Rev A3 board without a problem, therefore this may be due to a combination between the running application and the board. To better pinpoint what may be happening, I recommend taking a look at this forum thread. Also, you can manually launch the target to pinpoint which core/router this issue is coming from according to this thread. 

    One detail I noticed from your target configuration file: I see you are using a custom GEL file for the Cortex A8. If you are trying to connect to the board with pre-loaded code only to inspect its running status, the GEL file will try to re-initialize the device as if it was being done for the first time, which will disrupt the current running environment. If you don't intend to do that but instead restart the environment as similar as before, you can press the reset button in the board before connecting for the second time - this way the GEL may be able to reconfigure the device as close as if it was coming from a power up scenario.

    Hope this helps,

    Rafael

  • in reply to desouza
    Prodigy 160 points

    Thank you Rafael for your reply.

    I thought it would be working for you as it did for me in the beginning but then stopped working.  So I either guessing it might a software issue or a faulty board . I tried reinstalling but that did not help, I also tried another beaglebone white but I have the same problem with that as well.

    As for the target configuration I also tried the default one from the StarterWare which I was using initially (see 3324.AM335x_beaglebone.gel.zip ) . However, the same behavior applies. Also tried pressing reset which also did not do any difference.
    Please note that I already launch it manually. 
     The Test Connection works correctly

    I do not load any program I just do the following:
    1. Launch target configuration from the target configurations view
    2. Connect to Connect to CortexA8
    3. Disconnect
    4. Connect again ---> Error 

    As for the forum thread you recommend, I do not think it applies to my case. As I do not have a custom board but a beaglebone and I already have tried all the suggestion.