• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Subscribers 98 subscribers
  • Views 397 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.

AM261-SOM-EVM: SDL: integrated_examples test failed

wang zheng
Prodigy 50 points

Part Number: AM261-SOM-EVM
Other Parts Discussed in Thread: SYSCONFIG

SDK version: mcu_plus_sdk_am261x_26_00_00_06

EVM:e3a9a6ec-fd46-420b-83eb-71c3f86fea18.jpg

Example: C:\ti\mcu_plus_sdk_am261x_26_00_00_06\examples\sdl\integrated_examples

Test result: 

image.png

  • 0
    TI__Mastermind 27172 points

    Hi Wang,

    There is a known issue in v26.00 SDK where the bootloader has some issues w.r.t to locking/unlocking of MMR registers. Due to this, when running examples with any SBL (SBL Null or SBL Ospi), they end up failing.

    Q1. Are you using DEV-BOOT mode? Do you have initialization happening through GEL Scripts. The example should work WITHOUT any SBL and with a gel script doing initialization in DEV Bootmode. https://software-dl.ti.com/mcu-plus-sdk/esd/AM261X/latest/exports/docs/api_guide_am261x/EVM_SETUP_PAGE.html#BOOTMODE_NOBOOT

    This SBL issue is already fixed, the fix is available on our Github (github.com/.../) and will be included in the public v26.1 SDK release which is expected around end of August.

    Q2. I also notice you have attached screenshot for LaunchPad but the example imported shows "SOM" evm. Can you confirm which one is being used?

    The same questions/ suggestions apply to these two E2Es as well:

     AM261-SOM-EVM: SDL: RTI UC2 test failed 

     AM261-SOM-EVM: SDL: dcc test failed 

    Regards,
    Shaunak

  • 0 in reply to Shaunak Deshpande
    Prodigy 50 points

    Q1: No. I tested with OSPI boot mode.   Could you please share the specific GEL script with me?

    Good to know that this is a known issue.

    I cannot open that GitHub link.

    Q2: I only have LaunchPad. In the SDK, there is no example for LaunchPad. 

    So I tried this example on LaunchPad.

  • 0 in reply to wang zheng
    TI__Mastermind 27172 points

    Hi Wang,

    1. Sorry for the typo in previous link, The correct link is: https://github.com/TexasInstruments/mcu_plus_sdk_am261x

    2. The examples should work fine on the launchpad, i confirmed.

    The new SDK is expected to be live on ti.com by Sept 4.

    Regards,
    Shaunak

  • 0 in reply to Shaunak Deshpande
    Prodigy 50 points

    1. I had downloaded the next SDK and tried with DFU flash of mcan_sdl_am261x-som_r5fss0-0_freertos_ti-arm-clang.mcelf into the LaunchPad board.

    The UART log also showed the same that some tests failed.

      default_dfu_ospi.cfg

    2. I tried DEV-BOOT mode with 400MHZ, using CCS to load the program into the LaunchPad board.

    It gets stuck here. 

    This is my email; could we have a short call on Webex?

    zheng.wang@cn.seyond.com

  • 0 in reply to wang zheng
    TI__Mastermind 27172 points

    Hi Wang,

    I'll route this to the automotive team for further alignment. 

    Regards,
    Shaunak

  • 0 in reply to Shaunak Deshpande
    Prodigy 50 points

    Please help assign this ticket to the right expert.  Our development time is quite short, need strong support from TI side.

  • 0 in reply to wang zheng
    TI__Guru* 80666 points

    Hi Wang,

    From your screenshot i could see you are testing this example in Dev boot mode.

    However, in below steps to test example, they clearly mentioned that this example should need to be test in QSPI/OSPI boot modes.

    So, i would suggest you test in that method once and provide me an update.

    --
    Thanks & regards,
    Jagadish.

  • 0 in reply to Shaunak Deshpande
    Prodigy 50 points
    Shaunak Deshpande said:
    Q1. Are you using DEV-BOOT mode? Do you have initialization happening through GEL Scripts. The example should work WITHOUT any SBL and with a gel script doing initialization in DEV Bootmode.

    This is the reply from 

  • 0 in reply to wang zheng
    TI__Guru* 80666 points
    wang zheng said:
    This is the reply from 

    Understood wang, however could you please test this integrated SDL example with SBL using OSPI boot mode?

  • 0 in reply to jagadish gundavarapu
    Prodigy 50 points 

    [15:10:54.153]收←◆
Starting OSPI Bootloader ... 
KPI_DATA: [BOOTLOADER_PROFILE] k        : 400.000 MHz 
KPI_DATA: [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
KPI_DATA: [BOOTLOADER_PROFILE] Boot Media Clock : 133.333 MHz 
KPI_DATA: [BOOTLOADER_PROFILE] Boot Image Size  : 83 KB 
KPI_DATA: [BOOTLOADER_PROFILE] Cores present    : 
r5f0-0
KPI_DATA: [BOOTLOADER PROFILE] System_init                      :        540us 
KPI_DATA: [BOOTLOADER PROFILE] Drivers_open                     :        103us 
KPI_DATA: [BOOTLOADER PROFILE] LoadHsmRtFw                      :       7875us 
KPI_DATA: [BOOTLOADER PROFILE] Board_driversOpen                :       2372us 
KPI_DATA: [BOOTLOADER PROFILE] CPU load                         :       4856us 
KPI_DATA: [BOOTLOADER PROFILE] SBL End                          :          7us 
KPI_DATA: [BOOTLOADER_PROFILE] SBL Total Time Taken             :      15756us 

Image loading done, switching to application ...
[MAIN] Start up diagnostics (STC,PBIST,CCM) passed. 
[MAINolled: 1000 TxBytes: 400000  RxBytes:400000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:11:01.985]收←◆[MCAN] Polled: 2000 TxBytes: 800000  RxBytes:800000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:11:09.819]收←◆[MCAN] Polled: 3000 TxBytes: 1200000  RxBytes:1200000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:11:17.654]收←◆[MCAN] Polled: 4000 TxBytes: 1600000  RxBytes:1600000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:11:25.488]收←◆[MCAN] Polled: 5000 TxBytes: 2000000  RxBytes:2000000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:11:33.323]收←◆[MCAN] Polled: 6000 TxBytes: 2400000  RxBytes:2400000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:11:41.157]收←◆[MCAN] Polled: 7000 TxBytes: 2800000  RxBytes:2800000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:11:48.991]收←◆[MCAN] Polled: 8000 TxBytes: 3200000  RxBytes:3200000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:11:56.826]收←◆[MCAN] Polled: 9000 TxBytes: 3600000  RxBytes:3600000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:12:04.660]收←◆[MCAN] Polled: 10000 TxBytes: 4000000  RxBytes:4000000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:12:12.494]收←◆[MCAN] Polled: 11000 TxBytes: 4400000  RxBytes:4400000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:12:20.328]收←◆[MCAN] Polled: 12000 TxBytes: 4800000  RxBytes:4800000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:12:28.163]收←◆[MCAN] Polled: 13000 TxBytes: 5200000  RxBytes:5200000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:12:35.998]收←◆[MCAN] Polled: 14000 TxBytes: 5600000  RxBytes:5600000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:12:43.831]收←◆[MCAN] Polled: 15000 TxBytes: 6000000  RxBytes:6000000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:12:46.306]收←◆[MAIN] Running diagnostics... 
    RTI UC1...... PASSED. 
    RTI UC2...... PASSED. 
    MCRC AUTO mode test... PASSED. 
    ECC MCAN0.... PASSED. 
    ECC ICSSM.... PASSED. 
    ECC MSSL2.... PASSED. 
    ECC ATCM0.... PASSED. 
    ECC BTCM.... PASSED. 
    DCC UC1...... 
[15:12:53.118]收←◆PASSED. 
    TCM Parity... PASSED. 
    DMA Parity... PASSED. 
    Lockstep mode test... PASSED. 
    TMU ROM Checksum test... PASSED. 
    TMU Parity test... PASSED. 
    TOG test... PASSED. 
    VTM test... 
[15:12:53.209]收←◆PASSED. 
[MAIN] Diagnostics Complete. 

[15:12:58.564]收←◆[MCAN] Polled: 16000 TxBytes: 6400000  RxBytes:6400000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:13:06.398]收←◆[MCAN] Polled: 17000 TxBytes: 6800000  RxBytes:6800000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:13:14.233]收←◆[MCAN] Polled: 18000 TxBytes: 7200000  RxBytes:7200000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:13:22.067]收←◆[MCAN] Polled: 19000 TxBytes: 7600000  RxBytes:7600000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:13:29.903]收←◆[MCAN] Polled: 20000 TxBytes: 8000000  RxBytes:8000000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:13:37.737]收←◆[MCAN] Polled: 21000 TxBytes: 8400000  RxBytes:8400000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:13:45.570]收←◆[MCAN] Polled: 22000 TxBytes: 8800000  RxBytes:8800000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:13:53.405]收←◆[MCAN] Polled: 23000 TxBytes: 9200000  RxBytes:9200000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:14:01.240]收←◆[MCAN] Polled: 24000 TxBytes: 9600000  RxBytes:9600000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:14:09.073]收←◆[MCAN] Polled: 25000 TxBytes: 10000000  RxBytes:10000000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:14:16.908]收←◆[MCAN] Polled: 26000 TxBytes: 10400000  RxBytes:10400000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:14:24.743]收←◆[MCAN] Polled: 27000 TxBytes: 10800000  RxBytes:10800000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

[15:14:32.576]收←◆[MCAN] Polled: 28000 TxBytes: 11200000  RxBytes:11200000  TxErr: 0  RxErr: 0  BadID: 0  MismatchData: 0

    This time, I use UART mode to flash the app with mcan_sdl_ospi_uart.cfg into SOM board. It works.

    So now I would like to understand which dependencies within SBL are required to support SDL execution.

     mcan_sdl_ospi_uart.cfg

  • 0 in reply to wang zheng
    TI__Guru* 80666 points

    Hi Wang,

    wang zheng said:
    So now I would like to understand which dependencies within SBL are required to support SDL execution.

    Not all the examples of SDL, most of the examples will work without SBL only. Only the testings which have dependency with CCM has to be work with SBL (Integrated example also involves CCM).

    CCM test is sensitive to the R5F core and its execution environment.

    When you run the application directly through CCS in dev boot mode:

    • The debugger can initialize parts of the device.
    • The CPU may not go through the same reset/release sequence as in a real boot.
    • The debugger can halt the R5F which is particularly undesirable in CCM (Core Compare Module) testing

    These are some reasons we should not perform this particular test in dev boot mode. Apart from these remaining testings can be work through dev boot mode as well.

    --
    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    TI__Guru* 80666 points

    Hi Wang,

    I was able to reproduce your issue at my end and then i made few changes in sysconfig(related to board), and now the example is working without any issues at my end on my AM261x Launchpad.

    Here is my project for your reference:

    mcan_sdl_am261x-som_r5fss0-0_freertos_ti-arm-clang.zip

    --
    Thanks & regards,
    Jagadish.

  • +1 in reply to jagadish gundavarapu
    TI__Guru* 80666 points

    Hi Wang,

    We had a discussion with internal design team on this PBIST and LBIST/STC. And there the conclusion is that they both should only perform once per power-up cycle at beginning of the code (SBL) because they both are destructive testings.

    --
    Thanks & regards,
    Jagadish.