persmule has quit [Remote host closed the connection]
schroes has quit [Ping timeout: 240 seconds]
schroes has joined #u-boot
vagrantc has joined #u-boot
vagrantc has quit [Quit: leaving]
gsz has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
enok has joined #u-boot
rvalue has quit [Ping timeout: 255 seconds]
rvalue has joined #u-boot
schroes has quit [Ping timeout: 268 seconds]
f_ has joined #u-boot
schroes has joined #u-boot
redbrain has quit [Read error: Connection reset by peer]
enok has quit [Ping timeout: 240 seconds]
redbrain has joined #u-boot
slobodan has joined #u-boot
FergusL has quit [Changing host]
FergusL has joined #u-boot
jfsimon1981_b has quit [Remote host closed the connection]
jfsimon1981_b has joined #u-boot
jfsimon1981_b has quit [Remote host closed the connection]
jfsimon1981_b has joined #u-boot
jfsimon1981_b has quit [Remote host closed the connection]
jfsimon1981_c has joined #u-boot
dsimic has quit [Ping timeout: 268 seconds]
dsimic has joined #u-boot
stefanro has quit [Quit: Leaving.]
Forty-Bot has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
enok has joined #u-boot
persmule has joined #u-boot
enok has quit [Ping timeout: 256 seconds]
qqq has joined #u-boot
___nick___ has joined #u-boot
enok has joined #u-boot
joeskb7 has joined #u-boot
ikarso has joined #u-boot
Net147 has quit [Ping timeout: 252 seconds]
f_ has quit [Ping timeout: 260 seconds]
gsz has quit [Ping timeout: 272 seconds]
sakman_ is now known as sakman
mmu_man has quit [Ping timeout: 256 seconds]
Net147 has joined #u-boot
Net147 has quit [Changing host]
Net147 has joined #u-boot
mmu_man has joined #u-boot
rvalue has quit [Ping timeout: 268 seconds]
alan_o has quit [Remote host closed the connection]
alan_o has joined #u-boot
enok has quit [Ping timeout: 252 seconds]
yann-kaelig has joined #u-boot
<yann-kaelig>
Hello
<yann-kaelig>
Still with my issue but the noose is tightening. I found a combo that I can repoduce and fix the issue, this time I do not need to poweroff the board, but still I have to unplug and replug the SSD to get it work.
<yann-kaelig>
That pretty a good news because now I will be able to retrieve some info
schroes has quit [Ping timeout: 272 seconds]
<yann-kaelig>
The problem now is that I don't know how to efficiently recover what happens during this combo of actions.
<yann-kaelig>
how can I trace everything happening at u-boot command prompt
rvalue has joined #u-boot
schroes has joined #u-boot
joeskb7 has quit [Quit: Lost terminal]
ikarso has quit [Quit: Connection closed for inactivity]
<yann-kaelig>
Ok. so this is how it work. Power ON the board > Get U-boot command prompt > scsi reset ( timeout ) > unplug the SSD > reset > Get U-boot command prompt > plug the SSD > scsi reset ( it work )
<yann-kaelig>
Now how can I get trace of what is happening behind the hood
<marex>
yann-kaelig: add printfs into cmd/scsi.c and take it from there ?
persmule has quit [Ping timeout: 260 seconds]
<marex>
yann-kaelig: btw does it also work if you do cold-boot "unplug ssd, power on the board, plug the ssd, scsi reset" ?
<yann-kaelig>
No it doesn't work
<marex>
yann-kaelig: then start adding print("%s[%d]\n", __func__, _LINE__); s all over the place
persmule has joined #u-boot
<marex>
yann-kaelig: cmd/scsi.c and drivers/ata/*sunxi*c is probably a good start
<yann-kaelig>
The only way that works is the one I gave. If I try for example to scsi reset, unplug and plug then scsi reset again without a reset, it doesn't work ( time out )
jfsimon1981_c has quit [Remote host closed the connection]
jfsimon1981_c has joined #u-boot
<marex>
yann-kaelig: that means the reset has some significance
<yann-kaelig>
marex: I tried one time to add the printf(); as you recommended few days ago, but I was unable to build uboot. Could you please tell me where I should add this line that you give me now.
<marex>
yann-kaelig: what was the error ?
<yann-kaelig>
not only the reset but also reconnecting the SSD, the led turn on, blinks for a while and stays on.
<yann-kaelig>
don't remember but the build failed
<yann-kaelig>
certainly because I put the line in a wrong place
<marex>
yann-kaelig: drivers/scsi/scsi.c scsi_scan() is a good start
<marex>
come back when you have actual error message
<marex>
else this is guesswork, which is inefficient
<yann-kaelig>
I undestand, nut it llok like I'm alone with this hdd-raid ^^
<yann-kaelig>
but it looks like*
<yann-kaelig>
sorry, I have to ask again where should I put the line print("%s[%d]\n", __func__, _LINE__);
<yann-kaelig>
at which line
<yann-kaelig>
I learned turbo pascal at middle school 30 years ago. :D
<yann-kaelig>
Ha! remember that was on Thomson MO5 and TO7
<yann-kaelig>
And my first computer was a clone of the APPLE IIe, lol
<yann-kaelig>
Anyway don't want to bother you with that. You are helping a lot, thx
<marex>
yann-kaelig: you can put that print on every second line of that function to see what's going on
<marex>
printf is cheap
<yann-kaelig>
ok, I'll try to figure it out.
<yann-kaelig>
Thx. Enough for today, cu later, jave a good day/night
yann-kaelig has quit []
jfsimon1981_c has quit [Remote host closed the connection]
jfsimon1981_c has joined #u-boot
___nick___ has quit [Ping timeout: 260 seconds]
slobodan has quit [Ping timeout: 272 seconds]
jfsimon1981_c has quit [Read error: Connection reset by peer]
jfsimon1981_c has joined #u-boot
ikarso has joined #u-boot
ukky has quit [Quit: leaving]
ukky has joined #u-boot
enok has joined #u-boot
enok has quit [Quit: enok]
enok71 has joined #u-boot
enok71 is now known as enok
mmu_man has quit [Ping timeout: 268 seconds]
mmu_man has joined #u-boot
warthog9 has quit [Quit: Leaving]
warthog9 has joined #u-boot
enok has quit [Ping timeout: 268 seconds]
goliath has quit [Quit: SIGSEGV]
mmu_man has quit [Ping timeout: 256 seconds]
mmu_man has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]