• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 942 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.

TDA4VM: MCU only BOOTMODE usecase of TDA4

Sung-IL
Mastermind 31540 points

Part Number: TDA4VM
Other Parts Discussed in Thread: TDA2

Dear Champs,

My customer is very confusing on the complex boot mode in TDA4.

I think the basic boot procedure is

MCU boot -> Normal boot

Is this right?

Why MCU should be boot before Normal boot?

What is the purpose of MCU only boot?

Thanks and Best Regards,

SI.

  • 0
    TI__Mastermind 25140 points

    Hi SI,

    Think of the MCU's R5F processor as the boot master of the SoC. Note that boot master of J6/TDA2 was the A15 MPU, J6 didn't have an MCU island. The boot master runs its ROM code after reset and loads the SBL image. SBL then can load other cores images, in turn.

    The whole MCU island/domain is there for safety and diagnostics purposes in the automotive applications.

    The MCU-only boot allows sucessful boot even if main domain is not powered (due to power failure). MCU then can send message to other nodes in the vehicle that this node is not functional or can perform other tasks. The MCU-only  boot is tryed only from MCU domain's peripherals, that's why it can be successful when main domain is OFF.

    Please refer also to section 4.2.3 Boot Process Flow of the TRM.

    Regards,

    Stan