jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #u-boot
mmu_man has joined #u-boot
enok has quit [Ping timeout: 255 seconds]
goliath has joined #u-boot
enok has joined #u-boot
Hypfer5 has joined #u-boot
Hypfer has quit [Ping timeout: 256 seconds]
Hypfer5 is now known as Hypfer
persmule has joined #u-boot
goliath has quit [Quit: SIGSEGV]
warpme has joined #u-boot
monstr has joined #u-boot
Stat_headcrabed has quit [Quit: Stat_headcrabed]
ungeskriptet3 has joined #u-boot
ungeskriptet has quit [Ping timeout: 256 seconds]
ungeskriptet3 is now known as ungeskriptet
enok has quit [Ping timeout: 256 seconds]
tgamblin has joined #u-boot
monstr has quit [Remote host closed the connection]
goliath has joined #u-boot
thopiekar has joined #u-boot
darkxst has quit [Ping timeout: 268 seconds]
thopiekar has quit [Ping timeout: 255 seconds]
Raito_Bezarius has joined #u-boot
Raito_Bezarius has quit [Read error: Connection reset by peer]
darkxst has joined #u-boot
Clamor has quit [Ping timeout: 268 seconds]
Clamor has joined #u-boot
thopiekar has joined #u-boot
slobodan has joined #u-boot
slobodan_ has quit [Ping timeout: 245 seconds]
yann-kaelig has joined #u-boot
<yann-kaelig>
Hello
KREYREN has joined #u-boot
sickos has joined #u-boot
sickos has quit [Client Quit]
<yann-kaelig>
I found how to repoduce the issue about my drive not detected on my cubietruck hdd-raid subboard during U-boot boot and I found how to fix the issue, but I can not understand why the issue occur. So, to fix the issue I have to boot the OS first from my sdcard, next I reboot to enter to U-boot command prompt. Only at this time I plug the SATA drive to my subboard and the SATA LED turn on. Next I can run scsi scan and it works the
<yann-kaelig>
device is found. Oddly, if I follow the same step during the first power ON of the board and plug the SATA drive, the LED is not turning ON and scsi scan timeout
<marex>
yann-kaelig: check what commands are fed into the controller when Linux boots, or check if there is maybe some regulator/GPIO/... toggled by Linux
goliath has quit [Quit: SIGSEGV]
<marex>
it could be that's the init you are missing, Linux does it, and then it works
<marex>
so replicate it in U-Boot and it should be fine
<yann-kaelig>
ok
f_ has quit [Quit: To contact me, send a memo using MemoServ, PM f_[xmpp], or send an email. See https://vitali64.duckdns.org/.]
<yann-kaelig>
ha!
<marex>
is that a good ha or a bad ha ?
<yann-kaelig>
I suppose for now it could be a good ha!, because the subboard indeed use a special connector
<yann-kaelig>
The CN8 connector
<yann-kaelig>
so you right, somethign is missing during the u-boot boot probably to detect/enable/init the connection through this connector
Clamor has quit [Read error: Connection reset by peer]
<marex>
yann-kaelig: maybe some GPIO ?
<marex>
yann-kaelig: try gpio status -a with failing/working setup
<marex>
there might be a GPIO that is flipped the other way
<yann-kaelig>
Yes, maybe but the mistery for me is how is it possible that this has an impact on U-boot after a reboot. This is not reset ?
<yann-kaelig>
how does it persist after a reboot
<yann-kaelig>
OK, thx. Short time today. CU later
yann-kaelig has quit []
enok has joined #u-boot
pivi has quit [Remote host closed the connection]
pivi has joined #u-boot
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
vagrantc has joined #u-boot
prabhakalad has quit [Ping timeout: 255 seconds]
prabhakalad has joined #u-boot
enok has quit [Ping timeout: 255 seconds]
enok has joined #u-boot
enok has quit [Quit: enok]
enok has joined #u-boot
slobodan has quit [Ping timeout: 240 seconds]
enok has quit [Ping timeout: 256 seconds]
ungeskriptet has quit [Read error: Connection reset by peer]