• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 462 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.

AM2634: gpmc - freertos

gyeongju kwon
Prodigy 130 points
Part Number: AM2634


hi

Implemented gpmc0 in noos mode.
Put the value directly into the register and do the desired action.
An error occurs while implanting the gpmc implemented in noos mode from freetos.
Go to TaskP_loadGet(), I don't know why.
What should I do?

  • 0 in reply to gyeongju kwon
    TI__Guru 56105 points

    Hi Kwon,

    Where did you initialize the GPMC PSRAM (the only GPMC mode which AM263x MCU+ SDK 09.01.00.44 currently supports)?

    You cannot use the memory area starting at 0x68000000 until the GPMC initialization is done.

    Best regards,

    Ming

  • 0 in reply to Ming Wei
    Prodigy 130 points

    hi 

    I set it up like an image.
    I did it at freertos.
    error occurs in freertos.
    It works well with noos.

  • 0 in reply to gyeongju kwon
    TI__Guru 56105 points

    Hi Kwon,

    Which AM263x MCU+ SDK are you using? 09.00.00 or 09.01.00?

    Best regards,

    Ming

  • 0 in reply to Ming Wei
    Prodigy 130 points

    hi

    sdk 09.01.00.41

  • +1 in reply to gyeongju kwon
    TI__Guru 56105 points

    Hi Kwon,

    The AM263x GPMC initialization is the same between the NORTOS and FreeRTOS. It is done using the syscfg (in ti_drivers_config.c): System_init -->  GPMC_init (passing parameters through gGpmcConfig).

    One thing you can try is to comment out the following code:

    pSrc = &buff[0];
    pDes = (uint16_t *)0x68000000;
    *pDes = *pSrc;

    If the error is gone, then it means your GPMC initialization is not completed correctly. You can check the 0x68000000 with Memory Browser in CCS. It should show that the memory area is not available. 

    If that is the case, then two things can go wrong:

    1. The MPU setting for GPMC memory space is not done correctly.

    2. The GPMC initialization is not done correctly.  

    You can refer to gpmc_psram_io_am263x-cc_r5fss0-0_nortos_ti-arm-clang for both items.

    I tried your test case based on the modified empty_am263x-cc_r5fss0-0_freertos_ti-arm-clang (mimic gpmc_psram_io_am263x-cc_r5fss0-0_nortos_ti-arm-clang) on the AM263x LP without the PSRAM daughter card. Th example runs to data abortion with the above code (accessing GPMC memory)  

    Best regards,

    Ming