• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 149 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.

SYSCONFIG: AM263x SysCfg: GPIO1 assigned to a GPIO0 input

Daniel Brown
Prodigy 145 points
Part Number: SYSCONFIG
Other Parts Discussed in Thread: TMDSCNCD263

Hello,

SETUP: I am using the TMDSCNCD263 control card, CCS 12.5, MCU+ SDK for AM263x 8.6.0.34, and SysConfig version 1.18.0.3266 (from thread AM2634: Sysconfig error - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums).

In SysConfig, I have a GPIO input set up.  The only GPIO peripheral that it allows is GPIO0.

LARGER ISSUE: When I compile and run the code using the debugger, it gets stuck in HwiP_data_abort_handler_c(void).

I stepped through the code to see where it hangs up.  The first function called in main() is System_init(); That is defined in ti_drivers_config.c from SysConfig.  Within System_init(), it is fine until it calls GPIO_init(); inside the same file.  Then it gets to GPIO_setDirMode(baseAddr, GPIO_ILLK_POLARITY_PIN, GPIO_ILLK_POLARITY_DIR); and hangs up.

LIKELY CAUSE: The baseAddr that is passed to this function is CSL_GPIO1_U_BASE (0x52001000ul).  However, the GPIO examples provided in the SDK are given a base address of CSL_GPIO0_U_BASE (0x52000000ul).

A. Is my issue caused by an erroneous base address?

B. What is wrong with SysConfig that it is telling GPIO0 to have a base address for GPIO1?  And I do I fix or work around it?  I uninstalled CCS 12.4 this morning and installed the latest CCS 12.5 this morning.