<mwalle>
marex: btw, I have an USB key which still triggers the "EHCI timed out on TD" error. Are you aware that this still is an issue? Unfortunately, I don't have time to dig into that, I just used another thumb drive for now
mmu_man has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
<marex>
mwalle: with mainline u-boot ?
<marex>
mwalle: with ehci hcd ?
<marex>
the transfer length issues should've been fixed since
<marex>
so this is likely something else
<mwalle>
marex: mainline u-boot yes, on a kirkwood soc, so ehci i guess?
<mwalle>
marex: I'm converting the lsxl board to DM_* right now and just noticed that usb doesn't work
<mwalle>
marex: oh, it is not always the case btw. so i'd say you have a 50% chance that it will work (with a smaller file)
<marex>
mwalle: do you know how small is the file ?
<marex>
iirc the breaking limit is 16*512B and 240*512B or so
mmu_man has quit [Ping timeout: 268 seconds]
<hanetzer>
now if I could reliably figure out how to get openocd to do what I want it to I'd be in business.
<marex>
hanetzer: try #openocd
<hanetzer>
did, making some progress.
<marex>
oh, I see they sent you here, heh
<hanetzer>
nah
<hanetzer>
well, they may have. but if they did, I didn't notice it yet :P
<hanetzer>
I suppose 'check the linux/u-boot source' could be considered that :)
<marex>
hanetzer: you dont have either nTRST / nSRST ?
<hanetzer>
I only have nTRST. no SRST. (iirc that's muxed with the emmc somehow)
<mwalle>
marex: I can have a look later at home, but it was an arm kernel binary, so not that small
<mwalle>
(in contrast to an initramfs I meant)
<marex>
hanetzer: isnt that enough ?
<marex>
reset_config trst_only
<hanetzer>
doesn't seem like it. unless I'm mistaken, I *should* be able to get the device in the state of 'just-powered-on' and halted begin debugging?
<marex>
depends on the SoC
<hanetzer>
yerp.
<marex>
some SoCs keep JTAG off in the early stages for security reasons
<marex>
(so you cannot debug bootrom)
<hanetzer>
heh. I managed to dump this one's bootrom
<hanetzer>
took a lot more doing than the prior ones
<hanetzer>
haven't gotten around to completely tearing it apart but it seems the brom can pull files from a fat partition, so some parsing/etc in there.
prabhakarlad has quit [Quit: Client closed]
alpernebbi has quit [Quit: alpernebbi]
alpernebbi has joined #u-boot
camus has quit [Quit: camus]
alpernebbi has quit [Quit: alpernebbi]
camus has joined #u-boot
prabhakarlad has joined #u-boot
hanetzer has quit [Quit: WeeChat 3.5]
persmule has quit [Remote host closed the connection]
redbrain has quit [Read error: Connection reset by peer]
stefanct has quit [Ping timeout: 255 seconds]
flyback has quit [Ping timeout: 252 seconds]
stefanct has joined #u-boot
redbrain has joined #u-boot
torez has quit [Quit: torez]
flyback has joined #u-boot
mmu_man has joined #u-boot
torez has joined #u-boot
Xeroine has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
Net147 has quit [Ping timeout: 244 seconds]
Net147_ has joined #u-boot
Xeroine has quit [Ping timeout: 268 seconds]
Net147_ has quit [Ping timeout: 248 seconds]
Net147 has joined #u-boot
Net147 has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
adip has joined #u-boot
<adip>
Hello, does anyone here have experience with u-boot on pineboo pro? I can't boot my linux on u-boot newer than 2020.10.
<adip>
2020.04 and 2020.10 work fine. On newer tags I can't start my system. I'm using default config for my device.
<hramrach>
it sort of works for me
<adip>
what version are you using?
<hramrach>
what exactly does 'can't start my system' mean?
<hramrach>
2022.07
<hramrach>
the previous one was better, though
<hramrach>
I need some patches on top for the current release
<adip>
kernel on this laptop doesn't to uart. I don't know what's going wrong. I just know that system never starts. no init system messages and no login in display and uart
<adip>
*kernel doesn't print to uart
<hramrach>
it does do uart for me but there is some hardware switch for enabling it
<adip>
I did. I have u-boot messages on uart. but no kernel messages
<cambrian_invader>
earlycon?
<hramrach>
or even console=
<adip>
I've tried some earlycon, but my arguments may have been wrong. I have console= argument
<hramrach>
do you have no uart messages also with the woking u-boot?
<adip>
(I'm using mostly vanilla kernel with kernel config extracted out of manjaro)
<cambrian_invader>
usually you can use earlycon without arguments
<hramrach>
console=tty console=ttyS2,1500000
<cambrian_invader>
and it looks like your console loglevel is too high to show boot output for whatever reason
<cambrian_invader>
maybe pass "debug"?
<cambrian_invader>
or ignore_loglevel
<hramrach>
or ignore_loglevel or what was the parameter
<hramrach>
I cannot boot because u-boot bodges i2c initialization and the pmic is on i2c on 2022.07 but it worked on 2022.04
<adip>
I think at some point printing to uart was disabled in kernel due to stability issues (shared audio chip) I can't find that webpage with commit info
Xeroine has joined #u-boot
<adip>
nvm. igore_loglevel worked
<adip>
debug + ignore_logleved didn't work and I system didn't boot
<cambrian_invader>
even with old u-boot?
<adip>
I mean, starting system with igore_loglevel works on 2020.10. (adding debug flag breaks it)
<cambrian_invader>
well, your load addresses are different
<cambrian_invader>
I'd check to make sure nothing is getting overwrittem
<cambrian_invader>
it might also be that your environment is not what U-Boot expects for whatever reason; try comparing the output of `env default -a; env print`
gsz has quit [Ping timeout: 268 seconds]
akaWolf has quit [Ping timeout: 248 seconds]
indy has quit [Ping timeout: 248 seconds]
indy has joined #u-boot
alpernebbi has joined #u-boot
akaWolf has joined #u-boot
<adip>
https://dpaste.com/3FTC5KGTE this is a diff between enviroment on 2020.10 (working) and 2021.01 (not working one)
<adip>
this is a diff between enviroment on 2020.10 (working and 2022.07 (not working one) https://dpaste.com/6E7Z36SJ5
<cambrian_invader>
can you try booting with the new environment?
<adip>
add enviroment variables to old u-boot
<adip>
?
<cambrian_invader>
either way
<cambrian_invader>
or try the new u-boot with its default env
<adip>
I've tried to remove loadaddr=0x800800 and fdtoverlay_addr_r=0x02000000 from env in 2022.07 and it didn't work
<adip>
rest of the variables look less important
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
apritzel__ has quit [Ping timeout: 256 seconds]
vagrantc has joined #u-boot
rvalue has quit [Remote host closed the connection]
rvalue has joined #u-boot
frieder has quit [Remote host closed the connection]
rvalue has quit [Remote host closed the connection]
<adip>
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
<adip>
*** Warning - bad CRC, using default environment
<adip>
Could this be the source of my problems?
<adip>
older u-boot doesn't seem to read SPI flash
rvalue has joined #u-boot
<adip>
I did not write anything to SPI. it must have data from factory
<cambrian_invader>
does your newer U-Boot work with a default environment?
<adip>
no
Wouter0100 has quit [Ping timeout: 264 seconds]
Wouter0100 has joined #u-boot
<adip>
hramrach: could I borrow your compiled u-boot for pinebook pro?
<adip>
I've zeroed the SPI flash. Disabled eMMC and use only sd card for booting (rootfs is on nvme). I don't know what else could be wrong
srk has quit [Ping timeout: 240 seconds]
srk has joined #u-boot
thopiekar has quit [Ping timeout: 268 seconds]
thopiekar has joined #u-boot
persmule has quit [Ping timeout: 268 seconds]
prabhakarlad has quit [Quit: Client closed]
persmule has joined #u-boot
gsz has joined #u-boot
<hramrach>
adip: I have only broken u-boot binaries at hand because I am trying to debug the i2c problem