<clarity>
Hmm you don't have usb gadget support in SPL?
<clarity>
SPL_USB_GADGET, SPL_USB_SDP_SUPPORT etc
<Harm>
clarity: As far as I know the imx8mn does that through the ROM api. I'm using the uuu tool from NXP to load u-boot and that is using the SDP
<mrnuke>
sjg1: Are you working on #ifdef stuff that touches or relocates padding_pkcs_15_verify(). I'm seein gsome undefined reference to padding_pkcs_15_verify in v2021.10-rc2, and I think it's a combination of previous ECDSA work, and our improvements to the #ifdef stack
fdanis is now known as fdanis_away
<clarity>
Harm: Yea that's what I'm after. What happens is that it loads SPL through uuu, but then SPL doesn't know how to load the next part.. I assume SPL needs sdp support too
<Harm>
And that's happening just fine on my board using that config. Can't that be done through the ROM API on your board?
<clarity>
What would the code for that be called?
<Harm>
I think this is the code: /arch/arm/mach-imx/spl_imx_romapi.c
<clarity>
Aha
<clarity>
I'll look into it, never saw that before
<Harm>
Right, so you'll need the SDP code inside SPL then
<marex>
apparently different MX8Ms have different bootroms implemented by different engineering teams, so they have different features and different bugs
<Harm>
wow
<marex>
yes, it sucks
<marex>
MX8MN/MP for example doesn't support persist-secondary-boot (reboot into B-copy of bootloader with the option of falling back to A-copy using watchdog cold boot if B-copy is broken, e.g. in case broken update got installed)
<marex>
MX8MM still supported that ...
<marex>
yes, on MM/MQ , you will need UDC support in SPL ...
<marex>
you can hack out the dependency on ATF (which really is mostly useless on MX8M) to free up some space in the OCRAM
<marex>
on mx8mm, the ATF is at 0x960000 onward, so that could be freed up
<Harm>
I know I can control from which eMMC boot partition I'm booting by setting a flag in the eMMC. Also, when I zero out the first boot partition it automatically tries starting from the second on my 8MN
brujah has joined #u-boot
brujah_ has joined #u-boot
brujah_ has quit [Client Quit]
<Harm>
Won't you need ATF for enabling other CPU cores and power saving modes/cpu frequncy scaling?
<marex>
sure, it will, except for recovery and u-boot you dont really care
<Harm>
yeah
jwillikers has quit [Remote host closed the connection]
jwillikers has joined #u-boot
LokeshVutla has quit [Remote host closed the connection]
brujah has quit [Quit: Leaving]
jwillikers has quit [Remote host closed the connection]
alpernebbi has quit [Quit: alpernebbi]
jwillikers has joined #u-boot
<sjg1>
mrnuke: No not me
<mrnuke>
sjg1: Okay. I'll go ahead and write the fix
redbrain has quit [Ping timeout: 240 seconds]
vagrantc has quit [Quit: leaving]
LeSpocky has quit [Quit: leaving]
agust has quit [Quit: Leaving.]
vagrantc has joined #u-boot
Zapy has quit [Ping timeout: 245 seconds]
<mrnuke>
I'm trying to run the RSA tests in test/lib/rsa.c using " NO_SDL=1 ./test/py/test.py --bd sandbox --setup-show -krsa"
<mrnuke>
but I'm seeing "840/840 deselected" and no test actually runs
<mrnuke>
grep UT_LIB_RSA build-sandbox/.config shows that "CONFIG_UT_LIB_RSA=y" is indeed selected
Zapy has joined #u-boot
jwillikers has quit [Remote host closed the connection]
tlwoerner has quit [Read error: Connection reset by peer]
tlwoerner has joined #u-boot
<rfs613>
mrnuke: just a wild guess here, perhaps you also need CONFIG_RSA or similar options set?
<rfs613>
test/lib/rsa.c seems to be conditional on CONFIG_RSA_VERIFY_WITH_PKEY