OMAP L138 connecting problem with CCS 4.1.2

ravindra mudreddy

Prodigy 230 points

Other Parts Discussed in Thread: OMAPL138

i have downloaded new CCS 4.1.2, i am trying to connect to OMAP L138 with the help of XDS100V2(vista OS)

when i do a connect

nothing happens, not even my gel script gets executed

ravindra

over 15 years ago

0 tlee over 15 years ago

TI__Guru 62975 points

Ravindra,

Does CCS try to connect? Does your device status change to "Connected" or does it stall trying to connect? Do you get any error messages? Have you updated your XDS100v2 ( http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_update_the_CPLD_on_my_XDS100v2.3F )?

-Tommy

0 Gerry Simmons over 15 years ago

Intellectual 875 points

I had a similar experience with my Stellaris Dev. kits. I had CCS 4.1.1 loaded, and when CCS came up, it asked me if I wanted to upgrade. I checked what it wanted to upgrade:

4.1.2.00027 Service Release
MSP430 Code Generation Tools 3.2.3
TMS470 Code Generation Tools 4.6.3

When I let CCS upgrade itself, all communications to my Dev. Kit boards ceased. Same symptoms.

I uninstalled CCS 4.1.2 and re-installed 4.1.1, and everything started working again.

0 Gerry Simmons over 15 years ago in reply to Gerry Simmons

Intellectual 875 points

My experience was that CCS stalled in trying to connect to target, and it never timed out. I closed CCS to resolve the stalling issue.

No error messages.

0 ravindra mudreddy over 15 years ago in reply to tlee

Prodigy 230 points

hi tommy

i did not get any error messages (i will get back to you on the status)

1) about the cpld update ,,,, is it safe to do that, because i guess the changes cannot be reverted back(is it backward compatable)

2) do you have any updates about the problems in CCS4.1.2 with omp l138(or should i download 4.1.1)

3) perviously i was using CCS4.0.xxx, in that i wgen i selected xds100V2 i did not get target named omap l138,,,, instead i use to connect using L137,,,,, can you help me in solving this

4) one more thing i wanted to say was, that the board is loaded with linux ,,,,, and i am trying to connect to it while its booting is this a problem

ravindra

0 tlee over 15 years ago in reply to ravindra mudreddy

TI__Guru 62975 points

ravindra mudreddy said:
1) about the cpld update ,,,, is it safe to do that, because i guess the changes cannot be reverted back(is it backward compatable)

Yes, the CPLD has been checked out by a number of internal users and has proven to be safe thus far.

ravindra mudreddy said:
2) do you have any updates about the problems in CCS4.1.2 with omp l138(or should i download 4.1.1)

I am not aware of any problems specific to CCS4.1.2.

ravindra mudreddy said:
3) perviously i was using CCS4.0.xxx, in that i wgen i selected xds100V2 i did not get target named omap l138,,,, instead i use to connect using L137,,,,, can you help me in solving this

I think this was an honest mistake. XDS100v2 is supported for OMAPL138 and the hardware setup is compatible between the two devices.

ravindra mudreddy said:
4) one more thing i wanted to say was, that the board is loaded with linux ,,,,, and i am trying to connect to it while its booting is this a problem

There may be some issues to work around when connecting to ARM actively running Linux vs plain C-code. The CCS team recently completed this article for Linux-aware debug with CCS4: http://processors.wiki.ti.com/index.php/Linux_Aware_Debug

0 JayVee over 15 years ago in reply to tlee

Prodigy 180 points

I'd like to chime in on this problem since I'm seeing a similar problem. I'm also running CCS 4.1.2 (on Windows XP) and I'm using the XDS100V2 to connect to the Omap L138 eXperimenters kit, and I get the following error message in CCS4:

"Arm9_0:gel:error while executing OnTargetConnect():attempted to read unmapped virtual memory at 0X01C10800:failed to get PRSC status.

This gel file works with the eXperimenters kit when I use the XDS510 USB emulator instead of the XDS100v2. (It's the gel file that is supplied by Logic PD for the eXperimenters kit.) This memory location is a PRSC status register, so why would it look like unmapped virtual memory?

Thanks,

0 ravindra mudreddy over 15 years ago in reply to JayVee

Prodigy 230 points

hi JV

i had also the same error , what i did was

As soon as power up the board i quickly luanch "debug active project" as soon as i can, because linux starts booting on my board this helped me solveing the error

if i do manual "connect" and "load program" i still the error you mentioned

you can try it out

Jv,Tommy

Now i getting error

"ARM9_0: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map."

i am using the following linker config

-l ..\evmomapl138_bsl.lib

-stack 0x00000800
-heap 0x00000800

MEMORY
{
   dsp_l2_ram:      ORIGIN = 0x11800000 LENGTH = 0x00040000
   shared_ram:      ORIGIN = 0x80000000 LENGTH = 0x00020000
   external_ram:    ORIGIN = 0xC0000000 LENGTH = 0x08000000
   arm_local_ram:   ORIGIN = 0xFFFF0000 LENGTH = 0x00002000
}

SECTIONS
{
   .text       > shared_ram
   .const      > shared_ram
   .bss        > shared_ram
   .far        > shared_ram
   .switch     > shared_ram
   .stack      > shared_ram
   .data       > shared_ram
   .cinit      > shared_ram
   .sysmem     > shared_ram
   .cio        > shared_ram
}

can you help me with this

ravindra

0 tlee over 15 years ago in reply to ravindra mudreddy

TI__Guru 62975 points

JV,

Have you updated your XDS100v2 CPLD? That has fixed a number of known emulator issues.

-Tommy

0 tlee over 15 years ago in reply to ravindra mudreddy

TI__Guru 62975 points

Ravindra,

I would recommend that you try the emulation boot mode (Switch7[8:5] = ON-OFF-OFF-ON) if you want to load a program to ARM. Depending on where you catch the Linux boot process, virtual memory may or may not be enabled, which would create memory-map issues.

Are you given any hints as to which variable(s) or function(s) are falling into the invalid memory section?

-Tommy

0 José Sacerio over 15 years ago in reply to Gerry Simmons

Intellectual 370 points

I have the same experience running CCS 4.1.2 and trying to connect to any of my Stellaris dev boards. I am running Vista 32 bits Home Premium. However, 4.1.2 runs OK under XP Pro SP3 if you remove the firewall block.

Any suggstions on how to get 4.1.2 working under Vista?

0 desouza over 15 years ago in reply to José Sacerio

TI__Guru**** 171309 points

José,

Please check the wiki topic below:

http://processors.wiki.ti.com/index.php/Vista_with_CCS

I've been using CCSv4 with Vista for a while now and it works fine.

Hope this helps,

Rafael

0 ravindra mudreddy over 15 years ago in reply to desouza

Prodigy 230 points

desouza, rafael

Are you sure with that, beacuse i dont have a ccs starting problem ,,,,,,,,,,,,,,,, i have problem in the memory section while loading

if confirm i will reinstall CCS in a different folder

tommy

i will try to update CPLD and let you know

and the question you asked about any hints of function or variables i am not getting any

can you please let me know with above linker config from which address to which address code,variables etcc are dumped , or send me the link from where i can read about this

ravindra

0 JayVee over 15 years ago in reply to ravindra mudreddy

Prodigy 180 points

I updated the XDS100V2 emulator's CPLD file, and I've tried this emulator on three different PCs with the same results. On the eXperimenters kit the emulator runs the GEL file until it tries to set the system clock to 300MHz and then it hangs up and times out. I tried setting the 'fast arm download' setting to 'off' and setting the timeout delay to 'very slow'. I get the same results on our new prototype design which has no linux code loaded. I tried changing the system clock/DDR clock settings from 300MHz/132MHz to 200MHz/126MHz but it still hangs. Should this problem be directed to Spectrum Digital or should it be handled through this forum?

0 JayVee over 15 years ago in reply to JayVee

Prodigy 180 points

After some more debugging I can see that the startup hang problem is not limited to the XDS100V2 emulator, because it also happens with the XDS510PP emulator as well. The XDS510USB emulator works fine. I've isolated the place in the Logic PD GEL file that hangs up. It's in this function:

device_PLL0(unsigned int CLKMODE, unsigned int PLLM, unsigned int POSTDIV,unsigned int PLLDIV1, unsigned int PLLDIV2, unsigned int PLLDIV3, unsigned int PLLDIV7 ) {

unsigned int i=0;

/* Clear PLL lock bit */

CFGCHIP0 &= ~(0x00000010);

/* Set PLLENSRC '0',bit 5, PLL Enable(PLLEN) selection is controlled through MMR */

PLL0_PLLCTL &= ~(0x00000020);

/* PLLCTL.EXTCLKSRC bit 9 should be left at 0 for Freon */

PLL0_PLLCTL &= ~(0x00000200);

/* Set PLLEN=0 to put in bypass mode*/

PLL0_PLLCTL &= ~(0x00000001);

/*wait for 4 cycles to allow PLLEN mux switches properly to bypass clock*/

for(i=0; i<PLLEN_MUX_SWITCH; i++) {;}

/* Select the Clock Mode bit 8 as External Clock or On Chip Oscilator*/

GEL_TextOut("\tbefore PLL0_PLLCTL read, in PLL config function.\n","Output",1,1,1);

PLL0_PLLCTL &= 0xFFFFFEFF;

GEL_TextOut("\tafter PLL0_PLLCTL read, in PLL config function.\n","Output",1,1,1);

PLL0_PLLCTL |= (CLKMODE << 8);

I added the GEL_TextOut lines at the end of this function, and the second GEL_TextOut line never executes, so the emulator hangs up waiting to read the PLL0_PLLCTL register. This is confirmed on the console printout that says the emulator was unable to read address 0x01C11100, which is the address of the PLL0_PLLCTL register. I tried increasing the 4 cycle delay in the function before the register read to 1000 cycles, but that didn't fix it.

My guess is that these emulators have trouble communicating with the target chip when its system clock is being punched around (not too surprising). The XDS510USB emulator can survive this though, maybe because it retries JTAG communications whereas the XDS100V2 and the XDS510PP don't or something like that. If you guys at TI want me to try anything else to help fix this let me know.

-JV

0 tlee over 15 years ago in reply to JayVee

TI__Guru 62975 points

JV,

Did you also enable Adaptive Clocking?

http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_turn_on_adaptive_clocking.3F

-Tommy

0 JayVee over 15 years ago in reply to tlee

Prodigy 180 points

Adaptive clocking fixed it, thanks Tommy!

0 ravindra mudreddy over 15 years ago in reply to JayVee

Prodigy 230 points

hi all

i have updated the cpld on my xds100v2 ,,, and landed in big trouble,,,, first i was not able to load my program,,,now i am not even able to connect to the target,,,, i am getting icecrusher errors

can any body help me

ARM9_0: Error connecting to the target: 0x80000240/-2062 @ marker 13008 Fatal Error during: Initialization, OCS, Cannot halt the processor

ARM9_0: Warning: 0x40000240/-1029 @ marker 11103 Warning during: Initialization, OCS, The ICECrusher register scan returned invalid data

ARM9_0: Warning: 0x40020244/-1029 @ marker 11103 Warning during: Register, Initialization, OCS, Internal, The ICECrusher register scan returned invalid data

ARM9_0: Warning: 0x40000240/-1029 @ marker 11103 Warning during: Initialization, OCS, The ICECrusher register scan returned invalid data

ARM9_0: Error connecting to the target: 0x80000240/-2062 @ marker 13008 Fatal Error during: Initialization, OCS, Cannot halt the processor

ARM9_0: Warning: 0x40000240/-1029 @ marker 11103 Warning during: Initialization, OCS, The ICECrusher register scan returned invalid data

ARM9_0: Error connecting to the target: 0x80000240/-2062 @ marker 13008 Fatal Error during: Initialization, OCS, Cannot halt the processor

ARM9_0: Warning: 0x40000240/-1029 @ marker 11103 Warning during: Initialization, OCS, The ICECrusher register scan returned invalid data

0 tlee over 15 years ago in reply to ravindra mudreddy

TI__Guru 62975 points

Ravindra,

Did you enable adaptive clocking?

-Tommy

0 DanRinkes over 15 years ago in reply to JayVee

TI__Expert 8055 points

I believe I have seen a similar issue on a different device, and JV is right.

Without getting into all of the details. the basic solution is to program the PLL through target code, not through GEL. This problem is limited to ARM processors, as far as I know. Two sources of the problem are mentioned below.

1) Programming the PLL from GEL is historically problematic as the core clock will cause RTCK to modulate and TCK may not be slow enough.

2) The TI on-chip adaptive clock support appears to have some issues if TCK is stopped/restarted. When doing TCK clock stop operation we normally turn off TI on-chip adaptive clocking and let the emulator do the right thing. The XDS100V2 is supposed to have this feature but I do not think it was ever enabled in USCIF for XDS100v2.

0 ravindra mudreddy over 15 years ago in reply to tlee

Prodigy 230 points

yes i did turn on adaptive clocking

0 ravindra mudreddy over 15 years ago in reply to DanRinkes

Prodigy 230 points

danr

so what are my options now

if i do simple connecte with out gel file(linux is already booting in the background) , i am getting the same errors

ravindra

0 DanRinkes over 15 years ago in reply to ravindra mudreddy

TI__Expert 8055 points

The only validated option is to boot code that initializes the PLL rather than trying to have GEL do it for you.

0 Brad Griffis over 15 years ago in reply to tlee

TI__Guru*** 125430 points

tlee said:
I would recommend that you try the emulation boot mode (Switch7[8:5] = ON-OFF-OFF-ON) if you want to load a program to ARM. Depending on where you catch the Linux boot process, virtual memory may or may not be enabled, which would create memory-map issues.

Did you ever try this suggestion from Tommy? I think using "emulation boot" plus "adaptive clocking" is key.

0 ravindra mudreddy over 15 years ago in reply to Brad Griffis

Prodigy 230 points

hi brad

i tried with it but the errors are same

i am getting the following errors only , only after i updated my CPLD in XDS100v2

ARM9_0: Error connecting to the target: 0x80000240/-2062 @ marker 13008 Fatal Error during: Initialization, OCS, Cannot halt the processor

ARM9_0: Warning: 0x40020244/-1029 @ marker 11103 Warning during: Register, Initialization, OCS, Internal, The ICECrusher register scan returned invalid data

ARM9_0: Warning: 0x40000240/-1029 @ marker 11103 Warning during: Initialization, OCS, The ICECrusher register scan returned invalid data

ARM9_0: Error connecting to the target: 0x80000240/-2062 @ marker 13008 Fatal Error during: Initialization, OCS, Cannot halt the processor

ARM9_0: Warning: 0x40020204/-1026 @ marker 11112 Warning during: Register, OCS, Internal, The resource has not been claimed

after i do the multiple "retry" "retry",,,,,,device is shown as connected in CCS

but when i load the program i get the below error and my program is loaded

ARM9_0: File Loader: Data verification failed at address 0x80000000 Please verify target memory and memory map.

ARM9_0: Unable to terminate memory download: 0x00000004/-2030 @ marker 583696133 Error during: Register, Access to an unknown or invalid register was attempted.

Error found during data verification.

Ensure the linker command file matches the memory map."

1) can you please help me with this,,,

2) is there any way that i role back my CPLD version to the orignal thing

thanks & regards

ravindra

0 prat over 14 years ago in reply to ravindra mudreddy

Expert 1115 points

Hello friend,

Give a try to the following also. They may help you as it worked for me.

1. ARM9_0: File Loader: Data verification failed at address 0x80000000 Please verify target memory and memory map.

This can be due to to improper gel file.

Try loading the latest gel files available from the vendor for your board for your CCS version. Else look at OMAP data sheet, note down the memory locations corresponding to 0x80000000 (shared memory) , make corrections this gel file and save it with different name and use. It should work.

2) is there any way that i role back my CPLD version to the orignal thing

Please contact spectrumdigital regarding this.

All the best

Prat

Code Composer Studio™︎

Code Composer Studio forum

OMAP L138 connecting problem with CCS 4.1.2