AM3358: Bring up SDK9.03 Linux Kernel 6.1.y with U-BOOT 2012

Tony Tang

Mastermind 28992 points

Part Number: AM3358

Tool/software:

Customer plan to upgrade from SDK6(year 2012) to latest SDK9.03.

#1. Would like to keep using the old U-boot 2012, launch up Kernel fail as log, is it possible to use it in this way?

/cfs-file/__key/communityserver-discussions-components-files/791/dmest.txt

#2. How to use parallel NOR boot in SDK9.03? there is not am335x_evm_nor_config / am335x_evm_norboot_config in UBOOT, is there a way to bring back NOR boot support?

6 months ago

0 Bin Liu 6 months ago

TI__Guru**** 168211 points

Hi Tony,

The kernel crash is likely due to the used AM335x device is not a super set device but the kernel devicetree enable a module which doesn't exist.

Do you know if this AM335x doesn't have, for example, GPU or PRU, or any other module? then we can disable it in devicetree to fix the kernel crash.

0 Tony Tang 6 months ago in reply to Bin Liu

TI__Mastermind 28992 points

Customer said they are working on AM3358, read out DEV_FEATURE register is 0x20FD0383. it is AM3358 according to this thread:

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/662526/linux-am3351-dev_feature-register

0 Bin Liu 6 months ago in reply to Tony Tang

TI__Guru**** 168211 points

Hi Tony,

AM3358 should have all peripherals, not sure what is failing. Please ask the customer to apply the following kernel patch to print the module name in kernel boot log before probing. It might give a hint on which peripheral is failing.

diff --git a/drivers/bus/ti-sysc.c b/drivers/bus/ti-sysc.c
index 15c6b85b125d..fb002ddfb74f 100644
--- a/drivers/bus/ti-sysc.c
+++ b/drivers/bus/ti-sysc.c
@@ -3299,6 +3299,7 @@ static int sysc_probe(struct platform_device *pdev)
        if (!ddata)
                return -ENOMEM;
 
+       dev_info(&pdev->dev, "probling\n");
        ddata->offsets[SYSC_REVISION] = -ENODEV;
        ddata->offsets[SYSC_SYSCONFIG] = -ENODEV;
        ddata->offsets[SYSC_SYSSTATUS] = -ENODEV;

0 Tony Tang 6 months ago in reply to Bin Liu

TI__Mastermind 28992 points

Hi Bin,

log with patch, seems like RTC module is not powered, disable it to test again, will post back.

/cfs-file/__key/communityserver-discussions-components-files/791/am335x-dmesg_5F00_logpatch.txt

+1 Bin Liu 6 months ago in reply to Tony Tang

TI__Guru**** 168211 points

Hi Tony,

Yes, 0x44e3e000 is RTC.

I forgot all the details of AM335x RTC, but I guess by default all AM335x EVMs have external rtc clock, so devicetree configures the RTC module to use external clock, but the custom board doesn't have an external RTC clock? so the RTC module is not clocked which causes driver reading RTC register failed.

So disabling target-module@3e000 module in am33xx-l4.dtsi should fix this problem.

Processors

Processors forum

AM3358: Bring up SDK9.03 Linux Kernel 6.1.y with U-BOOT 2012