• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 1187 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.

DM6437 compatibility with NDK 2.0

Rob Beck
Intellectual 970 points

Other Parts Discussed in Thread: CCSTUDIO

Just got a nice shiny EVMDM6437 media board. Ran the demo OK, H264 file decode, works fine.

 

Now what I am doing is porting a C6457 application front end based upon NDK 2.0 to the DM6437 EVM.

I have got the DM6437 to printf that it added the network and has a link "full duplex on PHY 0". However, I cannot ping it or connect using an internet browser (HTTP index page) which seems unusual.

I then added to the project the NSP source files for the DM6437 from NDK 2.0 and attempted to build. This is where it starts to get interesting ...

It will not build because it starts looking in CCStudio_v3.3/C6000/csl/include/csl_chiphal.h and says "#error NO CHIP DEFINED". I know why this is, but there is no definition for the DM6437 in that file.

It then occurred to me that perhaps the NDK 2.0 NSP for the DM6437 is not compatible with the packages (specifically PSP) that come with the DM6437.

What I would like to do is have a CSL for the DM6437 and put it in the CCStudio_v3.3\C6000 directory but do not know if this is appropriate for this product?

(1) Can I successfully use NDK 2.0 with the DM6437 board? If not, why not?

(2) If I can, then do I need to get hold of a different version of the PSP that came with the board or use a separate CSL?

(3) The PSP is quite confusing because there is a CSL 'inc' directory (dvsdk_1_01_00_15\psp_1_00_02_00\pspdrivers\soc\dm6437\dsp\inc) but where are the CSL libs? (For the C6457 there were 2: little and big endian). I have spotted lots of libs in dvsdk_1_01_00_15\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug for example but I am not sure if these are the ones.

(4) I wonder if the source (c files) of the DM6437 NSP files - ethdriver, nimu, mdio, emac would be compatible with the DM6437 PSP which is psp_1_00_01_00 on my install?

(5) If the DM6437 is too problematic would I be better to use a DM642 which I have and does seem to be mentioned in the CCStudio_v3.3/C6000/csl/include/csl_chiphal.h file?

 

Also, as an aside I noticed in the evmdm6437init.c file that came with the board, the LinkStr is effectively commented out (#ifdef WARNING) and the 'printf' that prints the link status is commented out. If it is left that way the emac registers OK. If this string is uncommented and the printf used then the emac does not register with the NIMU. However, if I use a local not static string in the DM64LCEMAC_linkStatus function then the emac registers OK. I'm thinking there is some sort of issue here that was not resolved when the EVMDM6437 was released and wonder if there is similar code in other NSP components: ethdriver, nimu, emac, mdio?

  • 0
    TI__Expert 7290 points

    Hi Rob,

    Rob Beck said:

    (3) The PSP is quite confusing because there is a CSL 'inc' directory (dvsdk_1_01_00_15\psp_1_00_02_00\pspdrivers\soc\dm6437\dsp\inc) but where are the CSL libs? (For the C6457 there were 2: little and big endian). I have spotted lots of libs in dvsdk_1_01_00_15\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug for example but I am not sure if these are the ones.

    The psp does not come with the CSL library, it has only the CSL header files. The libraries available in the path "dvsdk_1_01_00_15\psp_1_00_02_00\pspdrivers\lib\DM6437\Debug" are driver libraries.

    Other questions are related to NDK and NDK team can comment on that.

    Thanks and Regards,

    Sandeep K  

  • 0 in reply to Sandeep Krishnaswamy
    TI__Mastermind 45025 points

    Rob,

    The NDK 2.00 fully supports the DM6437.  Have you tried running the NDK client example on your DM6437 board?  This should work and if so, will verify that your hardware setup is correct.  You can find the example here:

    <install location>\ndk_2_0_0\packages\ti\ndk\example\network\client\evmdm6437

    So I'm confused as to why you are trying to copy in the 6437 NSP files into your project?  Are you trying to rebuild the Ethernet driver?

    Steve

  • 0 in reply to Steven Connell
    Intellectual 970 points

    I wish to alter the NSP to timestamp incoming packets before they reach the stack, that's why I'm looking at the NSP.

    I think what I am really asking is this: The EVM DM6437 comes with an EVAL NDK 1.92. I'd like to use NDK 2.0 but I need to verify that the other 'things' are compatible with the interface to NDK 2.0, for example the PSP etc.

    I'm thinking that for using the DM6437 with NDK 2.0 I need a different version of the PSP (and codecs)?

    The NDK 1.92 appears not to handle IPv6 and is an EVAL, the NDK 2.0 handles IPv6 and is not an EVAL (i.e. does not time out after 24 hours)

     

    I realise that the DM6437 is supported by the NDK 2.0 because in the NDK 2.0 directory I have already spotted NSP for the DM6437. However, when I attempted to compile it in with NDK 2.0 and the other 'stuff' that comes with the DM6437 board I got compile errors.

  • 0 in reply to Rob Beck
    TI__Mastermind 45025 points

    Rob,

    I see the following in the NDK 2.00 release notes:

    Required Software

    • Code Composer Studio Version 3.3 or higher
    • DSP/BIOS 5.33.01 or higher.
    • C6x Code Generation Tools version 6.1.5 or higher.
    • The Board Support Library (BSL) package from the EVM vendor CD/site.

    I don't think the NDK has a PSP dependency.  I also checked the client project and I don't see a CSL or PSP drivers dependency.  Were you ever able to run the client example, in order to verify your setup?

    I really think that you can get your app to build against the new NDK simply by changing the project to point to the NDK 2.00 libraries, instead of the NDK 1.92 versions.  And you are correct, the NDK 2.00 does not have this eval issue.

    Steve