rburkholder has quit [Remote host closed the connection]
umbramalison has quit [Quit: %So long and thanks for all the fish%]
umbramalison has joined #u-boot
thopiekar has quit [Ping timeout: 252 seconds]
thopiekar has joined #u-boot
mmu_man has quit [Ping timeout: 248 seconds]
jclsn has quit [Ping timeout: 246 seconds]
jclsn has joined #u-boot
sigmaris has quit [Ping timeout: 248 seconds]
vagrantc has joined #u-boot
sigmaris has joined #u-boot
akaWolf has quit [Ping timeout: 246 seconds]
rburkholder has joined #u-boot
hanetzer has quit [Ping timeout: 260 seconds]
hanetzer has joined #u-boot
akaWolf has joined #u-boot
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #u-boot
hanetzer has quit [Ping timeout: 260 seconds]
hanetzer has joined #u-boot
ikarso has joined #u-boot
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #u-boot
vagrantc has quit [Quit: leaving]
mncheck has joined #u-boot
frieder has joined #u-boot
guillaume_g has joined #u-boot
m5zs7k has quit [Ping timeout: 272 seconds]
m5zs7k has joined #u-boot
akaWolf has quit [Ping timeout: 248 seconds]
<PhoenixMage>
Should "boot_fit [addr]" kick off the boot process or is there a followup command? After running it my u-boot prompt changes to "## Booting FIT Image =>" like its waiting for more input
mckoan|away is now known as mckoan
macromorgan has quit [Read error: Connection reset by peer]
prabhakarlad has joined #u-boot
akaWolf has joined #u-boot
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #u-boot
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #u-boot
Manouchehri has quit [Ping timeout: 252 seconds]
Manouchehri has joined #u-boot
apritzel__ has joined #u-boot
prabhakarlad has quit [Ping timeout: 260 seconds]
prabhakarlad has joined #u-boot
davlefou has quit [Ping timeout: 268 seconds]
davlefou has joined #u-boot
<PhoenixMage>
When I run attempt to extract my kernel subimage from my FIT image I am getting "Error: inflate() returned -5" and I am unable to find any useful info on that error anywhere. Does anyone have any idea?
<PhoenixMage>
Could I be overwriting something when I am attempting to extract it? The data size is 7.4M
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
mmu_man has joined #u-boot
<Tartarus>
Well, from errno, 5 is EIO
<Tartarus>
And boot_fit is a script / variable, depending on your platform, not a standard command
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
akaWolf has quit [Ping timeout: 260 seconds]
<PhoenixMage>
Sorry, what is EIO?
<PhoenixMage>
Good to know on the boot_fit thing, I would prefer to keep things more standard
<Tartarus>
#define EIO 5 /* I/O error */
<PhoenixMage>
Is it possible to tell what version of u-boot produced a fit image?
<PhoenixMage>
I believe there was a change in the image layout at some stage? And I am stuck using a legacy vendor version atm because rk3568 :/
<Tartarus>
That shouldn't matter
<PhoenixMage>
So, potentially a corrupt kernel image in the FIT Image?
<PhoenixMage>
I am out of ideas, there isnt a lot of feedback
<PhoenixMage>
(from the cli)
<Tartarus>
Well, you can use "bootm" directly instead of whatever boot_fit is doing, and maybe that'll explain a bit more what's going on
<PhoenixMage>
Oh yeah, was already trying that but it doesnt give any feedback either
<PhoenixMage>
All I get is "No misc partition", loading kernel from FIT Image at <addr> says its using the config from the fit, complains about optee (which I believe is normal) then "### ERROR ### Please RESET the board ###"