Connect to the PRSC failed problem

vijayabharathi chelladurai

Other Parts Discussed in Thread: OMAPL138, SECDEVTOOL-OMAPL138C6748

Iam getting the error "Connect to the PRSC failed" in the CCS message, when i tried to connect to the OMAPl138 using XDS100v2.

Iam currently using the CCS 4.1.2

Processor : OMAPl138 Rev 2.0

Iam currently using the omapl138 which contains the Secure boot option.. Is the current error due to this problem? KIndly suggest us

Regards

Vijayabharathi C

over 14 years ago

0 desouza over 14 years ago

TI__Guru**** 171309 points

Vijayabharathi,

Could you check the forum thread below? There are some troubleshooting suggestions listed there.

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/89175/308728.aspx#308728

I am not sure what "Secure boot" means exactly (unfortunately I am not the most knowledgeable person to talk about the device itself), but can you connect to the device before it starts the boot sequence? This way you could be able to single the connection process itself.

You can also check the status of the cores (and see if they are powered up or with active clock) by looking at the short clip named Using ICEPICK in the page below:

http://processors.wiki.ti.com/index.php/Quick_Tips

Hope this helps,

Rafael

0 vijayabharathi chelladurai over 14 years ago in reply to desouza

Intellectual 955 points

Thanks for the reply

When i tried "dbjtag" test it is passing succesfully.

We verfied the clock, reset, all are stable.

Currently we are using the below processor

http://focus.ti.com/docs/toolsw/folders/print/secdevtool-omapl138c6748.html

Regards

Vijayabharathi C

0 vijayabharathi chelladurai over 14 years ago in reply to vijayabharathi chelladurai

Intellectual 955 points

Hi Rafael

We identified the problem. its due to "Secure boot option" in OMAPl138. We replaced the Secure boot OMAPl138 chip with non secure OMAPl138 chip in our custom board. Now we could able to connect to the Target using the CCS. Debug tap of ICEPICK is disabled on a secure device by default and the device will have no JTAG access by default.

Regards

Vijayabharathi C

0 desouza over 14 years ago in reply to vijayabharathi chelladurai

TI__Guru**** 171309 points

Vijayabharathi,

Thank you for reporting your findings. This will be very useful for other developers.

Thank you,

Rafael

0 ~Inoui ~ over 13 years ago in reply to vijayabharathi chelladurai

Expert 1240 points

Hi,

i am getting same error of PRSC

Where to find the Secure Boot option /

I am using DM6446 board.

Jtag : XDS 510 USB jatg

0 xiaoin zhang over 11 years ago in reply to vijayabharathi chelladurai

Prodigy 10 points

hi Vijayabharathi C

how can i change the a secure device by default

Code Composer Studio™︎

Code Composer Studio forum

Connect to the PRSC failed problem