Hello,
I have a bootable SPI flash. It appears up and run after power on.
I'm NOT able to load program in debugging mode. I have to turn off SPI_Boot mode, say put in UART_Boot, in order to do debugging.
It appears to me the XDS not able to stop a running CPU and take over the control as it's supposed to do
I'm using XDS100v2 from Digital Spectrum and OMAP-L138 Experimenter board ?
Q1 : How to have XDS control a running CPU without changing boot mode ?
Thanks,
~Duy-Ky
It's extremely frustrating to work with very unstable development tool like what I'm experiencing with CCS-v5 !!!!
Now, no matter what I'm doing, it hangs forever in start of debugging. Below is screen capture of InitScript using GEL file, I guess
ARM9_0: Output: Memory Map Cleared.ARM9_0: Output: ---------------------------------------------ARM9_0: Output: Memory Map Setup Complete.ARM9_0: Output: ---------------------------------------------ARM9_0: Output: Enabling Full EVM PSCs...ARM9_0: Output: PSC Enable Complete.ARM9_0: Output: ---------------------------------------------ARM9_0: Output: PLL0 init done for Core:300MHz, EMIF:25MHzARM9_0: Output: mDDR initialization is in progress....ARM9_0: Output: PLL1 init done for DDR:132MHzARM9_0: Output: mDDR init for 132 MHz is doneARM9_0: Output: ---------------------------------------------
HANG here forever
Even with boot image, ocassionally I had successful loading and debugging. When it failed, I had to switch to UART_Boot, and it worked for few times.
Now, it stops working totally, no matter what I did, like cycle the power, plug/unplug XDS, clode/open CCS-v5, I did dozen times. It really frustrating
I do not believe anything to do with XDS and boot image on the board, as I have no problem at all in debugging for both CCS-v4 and CCS-v5
Now, all suddently it stops working even after I recover the original image come with the board. I'm able to see all output on Terminal as I saw before.
It still stops working.
Q1 : WHY it stops working in exactly the same original condition, I believe ???
Q2 : Does CCS-v5 store some secret info somewhere to prevent it from working ???
Now I'm able to debug a SPI-bootable device in UART-boot mode after creating a new work-space.
So CCSv5 corrupted the workspace is the root cause of my previous weird failure.
So far, I have used a dozen of debugger, from low-end like McCraiggor to high-end one like LauterBach, including several embedded Linux like BDI3000, ... all are able to take control of running CPU once they start debugging.
Now CCSv5 appears to me not able to control a running CPU in debugging job.
After start debugging, I got console output
ARM9_0: Output: Memory Map Cleared.ARM9_0: Output: ---------------------------------------------ARM9_0: Output: Memory Map Setup Complete.ARM9_0: Output: ---------------------------------------------ARM9_0: Output: Enabling Full EVM PSCs...ARM9_0: Output: PSC Enable Complete.ARM9_0: Output: ---------------------------------------------ARM9_0: Output: PLL0 init done for Core:300MHz, EMIF:25MHzARM9_0: Output: mDDR initialization is in progress....ARM9_0: Output: PLL1 init done for DDR:132MHz
It hangs there forever with a popup window "GEL Expression: On TargetConnect()"
So it seems to me it keeps trying to connect the target, but not able to get connected.
I have to cancel it after a very long waiting.
I then have another popup window "Load program Error" with message " a data verification error occured, file load failed"
Once I click "OK", it closes the debug window and back to compile window.
I add the TI AM1808.DEL as InitScript in Configuration
So
Q1 : Do I have to set any option in CCS-v5 to solve this problem ?
Q2 : Do I have to change GEL to solve this problem ?