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.

PDK rebuild for AM3517

Other Parts Discussed in Thread: AM3517

Hi all,

I've been working on building the PDK for my AM3517 project in windows and I've run into some trouble. I've installed the latest CCS as well as downloaded the latest SDK (3.0.0.4 at the time of this post). I've followed the steps outlined here: http://processors.wiki.ti.com/index.php/Rebuilding_The_PDK but haven't been successful in building the complete sdk,

I make it through much of the build without issues but when gmake tries to make the osal directory it throws an error and gmake execution stops. here is the error:

gmake[5]: *** No rule to make target 'cp15.asm', needed by '/ti/PDK_AM~1/packages/ti/binary/ti/osal/osal_nonos/obj/am335x/a8/release/cp15.oa8fg'. Stop.

all of the builds prior to this are successful, and there are no attempts to build any directories after this error.

I'm able to make the example projects but without the complete sdk they fail to build. Having not completed the full sdk generation, I'm not sure if this is a problem, but the setpenv.bat printout shows environment variables IPC_INSTALL_PATH, IMGLIB_INSTALL_PATH, and UIA_INSTALL_PATH that point to non-existent directories. My expectation right now is that the gmake command, if completed successfully, will install files in those directories since I have not found a way to install them manually.

I haven't been able to find anyone else with this problem, and since the CCS install was fresh specifically for this project I can't think of what would be wrong with my build environment.

Does the community have any thoughts?

Best,

Don

  • I've moved your thread to the device forum.

    Todd
  • I've been able to build the remaining parts of the PDK (profiling, pruss, spi, starterware, and uart) by individually invoking make using the gmake <component> command over each of them and have been able to confirm that there are not any further problems, just the one mentioned in the initial posting.

    By building the other components I have been able to bring down the total number of errors in the example project I'm interested in building to one. I'm digging into the makefiles now and if I have any updates I will be sure to post them.

    Don

  • Don,

    Can you confirm the part number you are using. We don`t support Processor SDK RTOS for AM3517 device. Did you mean AM335x device?

    Regards,
    Rahul
  • Rahul,

    I am using the 3517. I was basing this off of the conversation I had earlier this year here:

    e2e.ti.com/.../1745479

    Will I be able to look at the SDIO example or am I heading to a dead-end? What would you suggest?

    Don
  • Don,

    Sorry for the delayed response on this. The starterware package for AM335x is tested only with the AM335x based platforms and not with AM3517 platform. The 2 devices have the same SDIO/MMC interface so you can use the driver as reference code however from SOC perspective the pinmuxing, power management and clocking may differ so you will need to modify those portions of the example code to get the SD interface to work the way you intend it to work.

    Regards,
    Rahul
  • Thanks for the information Rahul. It sounds like it would still be useful for me to build this project so I can take a look at how the SDIO is implemented. I'll continue to pursue this with the pin and clock considerations in mind.

    That said, do you have any ideas as to why I am unable to build the project? I haven't been successful yet.

    Best,

    Don