[Buildroot] [PATCH v12 00/16] Add support for AM62x-SK HS-FS devices

Andreas Dannenberg dannenberg at ti.com
Wed Apr 10 09:23:06 UTC 2024 

Gero, Dario, All,

On Wed, Apr 10, 2024 at 03:24:29AM -0500, Andreas Dannenberg via buildroot wrote:
> Gero, Dario,
> 
> On Wed, Apr 10, 2024 at 10:00:06AM +0200, Gero Schwäricke via buildroot wrote:
> > On Wed, Apr 10, 2024 at 09:34:16AM +0200, Dario Binacchi wrote:
> > > Hi Romain, All
> > > 
> > > On Tue, Apr 9, 2024 at 11:17 PM Romain Naour <romain.naour at smile.fr> wrote:
> > > >
> > > > Hello Arnout, All,
> > [...]
> > > >
> > > > Thanks, the series is merged.
> > > >
> > > > Thanks to Dario and Michael for the initial work on the HS-FS topic!
> > > >
> > > > The initial series showed that it was necessary to rework heavily the TI K3 SoC
> > > > related packages in Buildroot. This was the opportinity to anticipate on the
> > > > addition of new TI K3 SoC support.
> > > >
> > > > Thanks to Andreas and Bryan from TI for the review and fine details about TI K3
> > > > SoC familly and the runtime testing.
> > > >
> > > > Thanks to all testers and reviewers.
> > > 
> > > I think my two patches for version 10 were ultimately lost:
> > > 
> > > [v10,05/12] package/ti-k3: disable HS-FS for AM65 SOC
> > > [v10,04/12] package/ti-k3: move TI_K3_{SECTYPE, SOC} out of the image-gen scope
> > > 
> > > Specifically, patch 4 is necessary for the proper creation of the
> > > image. Has version 12 actually been tested by anyone?
> > > I can assure you version 10 has been.
> > > 
> > > Additionally, it seems that patch
> > > [v10,02/12] boot/ti-k3-r5-loader: set binman environment
> > > has been incorporated into your patch "boot/ti-k3-r5-loader: remove
> > > BR2_TARGET_TI_K3_R5_LOADER_USE_BINMAN"
> > > and I don't understand why.
> > > 
> > > Thanks and regards,
> > > Dario
> > 
> > Hi Dario,
> > 
> > I can confirm that something is amiss, maybe it would have been better
> > to await more tests with patch V12.
> 
> I just tested top-of-master w/o any additional patches on SK-AM62 (with
> GP silicon) and SK-AM62B (production board, with HS-FS silicon) and it
> worked like a champ. Here's the beginning of the boot using SK-AM62...

I also just tested top-of-master with SK-AM64 (with GP silicon) and
SK-AM64B (production board, with HS-FS silicon) successfully. With this
I can boot on all 4 board/silicon variants without any issues. This was
done using commit...

d01e13c4d4 ("package/python3: fix cross builds when host and target use the same SOABI")

So from my POV there is no issue with missing patches.

--
Andreas Dannenberg
Texas Instruments Inc


> 
> <...snip...>
> U-Boot SPL 2024.01 (Apr 09 2024 - 20:11:30 -0500)
> SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
> SPL initial stack usage: 13368 bytes
> Trying to boot from MMC2
> Authentication passed
> Authentication passed
> Authentication passed
> Authentication passed
> Authentication passed
> Starting ATF on ARM64 core...
> 
> NOTICE:  BL31: v2.7(release):v2.7
> NOTICE:  BL31: Built : 20:08:16, Apr  9 2024
> I/TC:
> I/TC: OP-TEE version: Unknown_4.0 (gcc version 12.3.0 (Buildroot
> 2024.02-416-gd01e13c4d4)) #1 Wed Apr 10 01:08:14 UTC 2024 aarch64
> I/TC: WARNING: This OP-TEE configuration might be insecure!
> I/TC: WARNING: Please check
> https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
> I/TC: Primary CPU initializing
> I/TC: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill
> Capybar')
> I/TC: HUK Initialized
> I/TC: Activated SA2UL device
> I/TC: Enabled firewalls for SA2UL TRNG device
> I/TC: SA2UL TRNG initialized
> I/TC: SA2UL Drivers initialized
> I/TC: Primary CPU switching to normal world boot
> 
> U-Boot SPL 2024.01 (Apr 09 2024 - 20:11:48 -0500)
> SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
> SPL initial stack usage: 1872 bytes
> Trying to boot from MMC2
> Authentication passed
> Authentication passed
> 
> 
> U-Boot 2024.01 (Apr 09 2024 - 20:11:48 -0500)
> 
> SoC:   AM62X SR1.0 HS-FS
> Model: Texas Instruments AM625 SK
> DRAM:  2 GiB
> Core:  56 devices, 23 uclasses, devicetree: separate
> MMC:   mmc at fa10000: 0, mmc at fa00000: 1
> Loading Environment from nowhere... OK
> In:    serial at 2800000
> Out:   serial at 2800000
> Err:   serial at 2800000
> Net:   eth0: ethernet at 8000000port@1
> Hit any key to stop autoboot:  0
> <...snip...>
> 
> 
> > At least my current test of ti_am62x_sk_defconfig on master failed to boot:
> > 
> >   U-Boot SPL 2024.01 (Apr 10 2024 - 09:32:17 +0200)
> >   k3_system_controller sysctrler: k3_sysctrler_start: Boot Notification response failed. ret = -110
> >   Firmware init failed on rproc (-110)
> > 
> >   resetting ...
> > 
> > I tested with AM62x SK EVM E3. I'll try to apply your two missing
> > patches and test again.
> 
> Are you using a board with PCB revision 'PROC114E3'? If so this board is
> known as 'Third prototype, early release revision of the AM62x SK EVM'
> and should have GP silicon. Which means you must have re-added...
> 
> BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN="tiboot3-am62x-gp-evm.bin
> 
> ...to your .config?
> 
> I don't have a PROC114E3 board but the board I used to test the GP
> variant today is a PROC114E2, and it worked. But neither of those boards
> is considered "production".
> 
> Also just for refernce, an SK-AM62 PCB revision history can be found in
> Table 1-1 in the AM62x SK EVM User's Guide [1].
> 
> 
> --
> Andreas Dannenberg
> Texas Instruments Inc
> 
> 
> [1] https://www.ti.com/lit/pdf/spruj40 
> 
> 
> 
> 
> > Best,
> > Gero
> > 
> > > > Best regards,
> > > > Romain
> > > >
> > [...]
> > 
> > -- 
> > 
> > 
> > 
> > –––
> > 
> > 
> > grandcentrix GmbH | A Vodafone Company · Holzmarkt 1 · 50676 
> > *Cologne* | Phoenixseestrasse 18 · 44263 *Dortmund* · Germany
> > | in 
> > <https://www.linkedin.com/company/grandcentrix> | phone: +49-221-677-860-0 
> > | email: hello at grandcentrix.net <mailto:hello at grandcentrix.net>
> > 
> > 
> > grandcentrix cares about privacy 
> > <https://grandcentrix.net/de/pages/privacymail/>
> > 
> > Amtsgericht Köln | HRB  
> > 70119 | Geschäftsführer: M. Krömer,  R. Hänel | USt.-IdNr.: DE266333969
> > 
> > _______________________________________________
> > buildroot mailing list
> > buildroot at buildroot.org
> > https://lists.buildroot.org/mailman/listinfo/buildroot
> _______________________________________________
> buildroot mailing list
> buildroot at buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

More information about the buildroot mailing list