Using the latest NDK with a custom C6455 board

Hi Andrew Olson1,

Andrew Olson1 said:

I understand that the NSP ships with drivers for the OMAP138.  Would it be enough to rebuild those using xdc and config.bld for the C64 target?

I'm not sure how different these 2 drivers are, they may be similar but I would recommend to stick with the 6455 driver from NDK 2.0.0 (that's the latest version of the 6455 driver).

Andrew Olson1 said:

I've also found this post http://e2e.ti.com/support/embedded/bios/f/355/t/199858.aspx which talks about migrating from ndk 2.0 to ndk 2.21.  Would this be the correct approach to take?  Would there be functions in some of the other files that I would have to modify?  Would I have to rebuild the c6455 driver from ndk2.0.0.0 to work with sys\bios and the latest NDK?  How would that be done.

As you found in that post, you need to modify it and rebuild in order to use it with BIOS 6.x. I think the main issue is there are some BIOS 5.x APIs that are being referenced that are unneeded, and some interrupt related code that may need to change.

You could use the NSP that you have to rebuild it and build it for C64 as you guessed.  You might run into some hurdles, but you can still try.

Probably, the easiest way is to copy the files into your project and rebuild them like that.

Andrew Olson1 said:

  I'm trying to get the NDK examples running on our custom C6455 board.

One suggestion is to build and run the 6455 client example that ships in NDK 2.0.0.  The example will be for BIOS 5.x and will use the BIOS 5.x compatible driver that shipped in NDK 2.0.0.  this example works out of the box on a 6455 board, so doing this could help you validate that driver on your custom board.  Of course, it means that you would need to port the NDK 2.0.0 client project (made for CCS 3.x) to CCS 5.x (basically create a new project in CCS 5 and then bring all of the client example files, compiler and linker settings into the CCS 5.x project).

]Steve