• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 98 subscribers
  • Views 1615 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS: AM57x PDK 1.0.9 compile error

Michelle Le
Prodigy 60 points
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hi

I am trying to update my PDK liberary form 1.0.5 to 1.0.9. I download the latest SDK. My code comples fine with PDK_1_0_5, but it occurs the following error with PDK_1_0_9. Does anyone have idea on this?

akefile:165: recipe for target 'ICB_FW_LP.out' failed
C:\ti\pdk_am57xx_1_0_9\packages\ti\drv\mmcsd\lib\am572x\a15\release\ti.drv.mmcsd.aa15fg(MMCSD_v1.oa15fg): In function `MMCSD_v1_open':
C:\ti\PDK_AM~1\packages\ti\drv\mmcsd/src/v1/MMCSD_v1.c:736: undefined reference to `MuxIntcP_create'
collect2.exe: error: ld returned 1 exit status
gmake[1]: *** [ICB_FW_LP.out] Error 1
gmake: *** [all] Error 2
makefile:161: recipe for target 'all' failed

  • 0
    TI__Guru**** 463941 points
    Hello,
    I will move this thread to the Sitara forum. The experts there can help you best.

    Thnaks
    ki
  • 0 in reply to Ki
    TI__Guru* 95265 points
    Hi,

    This indicated the MuxIntcP_create is missing, when linking, do you have OSAL library: ti.osal.aa15fg?

    Regards, Eric
  • 0 in reply to lding
    Prodigy 60 points

    Hi Eric

    This is my Linker settings. If we need that libarary, I am confused why pdk 1.0.5 is working for me. Thanks

  • 0 in reply to Michelle Le
    TI__Guru* 95265 points
    Hi,

    The OSAL library is not linked from the libraries you showed, but it is linked from the .cfg file. For our MMCSD driver, there are many test examples in SYSBIOS, it has a .cfg file, typically with:

    /* Load the OSAL package */
    var osType = "tirtos"
    var Osal = xdc.useModule('ti.osal.Settings');
    Osal.osType = osType;
    Osal.socType = socType;

    This is how the OSAL library is linked. Can you double check?

    Regards, Eric
  • 0 in reply to lding
    Prodigy 60 points

    Hi Eric

    It is linked in my .cfg file.  Otherwise, it has to be "ti.osal.Settings" instead of "ti.osal"?

  • 0 in reply to Michelle Le
    TI__Guru* 95265 points

    Hi,

    I tried the AM57x 1.0.9, there are several MMCSD test examples. I tried to build one of them, the .cfg has:

    /* Load the OSAL package */

    var osType = "tirtos"

    var Osal = xdc.useModule('ti.osal.Settings');

    Osal.osType = osType;

    Osal.socType = socType;

    When building:

    configuring mmcsd_evm.xa15fg from package/cfg/mmcsd_evm_pa15fg.cfg ...

    generating custom ti.sysbios library makefile ...

    Linking with library ti.board:./lib/evmAM572x/a15/release/ti.board.aa15fg

    Linking with library C:/ti/pdk_am57xx_1_0_9/packages/ti/drv/pm/./lib/am572x/a15/release/pm_hal.aa15fg

    Linking with library C:/ti/pdk_am57xx_1_0_9/packages/ti/drv/pm/./lib/am572x/a15/release/pm_lib.aa15fg

    Linking with library C:/ti/pdk_am57xx_1_0_9/packages/ti/drv/pm/./lib/am572x/a15/release/pm_rtos.aa15fg

    Linking with library ti.drv.i2c:./lib/a15/release/ti.drv.i2c.aa15fg

    Linking with library ti.drv.uart:./lib/a15/release/ti.drv.uart.aa15fg

    Linking with library ti.drv.gpio:./lib/a15/release/ti.drv.gpio.aa15fg

    Linking with library ti.drv.mmcsd:./lib/a15/release/ti.drv.mmcsd.profiling.aa15fg

    Linking with library ti.utils.profiling:./lib/a15/release/ti.utils.profiling.aa15fg

    Linking with library ti.osal:./lib/tirtos/am572x/a15/release/ti.osal.aa15fg

    Linking with library ti.csl:./lib/am572x/a15/release/ti.csl.aa15fg

    Starting build of library sources ...

    making C:/ti/pdk_am57xx_1_0_9/packages/ti/drv/mmcsd/test/am572x/armv7/bios/src/sysbios/sysbios.aa15fg

    I have the right library linked. Yes, please use above setting.

    Regards, Eric

  • 0 in reply to lding
    Prodigy 60 points
    Hi Eric
    Thanks for your help. This issue has been fixed after I specify the Osal soc type