• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 508 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.

Problems with RM48L952ZWTT

ee hh
Prodigy 40 points
Other Parts Discussed in Thread: RM48L952, RM48L950

Hello

I'm trying to flash and then debug a basic program on RM48L952, which is located on a PCB we designed.

The "test connection" option in Codewarrior is completed successfully. I'm not sure, but I guess this means that all the basic JTAG lines are fine.

However, when I try to flash the program, or get any connection to the MCU, I keep getting error 1206:

     CortexR4: Error connecting to the target: (Error -1206 @ 0x0) Unable to access the DAP

Already tried looking in some answers in this forum, but nothing I tried works.

The same program is flashed properly on the evaluation board, and working fine.

The JTAG lines between the MCU and the JTAG connector are designed similarly to the evaluation board, as far as I checked. The clock source for the MCU comes from a 16Mhz oscillator instead of a crystal, if this matters.

This is the emulator I'm using: Blackhawk USB560v2 System Trace Emulator:

http://www.blackhawk-dsp.com/products/USB560v2.aspx

Any ideas?

Thanks

  • 0
    TI__Guru 68980 points

    ee hh,

    Are you trying to use codewarrior from freescale to debug the RM48L952?

     

  • 0 in reply to Anthony F. Seely
    Prodigy 40 points

    Sorry, I meant CCS of course.

  • 0 in reply to ee hh
    TI__Guru 68980 points

    Ok, if you have CCSv5.4 (or maybe even 5.5) we had an issue with the default settings for the XDS560v2 emulator so I would check this first.

    Open the target configuration file that you are using, and select the 'Advanced Tab'.

    Expand the connection tree (Starting from the emulator name) until the level that shows "CortexR4".  Select the Cortex R4 in the tree and on the right you will see some settings.

    If the "Access Port Designator" setting is '0x0' then this is likely the problem.   Change it to 0x02000100 and save the target configuration.   Then try connecting.

  • 0 in reply to Anthony F. Seely
    Prodigy 40 points

    Hi Anthony

    Thanks for the answer.
    This setting is already set up.
    So does the partnum change, as one of your mates suggested in another answer, to change the partnum to partnum="RM48L950" in the file rm48l952.xml .

    As I wrote earlier, the current configuration does work with the evaluation board that has the same MCU.

    Any other options?

    Regarding the PCB design (pullup resistors , MCU pins & JTAG pins connection), there shouldn't be any difference from the evaluation board, right?

  • 0 in reply to ee hh
    TI__Guru 68980 points

    Hi ee,

    If you want to send some schematics for us to look at we can do this.

    I'm checking w. some of the other guys on the team about the RM48L952 vs. 950.  I do seem to remember something about this being explained to me but I thought it was related to the clock rate and flash programming not just a simple 'connect to target' issue.

    -Anthony

  • 0 in reply to Anthony F. Seely
    TI__Guru 68980 points

    ee,

    Checked w. my colleague and he said if you've got CCSv5.5 no need to change the part #.
    CCSv5.4 might be a problem --  Which CCS version # did you have?

    In addition to making the CCS update to 5.5 - he suggested also making sure you have the blackhawk emulation pkg. updated to 5.5.0.102 at least and hercules emulation pack to 5.5.0.9 at least. (these should currently be the 'latest' pkgs. as of this posting date...)  

  • 0 in reply to Anthony F. Seely
    Prodigy 40 points

    Hi

    Update about this: after changing to a another (new) PCB and replacing the JTAG emulator to a new one, the problem was solved. 

    Thanks

  • 0 in reply to ee hh
    TI__Guru 68980 points

    EE,

    Great, glad that it was just a bad board.

    If you are going to try to debug the bad board there some wiki pages we can point you to on the TI processors wiki related to debugging JTAG hardware problems.   Otherwise let us know and we'll close this thread.