• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 3832 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCSv4.2.1 C6472: Trouble Writing Memory Block at 0x78000008 ..... and 0x29a0100

Eddie3909
Guru 10385 points
Other Parts Discussed in Thread: CCSTUDIO

Hi

I get the error below each time I try to connect to the C6472. (View -> Others -> PDE Runtime -> Error Log)

 

I'm using a Blackhawk 560 USB and my co-workers are using the XDS 510 USB PLUS.

This memory location 0x78000008 is the DDR SDCFG register and location 0x029A0100 is the PLLCTL register. We should not be having an write issues with these memory locations. Especially since the gel file is setting up the PLLM to 25 which is for 625 MHz and not the 700 MHz the board is rated for.

 

I have checked with several other co-workers and they too are getting this error. We are using the stock evm6472.gel file that came with the C6472.

My EVM's PCB is 17 - 00065 - 05.

My co-workers have 17 - 00065 - 04

 

eclipse.buildId=4.2.1.00004
java.version=1.5.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86 -clean
This is a continuation of log file C:\Work\CCSv4_256pntFft_0\.metadata\.bak_0.log
Created Time: 2011-01-25 10:20:36.005

Error
Mon Jan 31 10:50:49 PST 2011
Error: IcePick_C_0: GEL: Error while executing OnTargetConnect(): Target failed to read memory at 0x029A0100.

eclipse.buildId=4.2.1.00004
java.version=1.5.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

Error
Sun Jan 30 17:35:54 PST 2011
Error: IcePick_C_0: Trouble Writing Memory Block at 0x78000008 on Page 0 of Length 0x4

eclipse.buildId=4.2.1.00004
java.version=1.5.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86 -clean
This is a continuation of log file C:\Work\CCSv4_256pntFft_0\.metadata\.bak_0.log
Created Time: 2011-01-25 10:20:36.005

Error
Mon Jan 31 09:48:49 PST 2011
Error: IcePick_C_0: Trouble Reading Memory Block at 0x29a0100 on Page 0 of Length 0x4

  • 0
    TI__Guru* 84110 points

    Eddie,

    Have any of you tried the on-board emulator on the EVM?

    Try checking or changing the boot mode pins. If something external is holding the DSP in reset during a boot process, it might cause problems. Boot mode 0000 = Immediate boot would be a good mode to choose to take that out of the equation.

    Please let us know what results you get.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Guru 10385 points

    Hi

    I changed to boomode 0000 (SW2 pins 1 - 4 are set off). All other SW1 and SW2 pins are set to the board defaults. No change. So I switched to the XDS100.

    When I launch the XDS100, I get green errors below. When I connected, I got a pop up saying Trouble Reading Register CSR Error 0x00000004/-1060, Error during: Register....blah blah blah.... It is recommended to RESET emulator. Great!

    The console displayed the error in red below when I tried again and connected.

    I reset the board and launched the XDS100 again. This time it gave the same error log output as the XDS510. (i.e. It gives me six of each of these shown in purple): 

    x6 : Error: IcePick_C_0: GEL: Error while executing OnReset(0): target access failed.: An exception stack trace is not available.

    x6 :: Error: IcePick_C_0: GEL: Error while executing OnTargetConnect(): Target failed to read memory at 0x029A0100..: An exception stack trace is not available.

    x6: Error: IcePick_C_0: Trouble Reading Memory Block at 0x29a0100 on Page 0 of Length 0x4 .: An exception stack trace is not available.

    x6: Error: IcePick_C_0: Trouble Writing Memory Block at 0x78000008 on Page 0 of Length 0x4 .: An exception stack trace is not available.

    Why are there six of each error when I'm only highlighting one core before I select the "connect" button? Its as if the evm6472.gel is being run on all cores, yet I checked my ccxml file and only one core is supposed to be initialized with  evm6472.gel. The others are set to be initialized with evm6472-MemoryMap.gel.

    I attached my ccxml if that helps. 3660.EVM6472_BHUSB560M.zip (had to zip it because I get "File type not allowed" for almost every other extension I try to upload).

    C64XP_0: Trouble Writing Memory Block at 0x78000010 on Page 0 of Length 0x4: Error 0x00000002/-1175 Error during: Memory,  Security Violation Error when using IM unit.  
    C64XP_0: GEL: Error while executing OnTargetConnect(): target access failed.
    C64XP_0: Trouble Reading Register CSR: Error 0x00000004/-1060 Error during: Register,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target. 

    Unhandled event loop exception: An exception stack trace is not available.

    and (what has Mozilla got to do with CCS??????)

    org.eclipse.swt.SWTException: Failed to execute runnable (org.mozilla.xpcom.XPCOMException: Java/XPCOM bridge: exception while executing submit() with parameterorg.mozilla.xpcom.internal.XPCOMJavaProxy$3@1516c02.
    org.mozilla.xpcom.XPCOMException: The function "registerViewForRefresh" returned an error condition  (0x80070057)  (0x80004005))
        at org.eclipse.swt.SWT.error(SWT.java:3374)
        at org.eclipse.swt.SWT.error(SWT.java:3297)
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:97)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
        at org.eclipse.core.launcher.Main.run(Main.java:996)
        at org.eclipse.core.launcher.Main.main(Main.java:971)
    Caused by: org.mozilla.xpcom.XPCOMException: Java/XPCOM bridge: exception while executing submit() with parameterorg.mozilla.xpcom.internal.XPCOMJavaProxy$3@1516c02.
    org.mozilla.xpcom.XPCOMException: The function "registerViewForRefresh" returned an error condition  (0x80070057)  (0x80004005)
        at org.mozilla.xpcom.internal.XPCOMImpl$XPCOMCallExecutor.submit(XPCOMImpl.java:93)
        at org.mozilla.xpcom.internal.XPCOMJavaProxy.invoke(XPCOMJavaProxy.java:239)
        at $Proxy53.registerViewForRefresh(Unknown Source)
        at com.ti.debug.engine.impl.DspUser.registerViewForRefresh(DspUser.java:2203)
        at com.ti.debug.engine.impl.DspUser.registerViewForRefresh(DspUser.java:96)
        at com.ti.ccstudio.debug.engine.proxies.PxyDspUser.registerViewForRefresh(PxyDspUser.java:1091)
        at com.ti.dvt.cceideadapter.CCEIDECPUAdapter.registerView(CCEIDECPUAdapter.java:865)
        at com.ti.dvt.ideadapter.IDECPU.registerView(IDECPU.java:1019)
        at com.ti.dvt.util.SolutionHelper$4.switchPane(SolutionHelper.java:938)
        at com.ti.dvt.util.SolutionHelper$4.run(SolutionHelper.java:852)
        at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)

        ... 20 more

  • 0 in reply to Eddie3909
    TI__Guru* 84110 points

    You will have a better chance at a good answer in the Code Composer forum. We hardware guys go bleary-eyed with dumps like those, and your problem seems closer to the CCS and emulation side than the device side. I hope this does not get bounced back-and-forth.

    Eddie said:
    Why are there six of each error when I'm only highlighting one core before I select the "connect" button? Its as if the evm6472.gel is being run on all cores, yet I checked my ccxml file and only one core is supposed to be initialized with  evm6472.gel. The others are set to be initialized with evm6472-MemoryMap.gel.

    Which single core have you highlighted to connect? The messages you show all start with "x6" but include "ICEPICK_C_0".

    To which core do you have the evm6472.gel assigned?

    RandyP

  • 0 in reply to RandyP
    Guru 10385 points

    RandyP said:
    We hardware guys go bleary-eyed with dumps

    Thats how I feel!

    RandyP said:
    Which single core have you highlighted to connect? The messages you show all start with "x6" but include "ICEPICK_C_0".

    ICEPIC_C_0 is the "ICEPick_C Router" according to the ccxml file. I am connecting to C64XP_0 which is the DSP on ccxml defined "port 0x10", where the ports go from 0x10 to 0x15 (as I type this with the deer in the headlights look)

    The evm6472.gel is assigned to C64XP_0 (port 0x10)

    Cheers