NishanthMenon changed the topic of #linux-ti to: Linux development for TI SoCs | Logs: https://libera.irclog.whitequark.org/linux-ti/| paste logs in https://pastebin.ubuntu.com/ | Let it rock! Vendor SDK/kernel: Also see e2e.ti.com
florian_kc has quit [Ping timeout: 240 seconds]
Pali has quit [Ping timeout: 240 seconds]
tmlind has quit [Remote host closed the connection]
kishon has joined #linux-ti
kishon has quit [Ping timeout: 240 seconds]
rogerq has joined #linux-ti
kishon has joined #linux-ti
tmlind has joined #linux-ti
<vigneshr> austriancoder: I will take a look at ethernet issue today... u-boot may not be cleaning up DMA resources properly, leading to issues in kernel
<austriancoder> vigneshr: great. Yeah at a quick look something like this could be the issue. btw. I am using upstream U-Boot 2022.01
rob_w has joined #linux-ti
lucaceresoli has joined #linux-ti
ikarso has joined #linux-ti
Pali has joined #linux-ti
florian has joined #linux-ti
lucaceresoli_ has joined #linux-ti
florian_kc has joined #linux-ti
lucaceresoli has quit [Ping timeout: 256 seconds]
<vigneshr> austriancoder: Tried v2022.01 + next-20220125 Cannot seem to reproduce... Could you share full logs? Would like to see bootargs being used
<vigneshr> BTW are you using AM64x GP EVM or SK or custom HW?
<austriancoder> vigneshr: next-20220125 not in use here... but I think I can update to that.
<austriancoder> vigneshr: sure.. I can send you a full boot log
<austriancoder> vigneshr: custom HW
lucaceresoli_ has quit [Ping timeout: 256 seconds]
<vigneshr> Seems like fastboot eth case, eth device is not explicitly halted and would have to be done as part of driver remove sequence.
<vigneshr> FYI austriancoder confirmed below diff fixes the issue . I will post the same upstream.
lucaceresoli_ has joined #linux-ti
<NishanthMenon> thanks vigneshr austriancoder
rob_w has quit [Remote host closed the connection]
<austriancoder> I think U-Boot commit 03f1f78a9b44b5fd6fc09faf81639879d2d0f85f broke sysfw loading from emmc.
<austriancoder> spl_mmc_load
<austriancoder> k3_sysfw_loader
<austriancoder> mmc_load_image_raw_sector
<austriancoder> spl_load_simple_fit
<austriancoder> spl_simple_fit_read
<austriancoder> spl_simple_fit_read(..) uses the __weak board_spl_fit_buffer_addr(..) which allocates its own buffer and ignores spl_get_load_buffer() from sysfw-loader.c
florian has quit [Quit: Ex-Chat]
florian_kc has quit [Ping timeout: 250 seconds]
<vigneshr> austriancoder: Aren't you on AM64 and latest u-boot? I expect k3_sysfw_loader() to exit within if (rom_loaded_sysfw) {} block
rogerq has quit [Remote host closed the connection]
<austriancoder> vigneshr: I have seen that in ti's U-Boot that the ROM loads both. But here the r5 loads sysfw.
<vigneshr> austriancoder: that's not intention, AM64 is intended to use combined R5 SPL + SYSFW . how do you build tiboot3.bin ?
<vigneshr> Do you make use of k3-img-gen project?
<austriancoder> vigneshr: I used https://training.ti.com/process-linux-boot-flow-using-am64x-processors as reference. I am using k3-img-gen to build sysfw.itbvia SOC=am64x make
<austriancoder> tiboot3.bin comes from u-boot with an r5 defconfig
<austriancoder> ...
<austriancoder> -o tiboot3.bin -l 0x70000000 -k ""
<austriancoder> ./tools/k3_gen_x509_cert.sh -c 16 -b spl/u-boot-spl.bin \
<austriancoder> SYM spl/u-boot-spl.sym
<austriancoder> vigneshr: I am open for every improvement :)
lucaceresoli_ has quit [Ping timeout: 240 seconds]
florian_kc has joined #linux-ti
florian_kc has quit [Ping timeout: 240 seconds]
florian_kc has joined #linux-ti
rogerq has joined #linux-ti
rogerq has quit [Client Quit]
lucaceresoli_ has joined #linux-ti
florian_kc is now known as florian
lucaceresoli_ has quit [Ping timeout: 240 seconds]
HcE has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
rogerq has joined #linux-ti
rogerq has quit [Client Quit]
florian has quit [Ping timeout: 240 seconds]
florian has joined #linux-ti