17:29 <dujem> im trying to move coreprimevelte to OF_UPSTREAM, right now serial output is getting stuck at "DRAM:". this could imply that fdtdec_setup_mem_size_base() is failing but dram_init() should print an error if that happens, but it isnt. any ideas?

18:12 <marex> dujem: run dtc -I dtb -O dts -s u-boot.dtb > /tmp/old.dts before the switch , the same thing > /tmp/new.dts after the switch, diff the two /tmp/{old,new}.dts and search for differences , look at UART, possibly bootph tags

18:12 <marex> apply the same for SPL DT

18:12 <marex> that should let you find the issue quickly

18:12 <marex> OF_UPSTREAM affects your board control DT, so the difference has to be there

18:49 <dujem> marex: figured it out. looks like samsung bootloader will happily fill in /memory but not /memory@0

19:32 <shadows> marex: any other tricks to try for the suspicious USB storage device in U-Boot?

20:23 <marex> dujem: do you have DRAM located at 0 ?

20:23 <marex> shadows: aside from dig in and start debugging it properly, not really

20:31 <dujem> marex: according to samsung bootloader the DRAM range is 1000000-40000000

20:38 <marex> dujem: then why would your memory node be at 0 ?

20:38 <marex> btw 0..0x1000000 is probably some reserved range and the memory is at 0, but check SoC datasheet to be sure

20:49 <dujem> marex: because the memory node in the linux dts is empty and left to be filled in by bootloader

20:50 <dujem> trying to read 0 results in a synchronous abort so that is indeed unusable, though idk what it is as there is no datasheet

22:19 <marex> dujem: run 'bdinfo' , that will give you an idea what is U-Boot memory layout view

22:19 <marex> dujem: is that current mainline U-Boot or some downstream fork ?