• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 358 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.

AM625: Abnormality of AM625 input interrupt

Katherine Wang
Intellectual 2210 points
Part Number: AM625

Hi Team,

1. I used the AM6254 official development board to simulate the GPIO input interrupt function. I used the gpio_input_interrupt program in "mcu_plus_sdk_am62x_08_04_00_16" to replace the newly compiled am62-mcu-m4f0_0-fw in the /lib/firmware/ directory. The M core running program was abnormal after getting online again. The prompt is:

[Error] Sciclient event config failed!!!
ASSERT: 0.6697s: ../board.c:Sciclient_gpioIrqSet:107: FALSE failed !!!

2. I checked the source code and found an assertion error at the initialization of the GPIO interrupt. The specific code is as follows:

retVal = Sciclient_rmIrqSetRaw(&rmIrqReq, &rmIrqResp, SystemP_WAIT_FOREVER);
if(0 != retVal)
{
DebugP_log("[Error] Sciclient event config failed!!!\r\n");
DebugP_assert(FALSE);
}

3. All that I used was the official default hardwares and the SDK packages of the official website, and no modifications have been made to all other content.

4. I replaced it with other GPIO pins, and the issue remained the same.

Could you please help me to find out what is causing this issue?

Kind regards,

Katherine

  • 0
    TI__Mastermind 45486 points

    Hi Katherine,

    Thanks for your patience.

    I am assuming you are following the link( AM62x MCU+ SDK: GPIO Input Interrupt ) and you have gone through the part where it says "Attention".

    Once you have gone through the same, and followed the steps, please try running again.

    After trying, if you still face the issue, please do let me know.

    Thanks and Regards,

    Vaibhav

  • 0
    TI__Intellectual 2210 points

    Hi Vaibhav,

    1. After I modified the device tree according to this post, it was found that the problem of interrupt abnormality disappeared. After I short-circuited GPIO0_15 and GND, I could indeed detect the input interrupt.
    2. For the same device tree, I modified the example.syscfg file in ccs, changed GPIO0_15(E5) to GPIO0_16(D4), and copied the executable files, am62-mcu-m4f0_0-fw and gpio_input_interrupt_am62x-sk_m4fss0-0_nortos_ti-arm-clang.out, to the development board via FTP. At this time, after the power-on, am62-mcu-m4f0_0-fw would be loaded. The interrupt configuration error would not be prompted, but at this time GPIO0_16 (P9 terminal 11 bit) and GND were short-circuited. At this time, the application program cannot detect the binary input and remained in the state of waiting for the binary input interrupt.

    3. I used the method of loading the out file. I first switched to the /sys/class/remoteproc/remoteproc0 directory, and then checked that the M core status was 'running'. I entered echo stop > state to stop the M core program, loaded the out file (echo m4fss_firmware/ *.out > firmware), and then entered echo start > state to run. The result was different at this time, and the interrupt configuration abnormality was reported again, which was consistent with the initial issue.

    4. I used the grep command to search the device tree files of kernel and boot and found no definition of GPIO0_15 and GPIO0_16 nodes. Now I don’t know how to solve the problem that GPIO0_16 cannot use the input interrupt.

    Reards,

    Katherine

  • 0 in reply to Vaibhav Kumar
    TI__Intellectual 2210 points

    Hi Vaibhav,
    Could you please follow up on my issue?
    Regards,
    Katherine

  • 0 in reply to Katherine Wang
    TI__Mastermind 45486 points

    Hi Katherine,

    I am communicating with my team members, I will highlight on your issue as soon as possible.
    Thanks for your patience.

    Regards,

    Vaibhav

  • +1 in reply to Vaibhav Kumar
    TI__Mastermind 46626 points

    Hello Katherine,

    Please confirm which GPIO pin you want to use for your application.

    I understand you want to go with MCU_GPIO016.

    So, in that case update to SRC_IDX_BASE_MCU_GPIO_BANK_1 in marked yellow line in your application.

    Regards,

    S.Anil.