• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 52 subscribers
  • Views 1326 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.

Trouble Writing Memory Block with XDS510LC USB

Guido Suedholt
Prodigy 130 points

Other Parts Discussed in Thread: TMS320F2812

Hi Folks!

I am using Code Composer Studio V4.1.3.00038 with a XDS510LC USB emulator (Spectrum Digital) on a TMS320F2812 based board,
comparable to the eZdsp F2812 evaluation board.

In the early days (June) the uploading object code to external RAM (0x108000) board through the emulator works
very well, but after a series of CCS updates I get the following error message and the emulator hangs:

C28xx: Trouble Writing Memory Block at 0x108000 on Page 0 of Length 0x3ff8: Error 0x80002082/-1250
Fatal Error during: Memory, Target Communication, Control,  Device driver: Lost USB connection to emulator.
You should ABORT and restart to re-establish the USB link. 
Cannot write to target

Deeper investigations have shown that the RAM is accessible (manual read / write), but simply manually filling larger memory regions
(> 0x3800 words, independent from address) does not work and ends with the same result as above.
Therefore I assume that this problem is related to buffer sizes, timing or something in this area.
Programming of the flash memory (of course with a different memory map) works fine.

After having trouble with setting breakpoints, this patch was applied:
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/60276/215606.aspx#215606

Thanks in advance & Regards.
  Guido

  • 0
    TI__Guru**** 173310 points

    Guido,

    I don't have access to a XDS510LC emulator at the moment, but I cannot duplicate this issue with a XDS510USB emulator. I think the problem might have to do with the CCS update and driver patch that you applied, especially since you say this worked prior to these updates.

    Guido Suedholt said:
    Deeper investigations have shown that the RAM is accessible (manual read / write), but simply manually filling larger memory regions
    (> 0x3800 words, independent from address) does not work and ends with the same result as above.

    Are you saying that if you open a memory window at 0x108000 and try to fill a length >0x3800 with a certain value, it results in this error?

     

    Guido Suedholt said:
    After having trouble with setting breakpoints, this patch was applied:
    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/60276/215606.aspx#215606

    So you first updated to CCS 4.1.3, then updated the Spectrum drivers from the update site (the incorrectly posted ones?), and then applied the drivers attached to the above post to revert back to correct drivers? If so, I wonder if the drivers are not installed properly. Although not the ideal solution, could you try uninstalling and reinstalling CCS 4.1.3?

  • 0 in reply to AartiG
    Prodigy 130 points

    Hi Aarti!

    Thanks for your reply.

    Aarti said:

    Deeper investigations have shown that the RAM is accessible (manual read / write), but simply manually filling larger memory regions

    (> 0x3800 words, independent from address) does not work and ends with the same result as above.

    Are you saying that if you open a memory window at 0x108000 and try to fill a length >0x3800 with a certain value, it results in this error?

    [/quote]

    Yes, exactely.

    Aarti said:

    After having trouble with setting breakpoints, this patch was applied:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/60276/215606.aspx#215606

    So you first updated to CCS 4.1.3, then updated the Spectrum drivers from the update site (the incorrectly posted ones?), and then applied the drivers attached to the above post to revert back to correct drivers? If so, I wonder if the drivers are not installed properly. Although not the ideal solution, could you try uninstalling and reinstalling CCS 4.1.3?

    [/quote]

    On the other hand all the other USB communication works very well and stable, bus I will give it a try on another PC...
    But after updating to CCS 4.1.3 or installing it from scratch, it will again not be possible, to set BreakPoints, I assume.

    Regards.
      Guido

     

  • 0 in reply to Guido Suedholt
    TI__Guru**** 163045 points

    Guido,

    SD should have the correct drivers on their update site now so if you install 4.1.3 and get their driver update you should not lose the ability to set HW breakpoints.

    I have a 510LC. I will dig up a 2812 and see if I can reproduce the error you get filling memory.

    Regards,

    John

  • 0 in reply to JohnS
    TI__Guru**** 163045 points

    Ok if I do this in my 4.1.3 install with a eZdspF2812 and a Spectrum Digital C2000 XDS510LC I get the following error.

    C28xx: Trouble Writing Memory Block at 0x108000 on Page 0 of Length 0x3800: Error 0x80002082/-1250 Fatal Error during: Memory, Target Communication, Control,  Device driver: Lost USB connection to emulator. You should ABORT and restart to re-establish the USB link. 

    I then tried the same board with a Blackhawk USB510L and it works with no error.

    I then tried CCSv4.2.0 RC1.  Need to pull the USB cable and replug before switching CCS versions.  Here the first time I tried it most of the memory was filled before I got the error.  Subsequent tries I got it right away just like in 4.1.3.

    I will pass this on to Spectrum Digital as it appears there is something wrong with their LC driver.

    John

     

  • 0 in reply to JohnS
    Prodigy 130 points

    Hi JohnS!

    Thank you very much for reproducing my problem.

    I will monitor this thread for a solution from SD.

    Regards.

      Guido

  • 0 in reply to JohnS
    TI__Guru**** 163045 points

    Like Aarti I also tried the regular SD 510USB and it works fine so the problem is isolated to the LC version.

    John

  • 0 in reply to JohnS
    Prodigy 130 points

    Hi John!

    What do you expect or what is our experience: How long does it take usually until Spectrum Digital solves such a bug?
    Do they give any statement or timeline? Or takes it usually some weeks or months, so  that it makes sense to buy another emulator?

    Regards.
      Guido

  • 0 in reply to Guido Suedholt
    TI__Guru**** 163045 points

    Guido,

    Spectrum is typically pretty responsive to issues like this.  I heard back that they believe they know what the problem is.  When they have a solution what they would do is post a new driver package on their update site and CCS should pull it down automatically.  I don't have a timeline for you right now.  I expect I will hear from them today or tomorrow if their suspicion as to what the problem is was correct.

    Unless you have somewhere that you can get a cheap XDS100 within a few days I would wait for the fix.

    john

  • 0 in reply to JohnS
    TI__Guru**** 163045 points

    Good news.  I have an updated driver from Spectrum that fixes the issue.  

    Close CCS

    Extract the dvr file from the attached zip file and copy it into ccsv4\emulation\drivers Replace the file that is there.

    Start CCS

    unplug the USB cable on your emulator and plug it back in again (I had to do this to get mine to work)

    Now give it a try.

     

    The updated driver will be included in Spectrum's next update but they have provided the file early for anyone who is hitting this issue.

    Regards,

    John

     

    sdgo28xusb.zip
  • 0 in reply to JohnS
    Prodigy 130 points

    Hi John!

    Great! What a short response time!


    Now the RAM access works perfectly, filling RAM and uploading code into RAM causes no problems anymore.

    Thanks again & Regards.
      Guido