• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 362 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.

AM2434: the gpio interrupt example

HE
Intellectual 295 points
Part Number: AM2434

Hello: 

 A problem was encountered when using the gpio interrupt example.

The original example works fine, but after modifying the gpio pin from C13 to W6, the program does not run, with the following error

"[MAIN_Cortex_R5_0_0] [Error] Sciclient event config failed!!!
ASSERT: 0.12333s: syscfg/ti_drivers_config.c:Sciclient_gpioIrqSet:116: FALSE failed !!!"

===================================================================

Development board：AM243xEVM

Example：gpio_input_interrupt_am243x-evm_r5fss0-0_nortos

SDK: mcu_plus_sdk_am243x_08_06_00_43

help me ,thanks

  • 0
    TI__Guru 55045 points

    Hi He He,

    I changed the gpio pin from C13 to W6, the gpio_input_interrupt_am243x-evm_r5fss0-0_nortos works OK

    =========================================

    [MAIN_Cortex_R5_0_0] GPIO Input Interrupt Test Started ...
    GPIO Interrupt Configured for Rising Edge (Button release will trigger interrupt) ...
    Press and release SW5 button on EVM to trigger GPIO interrupt ...
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times

    ==========================================

    Did you update the SBL_NULL in the OSPI flash with the sbl_null.release.hs_fs.tiimage (for HS_FS device) or sbl_null.release.tiimage (GP device)?

    Best regards,

    Ming

  • 0
    Expert 1330 points

    This error can be caused by  incorrect pin or interrupt configurations or incompatible SDK versions.

  • 0 in reply to Ming Wei
    Intellectual 295 points

    thanks,

    Could you please tell me  what is the boot  mode of your board?

    I did not update the SBL_NULL in the OSPI flash with the sbl_null.release.hs_fs.tiimage, but my EVM is in DEV boot mode , I dubug code in ccs and use the following script to  soc Initialization

    "js:> loadJSFile "C:/ti/mcu_plus_sdk_am243x_08_06_00_43/tools/ccs_load/am243x/load_dmsc_hsfs.js""

    The EVM is in  DEV boot mode ,Whether to load the program in the OSPI flash?

    thanks

  • 0 in reply to HE
    TI__Guru 55045 points

    Hi He He,

    I am using the boot from OSPI flash mode. Can you try this mode?

    I can also try the DEV boot mode with load_dmsc_hsfs.js.

    Best regards,

    Ming

  • 0 in reply to Ming Wei
    TI__Guru 55045 points

    Hi He He,

    I also tried the following:

    1. Set AM243x HS-FS EVM is in DEV boot mode, in ccs and use the following script to do soc Initialization

    "js:> loadJSFile "C:/ti/mcu_plus_sdk_am243x_08_06_00_43/tools/ccs_load/am243x/load_dmsc_hsfs.js"

    2. Load the gpio_input_interrupt_am243x-evm_r5fss0-0_nortos_ti-arm-clang using CCS + JTAG (GPIO pin is using W6)

    3. The CCS console display the following:

    [MAIN_Cortex_R5_0_0] GPIO Input Interrupt Test Started ...
    GPIO Interrupt Configured for Rising Edge (Button release will trigger interrupt) ...
    Press and release SW5 button on EVM to trigger GPIO interrupt ...
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times
    Key is pressed 0 times

    The result is the same as using SBL_NULL to initialize the SoC.

    Best regards,

    Ming