Other Parts Discussed in Thread: SK-AM64B, , SYSCONFIG, AM6442, SK-AM62B
Tool/software:
I've a custom AM6411 board derived from SK-AM64B. I've got a few questions.
I've got the debian trixie 11.00.09.04 (Apr 4, 2025) image burned and am trying to boot. Not working, you can see the log below. I'm not terribly surprised because...
- I presume I need to build a new dtb file to boot
- Do I also need to re-build U-boot stuff too?
Can you help me with a high level overview of what needs to be done?
I was hoping to generate the dts file using the SysConfig tool, but I'm a bit confused about this. Seems there are multiple ways to run the SysConfig tool.
(1) I don't seem to be able to configure the DDR memory here.
https://dev.ti.com/sysconfig
Note in this first method to run the SysConfig, I do not select a software product. I've used this in the past to configure different hardware with AM6442 (with AM6442 selected instead).
But it seems I'm unable to get the ddr to actually configure? Is this something I need to worry about? I imagine I need to specify the size?
However, I see I can run this tool in a different fashion, with Software Product selected for DDR.
Now I get stuff for ddr config... how am I supposed to use this? I see you link to the README: https://dev.ti.com/tirex/content/Processor_DDR_Config_0.10.32.0000/docs/README.html
However I think my memory may be the same from the AM6442 --> AM6411, so ideally I don't need to bother with this, but I'm confused a bit how running the SysConfig in these different methods should be used.
(2) Is there a way I'm supposed to be able to disable the other cores since I'm using AM6411?
- Like SDK hit has k3-am642-sk.dts which includes k3-am642.dtsi
- Do I need to create a new k3-am641.dtsi that doesn't include the second core?
- And make myself a k3-am641-myboard.dts?
- Anything with U-boot?
For the record, here's the log of what I've got now:
U-Boot SPL 2025.01-00406-gcd91d7360181 (Mar 25 2025 - 16:14:37 +0000) Resetting on cold boot to workaround ErrataID:i2331 Please resend tiboot3.bin in case of UART/DFU boot resetting ... U-Boot SPL 2025.01-00406-gcd91d7360181 (Mar 25 2025 - 16:14:37 +0000) SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)') EEPROM not available at 0x50, trying to read at 0x51 Reading on-board EEPROM at 0x51 failed -121 SPL initial stack usage: 13392 bytes U-Boot SPL 2025.01-00406-gcd91d7360181 (Mar 25 2025 - 16:14:37 +0000) Resetting on cold boot to workaround ErrataID:i2331 Please resend tiboot3.bin in case of UART/DFU boot resetting ... U-Boot SPL 2025.01-00406-gcd91d7360181 (Mar 25 2025 - 16:14:37 +0000) SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.7--v11.00.07 (Fancy Rat)') EEPROM not available at 0x50, trying to read at 0x51 Reading on-board EEPROM at 0x51 failed -121 SPL initial stack usage: 13392 bytes