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.

attempting to make MMC/SD card project, can't link

Other Parts Discussed in Thread: SYSBIOS

So to start i made a new SYSBIOS project and pulled in the .c files for the MMC/SD FAT example.  i deleted the original main.c and app.cfg.  when i go to build the project with only the example files in the project i get these errors

Description Resource Path Location Type
can't locate the package 'ti.sdo.utils' along the path: 'C:/CCSv5/bios_6_33_05_46/packages;C:/CCSv5/biospsp_03_00_01_00/drivers;C:/PROGRA~2/TEXASI~1/dsplib_c674x_3_1_0_0/packages;C:/CCSv5/edma3_lld_02_11_04_01/packages;C:/CCSv5/ccsv5/ccs_base;C:/CCSv5/xdctools_3_23_03_53/packages;..;'. Ensure that the package path is set correctly. mmcsdSample.cfg /mmcsdsample 27 C/C++ Problem

Description Resource Path Location Type
xdc.PACKAGE_NOT_FOUND: can't locate the package 'ti.sdo.utils' along the path: 'C:/CCSv5/bios_6_33_05_46/packages;C:/CCSv5/biospsp_03_00_01_00/drivers;C:/Program Files (x86)/Texas Instruments/dsplib_c674x_3_1_0_0/packages;C:/CCSv5/edma3_lld_02_11_04_01/packages;C:/CCSv5/ccsv5/ccs_base;C:/CCSv5/My Projects/mmcsdsample/.config/;C:\CCSv5\xdctools_3_23_03_53\packages;'. Ensure that the package path is set correctly. mmcsdSample.cfg /mmcsdsample Configuration Validation XDCTools Configuration Marker

so what is "ti.sdo.utils"?

  • I’m not sure which MMC/SD FAT example you are using, but from the error message it seems that you need to select an “IPC” product in the project properties (the ti.sdo.utils package is in the IPC product).  

    If you right click on the project, select properties, general, and then click on the RTSC tab you should see something similar to the following.  



    I'm thinking that there is no checked box for an Inter-processor Communication product install, but if you select one of the IPC products, clean and rebuild the project then this error will go away…

    Scott

  • Hi Cobsonchael,

    As per the error log, it looks like you are using the BIOS PSP 03.00.01.00, am i right?

    Are you trying to build the example mmcsd application placed in the path "biospsp_03_00_01_00\drivers\examples\evm6748\mmcsd_fatfs"?  If yes, then, please check the "biospsp_03_00_01_00\makerules\env.mk" file for the appropriate path for all the tools (especially ipc_PATH). And also refer the userguide (C6748_BIOSPSP_Userguide.pdf) section 1.5 for all the environment variables to be set.

    Regards,

    Sandeep K

  • well using the IPC made that error go away, but i now have all sorts of linking errors for routines that i thought would be included in the PSP drivers. below is a list of functions that are not linking in.

    i am using my own project for this because there are no MMC/SD projects.  there are 2 .c files that would make up a project but it does not include a .project file so i had to make my own project and add in the C files. however, when i open up the ONLY project that comes with the psp drivers (the i2c project)  and that hasd linking errors as well.  this makes me think that i am missing something. either some library or an include path.  i already set up the UTILS_INSTALL_DIR, EXTERNAL_SW_ROOT, and INTERNAL_SW_ROOT. i didn't see anything else i am supposed set.

    _PSP_blkmediaFATfsRegister ./src/mmcsdSample_io.obj

    _PSP_blkmediaFATfsUnregister ./src/mmcsdSample_io.obj

    _PSP_mmcsdCheckCard ./src/mmcsdSample_io.obj

    __args_main C:\CCSv5\xdctools_3_23_03_53\packages\ti\targets\rts6000\lib\boot.a674<boot.o674>

    __divu C:\CCSv5\bios_6_33_05_46\packages\ti\sysbios\lib\instrumented_674\sysbios\sysbios.lib<BIOS.obj>

    __divul C:\CCSv5\bios_6_33_05_46\packages\ti\sysbios\fatfs\lib\release\ti.sysbios.fatfs.a674<ff.o674>

    __divull C:\CCSv5\bios_6_33_05_46\packages\ti\sysbios\lib\instrumented_674\sysbios\sysbios.lib<BIOS.obj>

    __ftable C:\CCSv5\xdctools_3_23_03_53\packages\ti\targets\rts6000\lib\ti.targets.rts6000.a674<SysStd.o674>

    __nop C:\CCSv5\My Projects\mmcsdsample\Debug\configPkg\package\cfg\mmcsdSample_p674.o674

    __register_lock C:\CCSv5\My Projects\mmcsdsample\Debug\configPkg\package\cfg\mmcsdSample_p674.o674

    __register_unlock C:\CCSv5\My Projects\mmcsdsample\Debug\configPkg\package\cfg\mmcsdSample_p674.o674

    __remu C:\CCSv5\bios_6_33_05_46\packages\ti\sysbios\lib\instrumented_674\sysbios\sysbios.lib<BIOS.obj>

    _abort C:\CCSv5\xdctools_3_23_03_53\packages\ti\targets\rts6000\lib\ti.targets.rts6000.a674<System.o674>

    _add_device C:\CCSv5\My Projects\mmcsdsample\Debug\configPkg\package\cfg\mmcsdSample_p674.o674

    _atexit C:\CCSv5\xdctools_3_23_03_53\packages\ti\targets\rts6000\lib\ti.targets.rts6000.a674<System.o674>

    _configureMmcsd0 ./src/mmcsdSample_main.obj

    _exit C:\CCSv5\xdctools_3_23_03_53\packages\ti\targets\rts6000\lib\ti.targets.rts6000.a674<System.o674>

    _fclose ./src/mmcsdSample_io.obj

    _fflush C:\CCSv5\xdctools_3_23_03_53\packages\ti\targets\rts6000\lib\ti.targets.rts6000.a674<SysStd.o674>

    _fopen ./src/mmcsdSample_io.obj

    _fread ./src/mmcsdSample_io.obj

    _fseek ./src/mmcsdSample_io.obj

    _fwrite ./src/mmcsdSample_io.obj

    _memcpy C:\CCSv5\My Projects\mmcsdsample\Debug\configPkg\package\cfg\mmcsdSample_p674.o674

    _memset C:\CCSv5\My Projects\mmcsdsample\Debug\configPkg\package\cfg\mmcsdSample_p674.o674

    _mmcsdPscInit C:\CCSv5\My Projects\mmcsdsample\Debug\configPkg\package\cfg\mmcsdSample_p674.o674

    _mmcsdStorageDeInit ./src/mmcsdSample_main.obj

    _mmcsdStorageInit ./src/mmcsdSample_main.obj

    _printf ./src/mmcsdSample_main.obj

    _putchar C:\CCSv5\xdctools_3_23_03_53\packages\ti\targets\rts6000\lib\ti.targets.rts6000.a674<SysStd.o674>

  • Can you please refer the demo video clip "C:\Program Files\Texas Instruments\biospsp_03_00_01_00\docs\C6748\C6748_BIOSPSP_CCSProjectCreation.wmv" available in the PSP to create the CCS project?

    Regards,

    Sandeep K 

  • i guess i must have missed that file (that or i am not used to looking for media files when i look for documentation).  that did fill in the blanks for my linking errors.

    it does, now, provide me with additional questions.

    1) what is the point of installing the EDMA module, the PSP module, if you have to go out and point to the repository manually anyway? in the video they had those modules installed, but instead of just checking the box they had to manually add the repositories.  what is the point of the module if you don't use them like they seem to be meant to be used?

    2) WHY are the drivers not a module you can select the RTSC check box? why do i have to add every single set of driver library myself? why is this a manual thing?  this has to be the least intuitive part of this process, even outside of the fact that the drivers are in a spot you absolutely need the documentation to find and know which files you want.  i swear there are more "driver" folders than you can shake a stick at.  i don't understand why the drivers are not considered a module and we can't just look into the "Available Products" box and select "Use XXXX" to use those drivers.  you claim you want to make this an easy experience but this has been a pain since i have started this task.

  • Yes, i agree with your concern. We had this RTSC support earlier with all the driver supporting IDriver model. To support this each module (driver) needs to have its own .xdc file and .xs file. As per the user feedback, we realized that the user is more familiar in modifying/understanding the .h/.c file instead of .xdc/.xs file.

    Note: The xdc command would convert the .xdc to .h file.

    And also, gmake is more generic than the xdc command.

    So, considering the above concerns from the end user, we decided to use the IOM driver model along with the gmake support.

    Any way, thanks for your valuable feeedback.

    Regards,

    Sandeep k