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.

Could not erase the DAP (Its not 0xffff_ffff every where)

Hello,

I have followed this procedure to check the memory of DAP. I could not erase the DAP.

1] After connecting the DAP, select "Texas Instruments XDS100v2 USB Emulator_0/Dap.
2] Select View->Memory Browser to open a memory window.
3] In the memory window enter 0x0000 and Go.
4] You should see the content of the Flash. Is it erased? (0xffff_ffff every where)
5] Enter a new base address as 0xFFFFFF00 (System Register)
6] Are you able to read something? 
7] At address 0xFFFFFFE0 you should read 0x00004000
8] Write 0x0 at this location.
9] Try to connect the CortexR4.

---------------------------------------------------------------------------------

XDS100V2 emulator TMS570LS20X Board

Could you suggest me. Thanks in advance.

  • Hello Aniketh,

    Based on the screen capture I will assume you are successfully connected to the device.

    Next, go to Tools-->Debugger Options-->Program/Memory Load Options

    This should open a panel with the noted title (Program/Memory Load Options).

    Select, the "On-Chip Flash" menu item in the panel on the left. This will cause the flash options to show in the panel to the right as shown in the picture below:

    Using the scroll bar on the window to the right of the panel (gray area), scroll down to "Erase Option." You will see the options to erase the entire flash, only the necessary sectors (determined by the image size to be programmed), or selected sectors. For you case, select entire flash (default selection).

    After selecting these, continue scrolling past the sector information to the bottom of the "Erase Options" section where you will see  a button labeled "Erase Flash" which you can click on to initiate the erase. Note there is a check box to "Enable Verbose Output" which will cause the erase to output information as it erases each sector and allow you to see a bit more of what is happening.

    Hopefully, this helps.

    Regards,

    Chuck Davenport

  • Hello Davenport,

    I tried now but it still shows the same error
    -------------------------------------------------------------------------------
    [16:41:59] Begin Launching session operation...
    [16:42:05] Operation Launching session returned.
    [16:42:05] Loaded target configuration from: C:\Users\achepuri\ti\CCSTargetConfigurations\tms570.ccxml
    [16:43:38] Restored settings from file: C:\Users\achepuri\ti\CCSTargetConfigurations\tms570.uniflashsession
    [16:44:07] FATAL >> Dap: Error connecting to the target: (Error -242 @ 0x0) A router subpath could not be accessed. The board configuration file is probably incorrect. (Emulation package 0.0.0.0)
    0-------------------------------------------------------------

    What should me my further steps to stop the error ??

    Regards,
  • Hello Aniketh,

    Can you double check your TM570.ccxml to insure it is set up with the correct part number for the device you are programming/erasing?
  • Hello,

    I have checked the .ccxml it is fine.

    regards,

  • Hello Aniketh,

    Can you open the ccxml file where you can see something similar to the below image:

    Click on the "Test Connection" button and post the resulting text output so we can check the connectivity of the debugger?

    Next, click on the "Advanced" tab at the bottom of the window and post the diagram that is displayed that is similar to the below.

  •  Hello Davenport,

    Here is the screenshot of the test configuratoon

  • Thank you, Aniketh. Were you able to execute the "Test Connection" to see if there are any scan chains that failed the test?

    In your original post, you posted a memory window view that showed the content of the device at address 0x0. Seeing this, I believe the connections should be OK given the debugger must go through the DAP to access the memory on the device. The only time I have seen the type of error you are describing is if the device is not connected via a debug session or if the device is not powered properly.

    Also, can you confirm the CCS version you are using? Is it the latest CCS6.1.0 or a prior version? Also, are you using the USB to power the board or are you plugged into a power outlet? Finally, what OS version are you using (WinXP, Win7, Win8?) Apologies for all the questions, but simply trying to figure out what might be affecting the setup.