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.

  • Resolved

CCS/AWR1642BOOST: Device is held in reset ERROR

Prodigy 160 points

Replies: 17

Views: 567

Part Number: AWR1642BOOST

Tool/software: Code Composer Studio

I am working on AWR1642Boost EVM for application development.

I am getting this error while connecting DSS XDS110 USB Debug Probe. I have followed all the steps required to debug the program as follows:

1.Flashed the 16xx ccsdebug bin (using the UNIFLASH when SOP0 and SOP2 are connected)

2.After successful flashing-> removed the SOP2 and power cycled the device.

3.ccs-> compilation on dss and mss projects ->passed well.

4.Crearting new target configuration file, the TEST CONNECTION passed well.

5.after grouping ->the message appears when trying to "CONNECT TARGET"

Error massage is:

Error connecting to the target:
(Error -1180 @ 0x0)
Device is held in reset. Take the device out of reset, and retry the operation.
(Emulation package 8.0.803.0)

Observations:

Texas Instruments XDS110 USB Debug Probe_0/Cortex_R4_0 (Disconnected : Unknown) - is getting connected

But

Texas Instruments XDS110 USB Debug Probe_0/C674X_0 (Disconnected : Unknown) - is not getting connected, it popup an error “device on reset”.

And also in flash mode binary file flashed successfully on device(using UNIFLASH).        

I had also searched on e2e forum ….and one of the solution is to make sure that  power supply is 5V, >2.5A.

In this case, yes I'm using adapter whose output capacity is 5VDC 3000mA. And I had also checked current by removing zero ohm resister on EVM board which is connected across 5v and 5v_unreg,

and current is 236 mAmp.

I have checked all the possibilities but fail to find the error, Please consider this as very urgent and help me to resolve this issue as early as possible.

  • Hi,
    After you connect to MSS core, are you able to load MSS image to it?
    And what is the value of 0xFFFFE1EC address? You need to look this address from MSS core connection and it should be 0x000F0028 value if ccsdebug.bin is flashed propery and BSS firmware matched.


    Regards,
    Jitendra
  • In reply to Jitendra Gupta:

    Hello Sir,

    Yes, I have tried to load MSS image but it popup an error -

    Cortex_R4_0: Trouble Writing Memory Block at 0x0 on Page 0 of Length 0x34: (Error -1065 @ 0x0) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.27.9)
    Cortex_R4_0: File Loader: Verification failed: Target failed to write 0x00000000
    Cortex_R4_0: GEL: File: C:\Users\sc_20717\Desktop\ePWM\New folder\New folder\AWR16xx_mss_nonOS\Debug\xwr16xx_mmw_mss_nonOS.xer4f: Load failed.

    any solution from your side will appreciate. 

    Regards,

    Sonal Chavhan. 

  • In reply to Sonal Chavhan36:

    Hello,  

    Let me know is there any solution to fix this error...

    Thanks in advance!

    Regards,

    Sonal Chavhan. 

  • In reply to Sonal Chavhan36:

    Hi Sonal,
    We need a few confirmation or information based on your board.
    1. Flashing ccsdebug.bin file:
    a. Make sure that you use xwr16xx_ccsdebug.bin file with AWR1642 device.
    b. While flashing from Uniflash, wait for all the flashing is done and it completes without any error. [It may be true based on your last comment].
    c. Post flashing, you need to remove SOP2 jumper and power cycle (physical) the board.
    2. Loading Image to the device via CCS
    a. When you connect to MSS core, could you check if address 0x00000000 is writable? Try to write something manually.
    b. Check the value of 0xFFFFE1EC address while it is connected to MSS core, it's value should be 0x000F0028.
    c. Check and confirm that you are using AWR1642 ES2.0 Silicon version, address 0xFFFF E218 [3:0] should be '0x2'.
    3. Are you able to load mmw demo image via CCS to the device (from SDK 2.1)?


    Regards,
    Jitendra
  • In reply to Sonal Chavhan36:

    Hi Sonal,
    In case you are using AWR1642 ES1.0 (address 0xFFFF E218 [3:0] = '0x1') then you need to flash xwr16xx_ccsdebug.bin from SDK 1.2 version as this is the last version which supports AWR1642 ES1.0 device.


    Regards,
    Jitendra
  • In reply to Jitendra Gupta:

    Hello Sir,

    Confirmation as following:

    1. Flashing ccsdebug.bin file:

    a. Make sure that you use xwr16xx_ccsdebug.bin file with AWR1642 device - Yes, it is xwr16xx_ccsdebug.bin  file only from SDK 2_0_0_4.

    b. While flashing from Uniflash, wait for all the flashing is done and it completes without any error. [It may be true based on your last comment] - Yes, it is successfully completed.  

    c. Post flashing, you need to remove SOP2 jumper and power cycle (physical) the board - Yes, after flashing device is kept in functional mode only by removing SOP 2 jumper and also (physical)power cycle the device.

    2. Loading Image to the device via CCS

    a. When you connect to MSS core, could you check if address 0x00000000 is writable? Try to write something manually - No, it is not writable. Manual write gives an error as follows:

    b. Check the value of 0xFFFFE1EC address while it is connected to MSS core, it's value should be 0x000F0028 - No, 0xFFFFE1EC this address has 0x00000028 value, please see below attachment-

      

    c. Check and confirm that you are using AWR1642 ES2.0 Silicon version, address 0xFFFF E218 [3:0] should be '0x2' - Yes, on 0xFFFF E218 this address first byte[3:0] has '0x2'. Please see below attachment-

    3. Are you able to load mmw demo image via CCS to the device (from SDK 2.1) - No, it is not getting loaded to device via SDK 2.1 as well.

  • In reply to Jitendra Gupta:

    Hello Sir,

    No, for my board (address 0xFFFF E218 [3:0] = '0x2'). so, it is ES2.0.

    Thanks and Regards,
    Sonal Chavhan.
  • In reply to Sonal Chavhan36:

    Hi Sonal,

    Based on this snapshot, I can say that the image (ccsdebug.bin) you have flashed is not booting up due to some reason. If it were then you should able to write on '0x0' location. 

    Issue observed in the above snapshot is very unlikely but could you try these options-

    1. For AWR1642 ES2.0, LTS version of mmWave SDK is 2.1, so better to move to this version. 

    2. Flash the mmw demo from SDK 2.1 to device using Uniflash and check if that boots up in functional mode (Only SOP2 jumper), or check those registers' value.

    Regards,

    Jitendra

  • In reply to Jitendra Gupta:

    Hello Sir,

    Yes, I just tried using SDK 2_1_0_4 version. 

    and also check for register's value. But there is no change it is showing same resister values, which I cheched for SDK 2_0_0_0_4.

    and for SDK 2_1_0_4 version as well 0x0 memory is not writable. 

    Thanks and Regards,

    Sonal R. Chavhan. 

  • In reply to Sonal Chavhan36:

    Do you another AWR1642BOOST with you which you can try this experiment on?
    Looks like some issue with your current EVM. Was it working when it arrived to you for the first time, means any application flashed on it?

    Regards,
    Jitendra

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.