• Resolved

TDA4VM: MCU Only Boot

Intellectual 290 points

Replies: 7

Views: 114

Part Number: TDA4VM

Hi, Sir, 

I would like to understand how to test MCU only boot mode in TDA4 EVM.

These are my test procedures

1.Set Boot mode switch as OSPI Flash and MCU only=0(SW8=00000000, SW9=01000000)

The result of booting form MCU to Main domain is successed.

2.Set Boot mode switch as OSPI Flash and MCU only=1(SW8=00000000, SW9=01001000)

The result of booting form MCU to Main domain is failed. 

There are not any uart log form MCU Spl.

My questions are

1.Is supported MCU only mode = 1 in PSDK 6.1.1 ?

2. Any application note document for MCU only mode = 1 ?

3. How can I run MCU only mode = 1 correctly on TDA4 EVM ?

Br,

KS.

  • Hi KS,

    Can you help me understand which software package you are trying to use?  Are you trying to boot Linux (from PSDKLA), or are you trying to boot an RTOS image (from PSDK RTOS)? 

    They each use different R5 bootloader software, so it would help to understand which direction you are trying to go here.

    Also, what is your goal in using the MCU-only boot mode - are you running some MCU R5 software that will run separately for a while and then boot the MAIN domain cores later on and you need to save some power for a while, or are you trying to implement a "Freedom from Interference" (FFI) feature, or something else?

    In parallel, I'll check to see if either SDK package supports the MCU-only bootmode at this time.

    Thanks,

    Jonathan

  • In reply to Jonathan Bergsagel:

    Hi, Jonathan

    I use PSDKLA(V6.1.1) to boot.
    At www.ti.com/.../PROCESSOR-SDK-DRA8X-TDA4X


    My goal is to implement "CAN Wakeup" Feature,

    1.Before CAN wakeup triggered, we need to keep whole systems on power saving mode.
    2.When CAN wakeup triggered, MCU R5F application must to power on Main Domain, boot up all CPU cores, and then start the normal operation mode.
    3.If system get sleep command in Normal operation mode, MCU have to power off main domain, and go back to power saving mode.

     

    So,
    firstly I need to understand how to boot on MCU only mode, and then run MCU R5F spl and application software.

    As you said -  Running some MCU R5 software that will run separately for a while and then boot the MAIN domain cores later on.

    Another question,
    In J721E Board, the signal CAN_WKUP connected to GPIO4 of TPS659413.
    If CAN_WKUP = 1, what kind of behavior will happen in TPS659413?

    Br,

    KS

  • In reply to ks:

    Hi KS,

    I checked on the latest PSDKLA release R5 bootloader software and the MCU-only boot feature is not supported there yet.  If I were to request this feature to be supported in a future release (TBD), then what is your requested timeframe for this bootloader feature to be supported?

    NOTE: another option here, to start your development, is to boot from OSPI flash in the regular way (full SoC boot), then develop your software to shut down the MAIN domain and put the SoC into "Deep Sleep" mode (this is NOT the same thing as Suspend-2-Ram "S2R" mode).  Then you can implement your CAN wake-up functionality from that point on (use the CAN_wkup signal to come out of Deep Sleep mode) and then restart the MAIN domain, etc.

    On your other question, the CAN wakeup signal doesn't seem to have a direct impact on the PMIC power state machine if the SoC is only going down into the "Deep Sleep" or "MCU-only" modes (compared to full "S2R" mode, where it does have a direct function).  In SoC "Deep Sleep" or "MCU-only" modes the PMIC power state is controlled by a different signal from the SoC.

    For more details on the PMIC power state machine transitions involved with each SoC power state (including turning back ON the MAIN domain power rails, etc., after coming out of the PMIC "MCU-only" mode), then take a look at Figure 3 and other related sections in the TPS6541x User's Guide here: http://www.ti.com/lit/ug/slvubr0/slvubr0.pdf

    Thanks,

    Jonathan

  • In reply to Jonathan Bergsagel:

    Hi, 

    We will need this feature in 5/S.

    Br,

    Ks 

  • In reply to ks:

    Hi KS,

    Sorry, I didn't understand the date listed in your last post.  Can you clarify what "5/S" refers to ?  Is that May, or September, or something else?

    NOTE: currently, neither PSDKRA or PSDKLA support the "MCU-only bootmode" feature in the hardware.  We need to add the secondary bootloader SW support for this.  It would likely need to be developed first in the PSDKRA bootloader (MCU SBL).

    Thanks,

    Jonathan

  • In reply to Jonathan Bergsagel:

    Hi, 

    I mean we will apply this feature in May.

    Thanks!

    br.

    KS

  • In reply to ks:

    KS,

    Ok, I will check with the program and see when we can get this feature added to our PSDKRA roadmap of releases.  It will partly depend on what other SW features we have to develop & release first.

    Note that the EVM with the PMIC control of the power rails is currently set to boot to SoC FULL-ACTIVE mode (with both MCU & MAIN domains powered) – and then transition into MCU-only mode via software control (for the SoC internally, and also for the signal to the PMIC).  It can then transition from MCU-only mode back to FULL-ACTIVE mode as desired (e.g., when you detect your CAN wake-up event).

    So, as I mentioned earlier, you could start your CAN wake-up feature development now, using that sequence above and then update it later once we release a bootloader with the capability to support booting up in the MCU-only mode.

    Let me know if this could work for you for the start of your feature development.

    Thanks,

    Jonathan