TDA4VM: Clarification on dev-boot mode

Hi,

Apologies this was in a wrong state. What is the exact use case here? Do you want to run some use case using dev-boot mode?
Can you add more details?

- Keerthy

Hi Keerthy,

thanks for your reply. The basic use case is to reduce the time it takes to connect the TDA4VM to a CCS Debug session (Currently this takes about 3 min and is done via Blackhawk XDS560v2 Debugger on Linux VM and the default launch.js script provided by TI). As a first approach, I wanted to avoid the launch.js + GEL functions, since parts of this config are already done by the ROM codes (DMSC,R5) and SPL/SBL. Please correct me, if this is a wrong assumption.

This is where dev-boot mode comes in. Since DMSC ROM Code + R5 ROM Code are doing part of the configurations, which are done by the launch.js script (in connection with the OnTargetConnect() GEL function), in specific configuring PLLs and PSCs, I thought, that starting from this point I can load applications to mcu2_0 or other cores (Maybe it is necessary to start SPL/SBL on mcu1_0 first). See also this thread in e2e: https://e2e.ti.com/support/processors/f/processors-forum/993957/tda4vm-about-dmsc-rom-code-and-r5-rom-code).

Thanks and best regards,

Felix

Felix,

Then can you just boot to u-boot prompt and then attach. If you do not want to go through the entire 3 minutes. U-boot comes up in few seconds
and you can connect to R5 or the A72 cores. Will that work for you?

- Keerthy

Hi Keerthy,

Hmm, I already tried that, but CCS throws errors, when I try to connect to MCU2_0, MCU2_1, MCU3_0, MCU3_1:

"Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 9.2.0.00002)"

Unfortunately, the proposed solutions (power cycle, JTAG settings) do not work.

My setup: I try to boot from SD card with unmodified boot files. So also the default firmware in lib/firmware, which gets loaded to the R5s are untouched. The Target Configuration File is without the GEL file for the DMSC, because this config is done by SPL and ROM Code I think.

I also got one additional question: Is TDA4VM, when halted at U-Boot prompt, in a smiliar state as it would be after running launch.js in No-Boot Mode? Are there any differences in configuring PLLs or PSCs?

Thanks again for your help and best regards,

Felix

Hi Keerthy,

I could solve the issue. It seemed, that MCU2_0 had to be started first in U-Boot in order to connect to it.

Thanks and best regards,

Felix