How to enable/use wake-up domain UART for collecting EthFw debug logs? when we not have Main Domain UART on Board.
When running EthFw with HLOS, we can get the EthFw Debug logs to HLOS using the trace command (using remoteproc), as EthFw will log the debug prints in trace buffers.
Command to get the EthFw trace buffer logs to HLOS is as follows:
# cat /sys/kernel/debug/remoteproc/remoteproc*/trace0
If still required to use the wake-up domain UART for Ethfw debug logs, we need to make the following changes in EthFw and UART Driver in pdk.
1. EthFw update to use wake-up domain UART:
Update the UART Soc Domain and Instance as shown in the below, form “board_soc_evm.c” file in the EthFw directory.
Ex: for J721E, the file name will be ” board_j721e_evm.c”.
2. PDK UART driver update to allow using cross-domain UART.
Comment “UART_socInit” as it will overwrite the UART Instance Base Address with Main Domain UART’s, as it will not allow use of cross-domain UART.
After making the above changes, rebuild the EthFw application and use the latest binaries.
Default Port will be configured for 115200 Baud rate, open wake-up UART, and check EthFw debug logs.
Note:
1. Ideally, it is not recommended to use cross-domain as SDK doesn’t support complete UART features in this cross-domain access like Interrupt mode is not supported.
2. You can only use this for stdio functionality like debug logs and so on.
3. Along with EthFw logs, you may observe the TIFS FW logs on the same UART (like firewall exceptions). It may conflict with the EthFw messages.
Best Regards,
Sudheer
