umbramalison_alt has quit [Quit: %So long and thanks for all the fish%]
umbramalison has joined #u-boot
<samueldr>
hi, I screwed-up sending a patch, hadn't caught my mail client wrapped lines (ugh), and I can't find the patch submitting guidelines on the U-Boot website, were they removed?
<milkylainen>
OT. Anyone here good at C openssl key handling questions? Tried #openssl. But that channel is completely dead. Question related to stm32 image signing.
GNUtoo has joined #u-boot
indy has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
camus has quit [Read error: Connection reset by peer]
camus has joined #u-boot
<hramrach>
milkylainen: they have a mailinglist which is not completely dead
<milkylainen>
hramrach: I think I've solved it. But thanks anyway. I had some issues understanding ec curve similarities and names.
<hramrach>
when I tried to do signing I tried to massage the openssl tool to do it, and then found a perl reimplementation of Linux sign-file, and bent that slightly to do the requested format
<hramrach>
because the openssl code iss worse than perl
<milkylainen>
hramrach: I'm done with my stm32mp1-sign.c. I've tried it on hw.
GNUtoo has quit [Remote host closed the connection]
persmule has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
persmule has joined #u-boot
aggi has joined #u-boot
<vagrantc>
hrm. both 2022.07 and 2022.10-rc2 seem to load a kernel just fine, but no nvme or mmc block devices show up once linux is booted. same exact configuration with 2022.04 seems to work.
<vagrantc>
it may also have a different arm-trusted-firmware version...
<vagrantc>
what sort of things cause those sorts of issues?
* vagrantc
has a growing list of boards that do not work with u-boot 2022.04+ :/
<vagrantc>
hmmm... also major toolchain differences between versions ...
<hramrach>
missing it breaks i2c which breaks pmic which breaks Linux
<hramrach>
and like the i2c does not come back even in Linux, have to reet the board
lucascastro has joined #u-boot
<vagrantc>
"reet" ?
<vagrantc>
reset?
aggi has quit [Quit: connection closed.]
lucascastro has quit [Ping timeout: 252 seconds]
torez has quit [Quit: torez]
adip has quit [Ping timeout: 252 seconds]
<hanetzer>
so, in theory. if I have full proper jtag and serial for a device, the 'ideal' mechanism would be loading spl into sram and executing it to init dram (doing whatever dev is needed to make that work) and loading u-boot proper into dram after that?
<marex>
yes
<hanetzer>
as my serial adapter is kaput (shitty header broke off the cable, waiting on some non-shit replacements to arrive tomorrow) I'm mostly flying blind atm
<marex>
hanetzer: time to buy soldering iron and start fixing all the broken hardware ? :)
<hanetzer>
I already own one :P
<marex>
it might take less time and save money ;-)
<hanetzer>
its just a tiny ass picoblade connector
<hanetzer>
that said, re: the openocd/jtag proc, is there any 'official' guide on that so I'm not fumbling too hard?
* vagrantc
is tempted to just solder all the boards together indiscriminently and be done with all the things :)
* vagrantc
just found an old board that has been running for years doing nothing
<marex>
vagrantc: toss them into a can of molten tin no less ?
<marex>
like the end scene of terminator 2 ... heh