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.

AM3517 XML support files

Other Parts Discussed in Thread: AM3517

OK, I'm still waiting for these.

The files in Modules/omap34xx are not all correct, and I'm tired of not being able to debug a TI processor with TI tools.  Here is but one example from many:

CM_CPLEN_PLL_MPU bits 9:8 are EN_MPU_DPLL_LPMODE.   The file Modules\omap34xx\MPU_CM.xml says those two bits are reserved!

What is it with TI!?!?!?  HOW LONG has this product been on the market but there are no files for it?

I'm using a AM3517.xml file that Rafael gave me, which he took from a OMAP chip, but recently I had to go in and add all the GPMC stuff for it!

WHY ARE YOU DOING THIS?  DO YOU REALLY NOT CARE?  I don't buy any excuses from TI that there's no time or demand.  YOU put support for this chip into the tools, but you failed to do all of it!!!

Come on, TI!! GET WITH IT!  Produce a complete set of files for this chipset!

I've wandered through the wiki, which is also poorly designed, and can't find anything for this part in the way of support files.

  • Matt,

    I don't have a good answer for you.  We have raised the issue to the group responsible for the AM3517 device and files.

    We will look into the issue you mentioned with MPU_CM, those files should have been generated right out of the spec for the OMAP3430.  Are you having issues with those files on OMAP3430 or on AM3517?

     

    John

  • Matt,

    I believe the xml file is correct.  It just can't be used for AM3517.

    For the OMAP34x/35x bits 9 and 8 are reserved. Check page 439 of:

    http://www.ti.com/lit/ug/spruf98t/spruf98t.pdf

     

    However, AM3517 has valid bits in positions 9 and 8. Check page 323 of rev G of the AM3517 TRM:

    http://www.ti.com/lit/ug/sprugr0b/sprugr0b.pdf

     

    So the problem is really the original one you pointed out which is that there are no definition files available for AM3517 and unfortunately you can't use the ones for OMAP3430.

     

    Regards,

    John

  • John,

    I made my own version of a file for the AM3517.  The file that Rafael gave me, however, was based on all of those values from the OMAP34x.  I'm still waiting for the RIGHT files.  It's a royal pain in the but to get debugging and find that the information given by the debugger is wrong, because the underlying XML files are wrong!

    I hope you can understand why I'm so annoyed about this.

    Regards,

    Matt

  • Matt,

    I have an AM3517 file now.  This is not an official file out the product team but just something I put together.  You are welcome to give it a try.  Our device file coverage on AM devices is horrible so I have been trying to get at least something basic in place for now.

    For AM3517 the file does have peripherals.  I used OMAP3630 as the reference instead of OMAP3430/3530.  This should work better.  The file is attached if you want to give it a try to see if it works better for you.

    2235.AM3517.zip

    Regards,

    John

     

  • Thanks, I will check into it.

    I have made numerous changes to one for myself, including allowing access to all the CP15 registers, and I modified the CortexA8 invisible .xml file so that the debugger would stop complaining about all the registers this chip doesn't have.

    I will see about posting a ZIP file here.

    Regards,

    Matt

  • If you could post the changes you have made that would be great.

  • Hi,

    I've included the files I've changed.  I thought I changed a GPMC file, but I can't be certain right now.

    Regards,

    Matt

    5824.AM3517_files.zip