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.

Problem connecting to DM365 EVM using XDS510PP Plus

Hi!

I am trying to connect to DM365 EVM (Rev D) from CCS (3.3.82.13), using XDS510PP Plus (Rev A).
I am using GEL file (Ver 1.02) <attached> .  

I see that CCS fails to connect. However if I comment out PLL initialiation code in GEL, then it is able to connect to target successfully.

I tried to move PLL init code into my C code.
With this, emulator disconnects as I run my code.
When I single step, I found that emulator disconnects as soon as PLL is put into BYPASS mode, during initialization steps.

I also tried configuring PLL in assembly, by refering to u-boot code (start.S). I have similar observation as above, emulator disconnects when PLL is put to BYPASS mode, during initialization steps.

Any idea on why I am not able to configure PLL from CCS?

Another observation is, with gel file, with PLL init commented, emulator connects only after processor is let run to boot from NAND i.e. after bootloader comes up (NAND has bootloader flashed onto it).
Is bootloader helping to bring ARM to a defined state?

Here is the output when I try to connect with GEL file loaded (PLL init uncommented)

Trouble Writing Memory Block at 0x1c40900 on Page 0 of Length 0x4:
Error 0x80002002/-140
Fatal Error during: Memory, Control,
Error generated by SD scan controller module

Here is GEL output for the above scenario -

Disable IRQ/FIQ
Flush Cache
Disable MMU
Setup Power Modules (All on)... [Done]
Setup PinMux... [Done]
Setup PLL0...        --> crashes here (seems like entering an infinite loop)

 

Any help is appreciated.

  • I have a very similar problem. Spectrum Digital XDS510PP Plus emulator and their EVMDM365 board. Can't even get to the .gel execution part of it, it stops with

    Fatal Error during: Memory, Control,
    Error generated by SD scan controller module

    message (or similar) before even connecting.

    Did anyone have this resolved? SD claims they tested this emulator/board combination, but won't provide an appropriate .ccs file.

    Any insight will be appreciated.

  • Hi Alexander,

    It is possible that when PLL is being programmed you loose RTCK while PLL is switching over.  The RTCK will also become much slower as it is slaved to the device core clock. It may only work if you are using an external adaptive clocking adapter to deal the RTCK issue. Aside of this, you will need to configure the PP+ via SdConfig(Ex) to uncheck disable polling and set the port speed to 100.  This will force the emulator to poll for emulator command completion and the 100 is the max retry loop count.  

    Hope this helps.

    Thanks,

    Tai

  • Tai,

    your advice actually helped! It must have been the port speed parameter. Now it works. Thank you very much.

    The other bit of info for the future generations: pull up EMU0 and EMU1 pins on your boards (or at least on your emulator cable). Internal pullup resistors on those pins that the DM365 docs claim to be present are either not there, or insufficient. As a result your board may work with some emulators, but not the others.

    A.

  • Hi Alexander,

    You are welcome. I am glad the suggestion worked for you.

    Regarding the pull up on EMU0 and EMU1 pins, SDI has the pull ups on those pins. Please refer to page 102 of the DM365EVM Technical Reference (you can find it here) or schematics sheet 19. You are correct that as a good practice is to have external pull ups on those two pins.

    Thanks.

    -Tai Nguyen