• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 30 subscribers
  • Views 298 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: System does not work when I use GPIO31 and GPIO32 as input

Kimi Hu
Mastermind 6095 points
Part Number: AWR6843AOP
Other Parts Discussed in Thread: IWR6843AOP, AWR6843

Hi,

I use GPIO31 and GPIO32 as input to communicate with another MCU. After setting the GPIO, the system does not work anymore. Do I miss anything? My program is showing below

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_GPIO_31);

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_GPIO_32);

GPIO_setConfig (SOC_XWR68XX_GPIO_31, GPIO_CFG_INPUT | GPIO_CFG_IN_INT_NONE);
GPIO_setConfig (SOC_XWR68XX_GPIO_32, GPIO_CFG_INPUT | GPIO_CFG_IN_INT_NONE);

  • 0
    TI__Genius 10534 points

    Hi Kimi,

    I have a few things you can check:

    1) Take a look at the following E2E FAQ document with included pinmux header files for the AOP devices: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1024687/faq-awr6843aop-mmwave-sdk-pinmux-awr1843aop-and-awr6843aop?tisearch=e2e-sitesearch&keymatch=aop%2520pinmux%2520awr6843aop

    You'll need these header files in order to pinmux on the AOP.

    2) Refer to the example for driving the GPIO pins included in the SDK download: 

    C:\ti\mmwave_sdk_03_05_00_04\packages\ti\drivers\gpio\test\xwr68xx

    Regards,

    Brennan

  • 0 in reply to Brennan Hartigan
    Mastermind 6095 points

    Hi, Brennan,

    Sorry, I provide the wrong Part number. I use IWR6843AOP(NOT AWR6843). I still follow the suggestion to re-build the pinmux driver library but it does not work. We use mmwave_industrial_toolbox_4_7_0 - people_counting project and mmwave_sdk_03_05_00_04. In our project, We already use

    2 GPIO(SOC_XWR68XX_PINK13_PADAZ_GPIO_2 and SOC_XWR68XX_PINH13_PADAB_GPIO_0)

    to control LED. Now We need add

    3 GPIO(SOC_XWR68XX_PINJ13_PADAC_GPIO_1, SOC_XWR68XX_PINR4_PADBF_GPIO_31 and SOC_XWR68XX_PINP5_PADBG_GPIO_32)

    as input to communicate with MCU.  The SOC_XWR68XX_PINJ13_PADAC_GPIO_1 work correctly. But after setting GPIO31 and 32, the system does not work. Do you have any suggestion?

  • 0 in reply to Brennan Hartigan
    Mastermind 6095 points

    Hi, Brennan,

    I try to follow E2E FAQ document with included pinmux header files for the AOP devices, but I fail. I provide my steps for your reference. Please correct me if I have a mistake.

    1. copy pinmux_xwr1843AOP.h and 6835.pinmux_xwr6843AOP.h(re-name to pinmux_xwr6843AOP.h) to mmwave_sdk_03_05_00_04\packages\ti\drivers\pinmux\include

    2. start cmd in wimdows

    3. change to mmwave_sdk_03_05_00_04\packages\scripts\windows

    4. execute setenv.dat

    5. change to mmwave_sdk_03_05_00_04\packages\ti\drivers\pinmux

    6. execute gmake clean

    7. execute gmake all

    8. rebuild project

    After rebuild project. I change the config to 

    Pinmux_Set_OverrideCtrl(SOC_XWR6843AOP_PINM2_PADAB, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR6843AOP_PINM2_PADAB, SOC_XWR6843AOP_PINM2_PADAB_GPIO_0);

    But it still display "SOC_XWR6843AOP_PINM2_PADAB" and "SOC_XWR6843AOP_PINM2_PADAB_GPIO_0" un-define

  • +1 in reply to Kimi Hu
    TI__Genius 10534 points

    Hi Kimi, 

    After further investigation and testing on my own device, you need to modify your code to the following and it will work:

    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_GPIO_31);

    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_GPIO_32);

    GPIO_setConfig (SOC_XWR68XX_GPIO_31, GPIO_CFG_INPUT);
    GPIO_setConfig (SOC_XWR68XX_GPIO_32, GPIO_CFG_INPUT);

    We are investigating the cause, but for now this will work for you.

    Regards,

    Brennan

  • 0 in reply to Brennan Hartigan
    Mastermind 6095 points

    Hi Brennan,

    Thank you. It works

  • 0 in reply to Brennan Hartigan
    Mastermind 6095 points

    Hi Brennan,

    One more question, if I change the pin config to correct header file(pinmux_xwr6843AOP.h). Can it solve this issue? Or it is SDK(mmwave_sdk_03_05_00_04) issue?

  • 0 in reply to Kimi Hu
    TI__Genius 10534 points

    Hi Kimi,

    This is an SDK issue that we are looking into.  I am glad your code works!

    Regards,

    Brennan