• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 222 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.

AWR6843AOP: MSS_ESM Group 1 bit2 and bit34 are set to 1, what does it mean?

ya luo
Prodigy 50 points
Part Number: AWR6843AOP
Other Parts Discussed in Thread: AWR6843

Hi 

   I monitored the ESMSR1 to ESMSR4 registers and read their values periodically.And output data through CAN message. After the software used the serial port to burn, I found that the ESMSR1 register value was always 0x800, and the ESMSR4 value was always 0x4. But it did not appear during debugging.I don’t know how these errors occurred. What are the effects? Can you help me answer it? Thank you very much!

  • 0
    TI__Guru 69960 points

    Hi ,

    What you debug this application, did you flash ccsdebug.bin file to device and then load your application image via CCS?

    And in the flash mode of application: could you check if these ESM bits are set at the beginning (before CAN data transmission) or during the the data transfer?

  • 0 in reply to Jitendra Gupta
    Prodigy 50 points

    hi Jitendra Gupta,

    Of course,in the debug mode ，I flash ccsdebug.bin file to device before debug this application,and i checked that ESMSR4 is set to 0x4 after calling the SOC_init() function, and ESMSR1 is set to 0x800 after calling the pin_config() function.

        gMmwMssMCB.socHandle   = SOC_init (&socCfg, &errCode);

        pin_config();To be more specific is after the following：

    (Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINN15_PADBV, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINN15_PADBV, SOC_XWR68XX_PINN15_PADBV_DMM_CLK);
    Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINP4_PADBB, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINP4_PADBB, SOC_XWR68XX_PINP4_PADBB_DMM_MUXIN);
    Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINR4_PADBF, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINR4_PADBF, SOC_XWR68XX_PINR4_PADBF_DMM0);
    Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINP5_PADBG, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINP5_PADBG, SOC_XWR68XX_PINP5_PADBG_DMM1);
    Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINR5_PADBH, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINR5_PADBH, SOC_XWR68XX_PINR5_PADBH_DMM2);
    Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINP6_PADBI, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINP6_PADBI, SOC_XWR68XX_PINP6_PADBI_DMM3);
    Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINR7_PADBJ, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINR7_PADBJ, SOC_XWR68XX_PINR7_PADBJ_DMM4);
    Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINP7_PADBK, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINP7_PADBK, SOC_XWR68XX_PINP7_PADBK_DMM5);
    Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINR8_PADBL, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINR8_PADBL, SOC_XWR68XX_PINR8_PADBL_DMM6);
    Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINP8_PADBM, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR68XX_PINP8_PADBM, SOC_XWR68XX_PINP8_PADBM_DMM7);)

  • 0 in reply to ya luo
    TI__Guru 69960 points

    Do you see this ESM status specifically with this application or even with mmw demo?

    And for AWR6843AOP, please check the datasheet for pin mapping to do the pinmux. There may be possibility of different pin mapping for AWR6843 vs AWR6843AOP. 

    Refer this related E2E FAQ

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1024687/faq-awr6843aop-mmwave-sdk-pinmux-awr1843aop-and-awr6843aop

  • 0 in reply to Jitendra Gupta
    Prodigy 50 points

    I found it on my application, and I haven't tried it in the mmw demo. I think the pin map is just a different macro definition, which has no effect.

  • 0 in reply to ya luo
    TI__Guru 69960 points

    I would suggest you to try once with mmw demo application, if there you see same behavior.