• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 533 views
  • Users 0 members are here
Support feedback
Options
Options

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.

TDA4VM: AUTOSAR SW is stuck via SBL+OSPI Boot Mode

user6314500
Intellectual 460 points
Part Number: TDA4VM

Hello supporter,

 

We get some issues when we integrate Vector AUTOSAR to ZF custom board and need TI expert for support:

 

  1. AUOSAR Bootup issue

With the same Vector AUTOSAR SW,

(1) The AUTOSAR SW runs normally when loading SW by CCS + No Boot Mode.

(2) The AUTOSAR SW is stuck in OS start when loading SW via TI SBL + OPSI flash.

 

  1. Test log

2.1 TDA4 Boot Mode: SBL + OSPI

SBL loads AUTOSAR SW to DDR, and AUOTSAR SW runs to AUTOSAR main() function.

(1) Debug Log

AUTOSAR SW runs to main() function which observed by adding BootUart_Init() to output UART log. 

 

      

   

(2) Add UART log to Default_Init_task. No log is observed.

Issue: OS  Default_Init_task() is not scheduled.

 

 

 

(3) According to the function calling relationship, add the test log.

Observation: all the test logs printed before EcuM_Init() function.

The program is stuck in Default_Init_Task().

 

 

application\third-party\vector-microsar\Components\Os\Implementation\Os_Hal_Context_v7r.h Line:311。

 

 

2.2 TDA4 Boot mode: CCS + No Boot mode

The AUTOSAR SW runs normally when loading SW by CCS + No Boot Mode. All the tasks are scheduled as expected.

 

Test log: Default_Init_Task logs observed.

 

 

  • 0
    Intellectual 460 points

    Hello Supporter,

    Information Upate:

    1. SDK version: R07.03

    2. SBL works normally.

        SBL boots CAN_BootApp() successfully.

    3. The Memory Layout

    Observation: With this memory layout, program jumps to AUTOSAR main(), and stuck in Os_Hal_ContextGo()

    3.1 Linker file

    3.2 Map file

    4. Update Memory Layout

    Observation: After the Memory layout update, the program can't jump to AUTOSAR main() function.

    Updated linker file:

    Updated map file:

  • 0 in reply to user6314500
    TI__Guru* 77074 points

    Hi,

    Can you please send across your MPU configuration as well? This will be the global structure gCslR5MpuCfg.

    Regards

    Karan

  • 0 in reply to Karan Saxena
    TI__Guru* 77074 points

    Also, can you also send across the Linker and Map file for working CAN_BootApp as well?

    Regards

    Karan

  • 0 in reply to Karan Saxena
    TI__Guru* 77074 points

    Closing the loop on this one.

    Issue-1. AUTOSAR Vector Table Over writing by SBL

    Solution: relocate AUTOSAR Vector Table. After jumping to AUTOSAR, AUOTSAR copy AUTOSAR vector table to Address 0x00000000 by the AUOTSAR startup code.

    (1) AUTOSAR Vector table relocation.

    (2) Copy AUTOSAR Vector table to Address 0x00000000.

    Issue-2. SciServer impact and maybe due to SciServer integration issue

    Solution: comment SciServer code temporarily.

    Issue-3: Wakeup_Uart1 interrupt impact: there is conflict of wakeup_uart1 interrupt and mcu_timer0 interrupt

    Solution: Disable Wakeup_Uart1

    Regards

    Karan