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.

Comprehensive peripheral memory map...



Many/most peripherals have a Module base address that the module registers are added to to get the actual address where the module registers resides.  For instance, the Technical Reference Manual in section 21.3 details the UART registers, but it indicates the module base address is required, but yet it fails to indicate what/where the module base addresses can be located.

In the datasheet at the bottom of Section 8.21 it references another document "TMS320DM814x DMSoc Universal Asynchronous Receiver/Transmitter (UART) User's Guide", but I've not been able to locate this.

It seems like most of the information (required for programming) is in the Technical Reference Manual, but key information like the above appears to be missing from many areas of the manual, the above being just a single example of this.

Is there a single place where a peripheral memory map is located which details the module base addresses for all the peripherals, or at least the peripherals that require module base addresses?  I'm spending alot of time trying to locate key information such as this, and this time could be better spent doing something more productive than posting message in this forum for information that should already be provided in said document sections.

  • Joe,

    Sorry for confusion.  We will continue to improve our doc.

    For your question, the Data Sheet has the base address of all the modules in Table 2-3. L3 Memory Map.  For UART, you see the L4 Slow Peripheral Domain (see Table 2-6).  When you go to Table 2-6, you will see the base address for UART0 is at 0x4802_0000.

    I know how you feel since I was on the same boat at the beginning but after look up a few registers, I start to get used to it.

    Regards,

    Viet

     

    Don't forget to verify answers to your forum questions by using the green "Verify Answer" button.

  • Thank-you very much for the clarification.  This device family is one of the most sophisticated and complicated I've ever worked with.I too have been working with it (under NDA) prior to it's public release, and I guess I've got a case of "document fatigue"...that is to say, I've seen so many revisions of documentation, each adding a bit more than the prior document...that I'm finding it difficult to keep up...

     

    Thanks for your continued support.