<Xogium>
well… after more investigation, I have no clue why u-boot seems to hang on vfat related code, at least according to openocd and gdb. I removed ext4 fs thinking it was the problem, but nop. It just found someplace else to hang
<Xogium>
I still have no idea why u-boot doesn't talk over serial on stm32f769 discovery kit
<Xogium>
I'd really appreciate any help
<Xogium>
this is default config, default dts, haven't touched a thing, from u-boot 2021.01
<Xogium>
if someone has ideas of things I can try, feel free… I'm just confused at this point
<Xogium>
I've tripple checked usart1 is the correct serial console and it is, st-link chip is connected to this, and that's exactly what I'm trying to use with screen, at 115200n8 baud
<Xogium>
ftr, the only thing I was able to get out of gdb is this
<Xogium>
0x0802781a in ext4_read_file (filename=0x2004ffe0 "_\256O\376", buf=0x16, offset=<optimized out>, len=0, len_read=0x0) at fs/ext4/ext4fs.c:259
monstr has quit [Remote host closed the connection]
fdanis is now known as fdanis_away
as2334 has joined #u-boot
<as2334>
I completely erased the nand flash of my rk3126 device but rkdeveloptool still lists it as "loader" - does that make sense?
<cambrian_invader>
is it possible to cancel an azure run started from github?
Xogium has left #u-boot [leaving channel]
<cambrian_invader>
(if you force push you cancel the job and it restarts on the new head)
___nick___ has joined #u-boot
<rfried>
sjg1: Hey. there's a patch pending in network which switches the initializaton of the ethernet phy from start() to probe().
<rfried>
It does it to hurry up the link up negociation. I'm wondering if it's anti-pattern to do that in probe(), it means that the link will be brought up without user request.
guillaume_g has quit [Quit: Konversation terminated!]
v0|d has joined #u-boot
milkylainen has quit [Quit: Connection closed]
macromorgan has joined #u-boot
matthias_bgg has quit [Quit: Leaving]
<sjg1>
rfried: Yes we can poke the hardware in probe() but should do do anything that takes too long. Best to be a separate method. It breaks the lazy-init feature of U-Boot