warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
urja has quit [Read error: Connection reset by peer]
slobodan_ has quit [Read error: Connection reset by peer]
slobodan_ has joined #u-boot
urja has joined #u-boot
warpme has joined #u-boot
Dr_Who has joined #u-boot
slobodan_ has quit [Ping timeout: 265 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
naoki has quit [Quit: naoki]
mrnuke has quit [Ping timeout: 265 seconds]
warpme has joined #u-boot
frytaped has quit [Quit: WeeChat 4.4.2]
frytaped has joined #u-boot
mrnuke has joined #u-boot
ungeskriptet has quit [Ping timeout: 244 seconds]
ungeskriptet has joined #u-boot
goliath has joined #u-boot
mrnuke has quit [Ping timeout: 252 seconds]
<Tartarus>
Hmmm, has anyone configured and run test/py/tests/test_spi.py on their platform?
mrnuke has joined #u-boot
<marex>
Tartarus: not me, I generally catch errors during regular day to day operation
<Tartarus>
Kinda thought so. And I'm trying to figure out if the test is wrong/weird, or this TI K3 platform is still buggy, even with the fix still applied
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marex>
Tartarus: test it with 2024.10 and see what happens ?
<marex>
Tartarus: what's the problem ?
<marex>
back in 20
ikarso has joined #u-boot
<Tartarus>
I'm in platform hell on this, yeah
<Tartarus>
2024.10 doesn't work
<Tartarus>
=> sf erase 0 0x4000000
<Tartarus>
jedec_spi_nor flash@0: flash operation timed out
<Tartarus>
Which is funny enough to debug that I'd love to know the test does work for someone on something else
warpme has joined #u-boot
warpme has quit [Client Quit]
warpme has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #u-boot
<rfs613>
Tartarus: i copy'n'pasted the crc/sf commands from your paste and ran them on my board... had to adjust the last 5 because I only have 16MB of flash... but the final CRC matched expected value.
<marex>
Tartarus: check SPI_FLASH_BAR enablement and 4K pages enablement
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Tartarus>
marex: Yeah, I'm not sure what they should be, I'll poke the TI folks in the new year most likely
<marex>
Tartarus: also check the SPI bus frequency
<marex>
Tartarus: erase timeout might be the flash doing long page/chip erase and it simply timing out
<marex>
Tartarus: did you try to bisect it back to something even older ?
<marex>
Tartarus: try and enable the 4K pages support in config , that might do the trick, it will increase the operation granularity and thus possibly prevent the timeout, as the erase will happen on smaller units
<marex>
Tartarus: although, the spi nor framework is likely optimizing the larger erase units into use of larger erase operations
<marex>
hum
<Tartarus>
marex: Yeah, I dunno *when* this actually worked upstream
<Tartarus>
That's the biggest problem.
<marex>
Tartarus: try a few versions going back, e.g. 2023.01 , 2022.01 ... ?
<Tartarus>
v2024.04 is maybe when SPI support was introduced and working
<marex>
Tartarus: 'git bisect run' is awesome for automated bisect
<Tartarus>
Oh yes
<Tartarus>
But sadly the spi test was introduced in -next this go-round :)
<Tartarus>
I'm gonna clear out other backlog of patch stuff for now, and perhaps see if a manual read/write/read cycle works