TDA2EVM5777: SBL multicore mailbox EVE UART output issues

Hi Rishabh

   What you mean "wait for SBL to finish"?

   Is it the time when the "EVE1 boot-up successfully" log is output means "SBL is finish"? Because both A15 and EVE's main function have been implemented  at this moment.

   I did the UART init in EVE app as follows, but it still did not work:

1  "sbl_mbx_eve1.c"

uint32_t uartBaseAddr = SOC_UART1_BASE;

void padConfig_prcmEnable()

{

   /*Pad configurations */

   HW_WR_REG32(SOC_CORE_PAD_IO_REGISTERS_BASE+CTRL_CORE_PAD_UART1_RXD,0x00040000);

   HW_WR_REG32(SOC_CORE_PAD_IO_REGISTERS_BASE+CTRL_CORE_PAD_UART1_TXD,0x00000000);

   /* Set the UART Parameters */

   UARTConfigInit(uartBaseAddr, BAUD_RATE_115200, UART_WORD_LENGTH_8, UART_STOP_BIT_1, UART_NO_PARITY,

                   UART_16x_MODE);

}

void main(void) {

   uint32_t msg = 'D';

   /* Wait for message from MPU */

   while (MESSAGE_INVALID ==

          MailboxGetMessage(SOC_MAILBOX2_BASE, MAILBOX_QUEUE_6, &msg)) ;

   /* Send ack message to MPU */

   MailboxSendMessage(SOC_MAILBOX9_BASE, MAILBOX_QUEUE_0, 0xAA55FF00);

   /*Pad configuration and PRCM enable*/

   padConfig_prcmEnable();

   UARTConfigPuts(uartBaseAddr,"\r\nEVE1 main UARTConfigPuts\r\n ", -1);

   while (1) ;

}

Which is the same as "sbl_mbx_mpu_cpu0.c", but no "EVE1 main UARTConfigPuts" log output.

2

uint32_t uartBaseAddr = SOC_UART2_BASE;

void padConfig_prcmEnable()

{

   /*Pad configurations */

   HW_WR_REG32(SOC_CORE_PAD_IO_REGISTERS_BASE+CTRL_CORE_PAD_UART2_RXD,0x00040000);

   HW_WR_REG32(SOC_CORE_PAD_IO_REGISTERS_BASE+CTRL_CORE_PAD_UART2_TXD,0x00000000);

   /* Set the UART Parameters */

   UARTConfigInit(uartBaseAddr, BAUD_RATE_115200, UART_WORD_LENGTH_8, UART_STOP_BIT_1, UART_NO_PARITY,

                   UART_16x_MODE);

}

void main(void) {

   uint32_t msg = 'D';

   /* Wait for message from MPU */

   while (MESSAGE_INVALID ==

          MailboxGetMessage(SOC_MAILBOX2_BASE, MAILBOX_QUEUE_6, &msg)) ;

   /* Send ack message to MPU */

   MailboxSendMessage(SOC_MAILBOX9_BASE, MAILBOX_QUEUE_0, 0xAA55FF00);

   /*Pad configuration and PRCM enable*/

   padConfig_prcmEnable();

   UARTConfigPuts(uartBaseAddr,"\r\nEVE1 main UARTConfigPuts\r\n ", -1);

   while (1) ;

}

I uesd the UART2 to replace the UART1, but this method did not work too.

And from the Schematic of TDA2X EVM, the USB terminal is connected to UART1 only:

So is it only UART1 can be used in the apps?

Thanks

xuanbo

Hi Xuanbo,

SBL runs on master A15. A15 parses the application image and after identifying/loading app images present in multi core image will bring the slave cores out of reset one by one. First is IPU, then DSPs and then EVEs. Then it will print timing statistics. After that SBL will jump to A15 app. Till the point SBL has not jumped to A15 application SBL is not finished.

On the EVM UART2 is not connected so you should use UART1.

Regards,
Rishabh

Hi Rishabh

Thank you for your reply.
I know the SBL flow as you said, "load image, reset slave cores, then jump to master core's binary which is the A15 app". Does the main function of "sbl_mbx_mpu_cpu0.c" is the A15 app? My previous understanding is that "sbl_mbx_mpu_cpu0.c"'s main function is the app of A15, and "sbl_mbx_eve1.c"'s main function is the EVE app. So when the "EVE1 boot-up successfully" log is output, the A15 app has been jumped in and implemented, which means SBL is finished? But from what your said above, i think my understanding is wrong.
So which part is A15 app, and which is EVE app?

Thanks
xuanbo

By the way, the whole log is:

TDA2xx SBL Boot

DPLL Configuration Completed

Clock Domain Configuration Completed

Module Enable Configuration Completed

TI EVM PAD Config Completed

DDR Config Completed

App Image Download Begins

SD Boot - file open completed successfully

Trying to boot App Image with header version 1

MPU CPU0 Image Load Completed

DSP1 Image Load Completed

EVE1 Image Load Completed

App Image Download Completed

Putting MPU CPU1 in Off mode

EVE MMU configuration completed

EVE MMU configuration completed

EVE MMU configuration completed

EVE MMU configuration completed

*****************************************************************

PMCCNTR counts once every 64 clock cycles, multiple by 64 to get actual CPU cycles

SBL Initial Config Cycles - 114701 (9.78 ms)
SOC Init Cycles - 264161 (22.54 ms)
DDR Config Clock Cycles - 68023 (5.80 ms)
App Image Load Cycles - 814209 (69.47 ms)
Slave Core Bootup Cycles - 323094 (27.57 ms)
SBL Boot-up Cycles - 1585525 (135.29 ms)
Time at which SBL started IPU1_0 - 10895 (0.92 ms)
*****************************************************************

Jumping to MPU CPU0 App

Multicore Mailbox app - MPU-Core0 Master core

EVE1 boot-up successfully

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Before the "EVE1 boot-up successfully", there is " Jumping to MPU CPU0 App ", so my previous understanding is that the main function of "sbl_mbx_mpu_cpu0.c" is the A15 app.