Hello Ti team,
We need to change the u-boot debug console from main_uart0 (default) to main_uart2.
Can we do this ?
If yes, please let us know the changes required for the same.
Regards
Ishan.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello Ti team,
We need to change the u-boot debug console from main_uart0 (default) to main_uart2.
Can we do this ?
If yes, please let us know the changes required for the same.
Regards
Ishan.
Hi Ishan,
I have assigned the query to our expert, in the meantime, please look into these threads and see if it can be of any help.
Best Regards,
Suren
Hi Ishan,
the first link Suren pointed to has much of the needed info, however we need different custom clk-data.c and dev-data.c files to support a clock ID of 153 (needed for main_uart2) instead of 155 (associated with main_uart4). I'm working on getting those files generated, and will circle back here soon.
Regards, Andreas
Thanks, Andreas. Looking forward to getting the required clk and dev files as we need to resolve this ASAP for our custom board.
Thanks,
Anil Patel
Hi Anil,
I'm still waiting for the files; just send a reminder to the developer. There's also a way to update the clk-data.c and dev-data.c files manually to add a new device ID and all related definitions (I've done it before) but it is rather painful and error-prone, not something you want to debug while also trying to bring up a custom board. I know we have a way to generate those in a scripted-fashion, which will be the better approach.
Will keep you posted.
Regards, Andreas
Thanks, Andreas.
I totally rely on your provided clk and dev files as they should be error-free. Looking forward to get that soon.
Regards,
Anil
Hello Andreas/ Bin Liu
Is there any update on this?
We are waiting for the files. Pls run the script at your end and provide that.
Regards,
Anil
Hi Anil,
I since got a hold of the script; will start trying to get this configured and running here very soon.
Regards, Andreas
Hi Anil,
just a quick update; I have the script running but U-Boot SPL isn't working yet the way it should so I'm actively debugging this atm. Will be in touch.
Regards, Andreas
Thanks Andreas. Please Let me know when u have those files working correctly.
Regards,
Anil
Hi Anil,
I was able to generate updated arch/arm/mach-k3/am62x/clk-data.c and arch/arm/mach-k3/am62x/dev-data.c SoC data files for you to plug into ti-u-boot-2023.04 (used as part of SDK v9.x) that are functionally equivalent (in terms of supported device IDs) to what was already in there except it now supports main_uart2 instead of main_uart0 (also meaning, support for main_uart0 was removed!).
Can you please give these files a try. Note that you'll also need to make other modifications as referenced in the earlier threads to actually make use of that new UART instance for your U-Boot console, the updated SoC data is only a piece of this puzzle.
Regards, Andreas
/cfs-file/__key/communityserver-discussions-components-files/791/1464.clk_2D00_data.c
/cfs-file/__key/communityserver-discussions-components-files/791/4188.dev_2D00_data.c
Thanks, Andreas.
With your given files, I am able to get uboot logs on the desired UART (main_uart2)
Regards,
Anil
With your given files, I am able to get uboot logs on the desired UART (main_uart2)
Awesome, glad to hear! Let's close this thread then.
Regards, Andreas