Post Go back to editing

cldp Error: failed to resolve symbol "AFP_BreakReady".

Iv'e seen this issue pop up around here for other target configurations, but haven't found any solution appliccable to my problem.

I've got a small prototype board using the ADSP-21584, and I have a small test application that runs successfully through the ICE-1000 from CrossCore 2.8.0.0. (in the Debug build configuration - with artifact type set to executable)

In the Release Build configuration I changed the artifact type to loader, 

In the loader configuration I set my test application on Booting Core == Core1(SHARC), and just a empty main executable on the second core.

Also on this Release configuration I've added the Post-Build step, where cldp is called.

As driver I started with the OTPProgrammer_Core1 from the "CrossCore Embedded Studio 2.8.0\SHARC\Examples\Device_Programmer\ADSP-SC58x" folder.

And of course my testproject loader artifact as file to download.

Upon building everything seems fine until the post-build step, that halts with:

Error: failed to resolve symbol "AFP_BreakReady".
Error: driver load failed.

Please advice on what I need to do to get around this problem, I'm in a bit of a rush here to get this test done.

PS

I also used the log switch on the cldp commandline, which produced the following output.

Connect()
[I] Target: Emulation Debug Target
[I] Platform: ADSP-21584 via ICE-1000
[I] Processor:
EMU[ emutarget ]: Connecting to emutarget family library...
EMU[ emutarget ]: Connecting to emulator library...
EMU[ emutarget ]: Connecting to processor Device 0 ( ADSP-21584 )...
EMU[ emucoresharc11 ]: Debug interface is JTAG [procID=1156853866, coreID=59530020]
EMU[ emucoresharc11 ]: Detected IDCODE: 0x228080cb [procID=0, coreID=1]
EMU[ emutarget ]: Connected to emutarget family library version 7.8.0.1
successfully

>> StateChange()
EMU[ emutarget ]: Connected to ICE-1000 emulator library version 7.7.0.0 successfully
EMU[ emutarget ]: Connected to Device 0 ( ADSP-21584 ) silicon revision 1.0 successfully
EMU[ emutarget ]: Connected to Core 1 (SHARC) [proc=0/core=0] successfully
[I] State: Running
[I] Reason: Client Request
[I] ProcId: 0

>> StateChange()
[I] State: Halted
[I] Reason: Client Request
[I] ProcId: 0
EMU[ emucoresharc11 ]: Detected IDCODE: 0x228080cb [procID=0, coreID=2]
EMU[ emutarget ]: Connected to Core 2 (SHARC) [proc=0/core=1] successfully

>> StateChange()
[I] State: Running
[I] Reason: Client Request
[I] ProcId: 1

>> StateChange()
[I] State: Halted
[I] Reason: Client Request
[I] ProcId: 1
[T] 2.17369 seconds

Reset()
[I] ProcId: 0
[I] Wait: 1

>> StateChange()
[I] State: Reset
[I] Reason: Client Request
[I] ProcId: 0

>> StateChange()
[I] State: Halted
[I] Reason: Client Request
[I] ProcId: 0
[T] 0.16933 seconds

GetTargetState()
[I] ProcId: 0
[O] State: 3
[T] 0.00003 seconds

LoadProgram()
[I] ProcId: 0
[I] FileName: OTPProgrammer_Core1.dxe
[I] SymbolsOnly: 0
[T] 0.66287 seconds

EvaluateExpression()
[I] ProcId: 0
[I] Expression: $RCU0_MSG
[I] Format: Integer
[O] Result: 6685184
[T] 0.00244 seconds

SetExpression()
[I] ProcId: 0
[I] Expression: $RCU0_MSG
[I] Value: 8258048
[T] 0.00141 seconds

GetSymbolsByName()
[I] ProcId: 0
[I] Name: AFP_BreakReady
[O] Symbols Found: 0
[T] 0.00022 seconds

Disconnect()
EMU[ emucoresharc11 ]: Disconnecting from Device 0
EMU[ emucoresharc11 ]: Disconnecting from Device 0
[T] 0.35018 seconds

  • Hi,


    We understand that you have already contacted our private support.
    Please continue the discussion there. We will post the final response here for others to benefit.

    Regards

    Reva

  • Hi,

     

    We understand that you have already contacted our private support. Please continue the discussion there. We are posting the response here for others to benefit.

    Can you please confirm that you are not trying to program the OTP memory of the ADSP-21584 processor. If so please use Device programmer available in the BSP package.

    You can download ADSP-SC5XX BSP from the below link
    http://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/EVAL-ADSP-SC584.html#eb-relatedsoftware

    After installation you can find flash driver for Winbond W25Q128FV part in the below path:
    <Installation path>\ADSP-SC5xx_EZ-KIT_Lite-Rel2.0.2\ADSP-SC5xx_EZ-KIT\Examples\Device_Programmer\sc584\sharc\sc584_w25q128fv_dpia_Core1\sc584_w25q128fv_dpia_Core1.dxe

    Below is the sample CLDP command line:
    "C:\Analog Devices\CrossCore Embedded Studio 2.8.0\cldp.exe" -proc ADSP-21584 -core 1 -emu 2000 -driver "C:\Analog Devices\ADSP-SC5xx_EZ-KIT_Lite-Rel2.0.2\ADSP-SC5xx_EZ-KIT\Examples\Device_Programmer\sc584\sharc\sc584_w25q128fv_dpia_Core1\sc584_w25q128fv_dpia_Core1.dxe" -cmd prog -erase affected -format hex -file LoaderFile.ldr

    Also please note that the flash drivers we ship with our tools are specific to our EZ-Kit boards. For example, the sc58x_w25q128fv_dpia driver is specific to the SC58x and the Winbond W25Q128FV part. We would strongly recommend you confirm the exact flash part you are working with. If you discover you are working with a different part you will need to modify the existing driver.

    We provide documentation for the Device Programmer API, which describes the commands the Flash Programmer Drivers require to perform the Flash accesses.

    This documentation is available at help > CrossCoreRegistered Embedded Studio 2.8.0 > Integrated Development Environment > Working with Bootable and Non-bootable Files > Device Programmer > Custom Device Drivers

    We are aware of many customers who have successfully modified our flash drivers to suit different flash parts.

    Regards

    Reva

  • This question has been assumed as answered either offline via email or with a multi-part answer. This question has now been closed out. If you have an inquiry related to this topic please post a new question in the applicable product forum.

    Thank you,
    EZ Admin