Closed danh-arm closed 8 years ago
I updated the description here to make the distinction between the UARTs used on the cold boot path and the UARTs used at runtime.
For BL3-1 and BL3-2, these UARTs change between cold boot time and runtime. Supporting this requires additional platform hooks in the BL entrypoint (or main function) to allow platform code to re-initialize the console when the BL has finished its part in the cold boot path.
Until this supported properly, an interim solution will be to:
An update to the issue description. We decided that the TSP will use the runtime console for all output because of the complexities involved in synchronous and asynchronous initialization of TSP (depending on TSP_INIT_ASYNC build flag).
The way that UARTs are used by TF in the FVP and Juno ports is inconsistent. The FVPs have 4 UARTs available for use, UART0 - UART3. Juno also has 4 UARTs but 2 of these are SoC UARTs, which are exposed via connectors on the back panel, and 2 are FPGA UARTs, which are only accessible via headers on the motherboard (J55 and J56).
The current usage is as follows:
The issues with this are as follows:
So the proposed changes are as follows:
* = changed UARTs