• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 73 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.

TDA4AEN-Q1: Supporting “Early CAN Response” on MCU R5

SanHsin Kuo
Prodigy 100 points
Part Number: TDA4AEN-Q1

Tool/software:

Hi,

         We are currently developing CAN communication functionality and need to support an Early CAN Response requirement on the MCU R5 core using FreeRTOS or AUTOSAR.

However, in the default BSP for the TDA4AEN, the MCU R5 firmware image is packaged within the Linux RootFS. For our use case, this is too late in the boot sequence.

To meet the Early CAN Response requirement, the MCU R5 firmware must boot directly from NOR Flash, rather than being loaded by Linux from the RootFS.

We have the following questions:

Q1) Can the Wakeup R5 / SBL load the MCU R5 firmware binary directly from NOR Flash?

Q2) How can we implement MCU R5 booting from NOR Flash to fulfill the Early CAN Response requirement?

Q3) How can we configure the Wakeup R5 / SBL to boot or reset only the MCU R5, while keeping the A53 cores inactive?

Q4) Do you have any recommendations or best practices for implementing Early CAN Response on MCU R5?

B.R.

SanHsinTDA4AEN Boot Flow

  • 0
    TI__Mastermind 49696 points

    Hello,

    I will be out of office next 2 days .Please expect delay in response.

    Regards

    Tarun Mukesh

  • 0 in reply to Tarun Mukesh Puvvada
    TI__Mastermind 49696 points

    Hello,

    On WK R5F core , we have initially SBL running and later we have sciserver running on it. In the above flow diagram, linux is not loading MCU R5F and MAIN Domain cores it is WK R5F core running SBL .

    First step is to load the MCU R5F ,MAIN R5F and A53 cores running linux using combined app image by SBL. All cores are started once WK UP starts running sci server , without sciserver running your sciclient calls on other cores might fail.

    If you don't need linux running on A53 and other Main domain cores then yu need not fill there images.

    Regards

    Tarun Mukesh

  • 0 in reply to Tarun Mukesh Puvvada
    Prodigy 100 points

    Hi,

       We aim to implement "Early CAN Response" on TDA4AEN using the MCU R5F core (running AutoSAR/FreeRTOS) within the Secondary Boot (SBL) boot flow.

    Does TI have an Application Report for "Early CAN Response on TDA4AEN" (or the broader TDA4 series)?

    We found TI’s existing document, "Early CAN Response on DRA7xx" (SPRACD1), but have not yet located a corresponding report for the TDA4AEN.

    If no such document exists for TDA4AEN, could you clarify the key differences in software implementation for "Early CAN Response" between TDA4AEN and DRA7xx?

    Thanks a lot.

    SanHsin 

  • 0 in reply to SanHsin Kuo
    TI__Mastermind 49696 points

    Hello,

    There is difference between in architecture TDA4AEN and DRA7xx 

    SanHsin Kuo said:
       We aim to implement "Early CAN Response" on TDA4AEN using the MCU R5F core (running AutoSAR/FreeRTOS) within the Secondary Boot (SBL) boot flow.

    TDA4AEN has wkup R5F core this is the DM core which runs SBL prior. MCUR5F doesn't run SBL or it is not the DM core.

    SanHsin Kuo said:
    If no such document exists for TDA4AEN, could you clarify the key differences in software implementation for "Early CAN Response" between TDA4AEN and DRA7xx?

    No such document is available for now to do this. Now since WKUP domain comes first as soon as you load MCU R5F core you can directly start CAN application on MCU R5F so no extra things are needed.

    Regards

    Tarun Mukesh