<marex>
cambrian_invader: hey, I recall you worked with ZynqMP ?
<Forty-Bot>
marex: yea
vagrantc has quit [Quit: leaving]
patersonc has quit [Ping timeout: 252 seconds]
Tartarus has quit [Read error: Connection reset by peer]
khilman has quit [Read error: Connection reset by peer]
Tartarus has joined #u-boot
LetoThe2nd has quit [Ping timeout: 252 seconds]
khilman has joined #u-boot
broonie has quit [Ping timeout: 252 seconds]
goliath has quit [Quit: SIGSEGV]
ellyq has quit [Ping timeout: 244 seconds]
LetoThe2nd has joined #u-boot
patersonc has joined #u-boot
ellyq has joined #u-boot
ellyq has quit [Client Quit]
broonie has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
<marex>
NishanthMenon: hey, do you happen to have any more detailed bit mappsings for AM654 DDRSS_DDRPHY_GPR0 and DDRSS_DDRPHY_GPR1 registers ?
jclsn has quit [Ping timeout: 246 seconds]
jclsn has joined #u-boot
mmu_man has quit [Ping timeout: 244 seconds]
Jones42_ has joined #u-boot
Jones42 has quit [Ping timeout: 272 seconds]
mmu_man has joined #u-boot
Jones42 has joined #u-boot
sally_ has joined #u-boot
sally_ is now known as sally
Jones42_ has quit [Ping timeout: 248 seconds]
mmu_man has quit [Ping timeout: 272 seconds]
Clamor has joined #u-boot
gsz has joined #u-boot
rockosov has quit [Ping timeout: 246 seconds]
rockosov has joined #u-boot
cambrian_invader has quit [Ping timeout: 252 seconds]
cambrian_invader has joined #u-boot
warpme has joined #u-boot
goliath has joined #u-boot
monstr has joined #u-boot
ldevulder has joined #u-boot
warpme has quit [Ping timeout: 246 seconds]
warpme has joined #u-boot
mckoan|away is now known as mckoan
Clamor has quit [Read error: Connection reset by peer]
Clamor has joined #u-boot
Jones42_ has joined #u-boot
Jones42 has quit [Ping timeout: 246 seconds]
ikarso has joined #u-boot
Jones42__ has joined #u-boot
Jones42_ has quit [Read error: Connection reset by peer]
mripard has joined #u-boot
Guest9 has joined #u-boot
<Guest9>
Hello together, what fields or addresses should be same if I compare old and new u-boot elf files. I am struggling with booting through new u-boot I have ported
<quinq>
What are “old” and “new” elf files in this context?
<Guest9>
quinq i mean disassembly
<Guest9>
quinq objdump -d -marm u-boot for older version of u boot and the same for latest what I have created and if I compare this disassembly what fields and addresses should be same to u-boot work
<Guest9>
quinq for example <__image_copy_start>: is same in old and new
mmu_man has joined #u-boot
Clamor has quit [Ping timeout: 246 seconds]
gdfsf has joined #u-boot
Guest9 has quit [Quit: Client closed]
Guest9 has joined #u-boot
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #u-boot
mmu_man has quit [Ping timeout: 255 seconds]
<marex>
Guest9: what are you trying to achieve in the end ?
<Guest9>
marex I want to figure out if there are some addresses which differs from old uboot making it unfunctional. I can see a difference of 2 mA on multimeter if I copies new uboot onto my board. However it doesn't jump to uboot or show me anything on serial port as I see if I do the same with older uboot.
<marex>
Guest9: do you have a JTAG debugger ? if so, use it to figure out where the new U-Boot is stuck
<marex>
Guest9: if not, look at CONFIG_DEBUG_UART and co
<marex>
Guest9: also, which hardware is this , which board, which U-Boot version ?
<Guest9>
marex I have JTAG also attached to it. CONFIG_DEBUG didn't give me anything. NXP 2024.04
<NishanthMenon>
marex: checking.. 3rd party IP, so might take a bit of time - anychance of using e2e.ti.com if this is a customer query? else if it is u-boot review of some sort.. i can get our guys to review as well.. if you can share the patch link..
<marex>
NishanthMenon: yes, I know it is Synopsys register
<marex>
Guest9: OK, if it is a massively modified downstream fork, please ask NXP for support
<marex>
Guest9: on imx that fork is unnecessary, use mainline as-is
<NishanthMenon>
marex: will help if i get a context of the query..
mmu_man has joined #u-boot
Jones42__ is now known as Jones42
naoki has quit [Quit: naoki]
<Guest9>
marex thank you so much for your suggestion. I didn't apply CONFIG_DEBUG correctly however now it gives me, could you have a look and suggest me what to do now
enok has quit [Read error: Connection reset by peer]
enok has joined #u-boot
enok has quit [Client Quit]
<welder>
Hi, I'm building U-Boot for rock5b. Everything boots well, except that the nvme drive is not seen early, when the boot commands from boot.scr located on SDcard are executed. Only when U-Boot goes through checking USBs, PXE etc and finally drops to the shell, nvme is visible. How can I make it be seen earlier?
warpme has joined #u-boot
jfsimon1981 has quit [Ping timeout: 276 seconds]
warpme has quit [Ping timeout: 252 seconds]
ikarso has joined #u-boot
warpme has joined #u-boot
warpme has quit [Ping timeout: 272 seconds]
warpme has joined #u-boot
warpme has quit [Ping timeout: 246 seconds]
mmu_man has joined #u-boot
warpme has joined #u-boot
<Kwiboo>
welder: you could add "pci enum" to your boot.scr, enable CONFIG_PCI_INIT_R to force init pci early, drop your boot.scr from sd-card and use boot.scr, extlinux.conf or EFI boot from your nvme drive, or change boot_targets to try and boot from nvme before mmc1, it depends on what you want to do
warpme has quit [Ping timeout: 248 seconds]
<welder>
that's exactly what i did - I mvoed boot.scr from sd card to nvme :)
<welder>
I will check the "pci enum" too, thanks
naoki has quit [Quit: naoki]
warpme has joined #u-boot
<welder>
If I don't have extlinux nor boot.src, will U-Boot by default search for and start EFI/boot/bootaa64.efi?
warpme has quit [Ping timeout: 246 seconds]
warpme has joined #u-boot
vfazio_ has quit [Remote host closed the connection]