• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 102 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AWR6843AOPEVM: Address mismatch between sys_common_xwr68xx_mss.h file & AWR6843AOPEVM DataSheet in (mmwave_sdk_03_06_02_00) SDK

Shubham Sawant
Prodigy 20 points
Part Number: AWR6843AOPEVM
Other Parts Discussed in Thread: AWR6843AOP

Tool/software:

Hello Team,

I'm referring mmwave_sdk_03_06_02_00-LTS, In that the header file "sys_common_xwr68xx_mss.h" contains macros that specify the base addresses. Is the AWR6843AOPEVM model associated with those addresses?

While checking "UART_config" in the UART_init() function, I was unable find these addresses in the "AWR6843AOP Single-Chip 60- to 64-GHz mmWave Sensor Antennas-On-Package (AOP)" datasheet.

  • +1
    TI__Genius 11806 points

    Hey Shubham,

    Yes, the addresses within the sys_common_xwr68xx_mss.h are also applicable for AWR6843AOPEVM.

    Shubham Sawant said:
    While checking "UART_config" in the UART_init() function, I was unable find these addresses in the "AWR6843AOP Single-Chip 60- to 64-GHz mmWave Sensor Antennas-On-Package (AOP)" datasheet.

    I'm a bit confused on why you are looking for an address that is associated with UART_config. UART_config is an array of structs that each contains a function table, driver data object, and hardware attribute structure. UART_init will call the init function registered in the UART_config function table, UartSci_init, which effectively does nothing. UartSci_open is where most of the configuration for each UART peripheral is handled.

    Anyways, I just wanted to provide some extra context to the UART driver, but let me know if this answered your question.

    Regards,

    Kristien