Been working on getting the i2c4 up and looking for the correct power-domain and clock, while looking found c7x stuff and it will need an overlay to turn it on. c7x is disabled. Those links are a step closer.
Here is the link. https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-1bSfTnVt5d/09.02.00.05/ti-processor-sdk-rtos-j722s-evm-09_02_00_05.tar.gz you need that. Only works in Linux though.
@Olof_Astrand Have you been successful booting the
ti-processor-sdk-rtos-j722s-evm-09_02_00_05-prebuilt
U-Boot SPL 2023.04-ti-gf9b966c67473 (Mar 19 2024 - 20:31:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--w2023.01-j722s (Kool Koa')
SPL initial stack usage: 17064 bytes
It starts then it is not handing it over. My question is regarding if you had luck getting it running, I am using a board that has been flaky out of the box. Our other board that does work is under test and cannot be disturbed.
Update: at the moment of writing I forgot about the board not having emmc. Just realized this and suspect that uboot and dtb will have to be modified to work on sd.
Yes. I do not think it Will work. The hardware is not compatible. Also make sure to download the latest image BeagleY-AI Debian 12.6 2024-07-11 XFCE - BeagleBoard it has newer firmware. Upgrading an oldler image did not work. Things gets really unstable when the firmware is started though. .
To some degree, yes, however it is very similar other than the stuff on the i/o header ( maybe wishful thinking). Core might be close, I am trying to find the default uboot config for the j722. Found some .yaml files where the config should be. At this point I am going a spend another hour on it before pulling the plug on this one.
Pretty sure the boards are on the 12.6 Debian. Might revisit this board down the road, stuff I have ran into is the i2c4 does not even have a description upstream in the .dtsi. I could be wrong but have not been able to find it, it stops at i2c3. Did find the interrupt along with reg for it and that was it, looking at the base for those they have a power config value that I cannot find. So how were they even able to test this board without a complete device tree…Does the driver even work past i2c3?