<robher>
marex: don't mind the prompt to enter your CC number.
mmu_man has quit [Ping timeout: 245 seconds]
sdfgsdfg has joined #u-boot
vagrantc has quit [Quit: leaving]
<Forty-Bot>
patman could use a bit of the same treatment
<Forty-Bot>
sometimes I am working with an old U-Boot checked out and want to use a new feature
samekh has quit [Ping timeout: 252 seconds]
samekh has joined #u-boot
<marex>
robher: heh
Lokis has joined #u-boot
Lokis has quit [Ping timeout: 245 seconds]
LeSpocky has quit [Ping timeout: 256 seconds]
LeSpocky has joined #u-boot
Lokis has joined #u-boot
Lokis has quit [Ping timeout: 245 seconds]
Lokis has joined #u-boot
milkylainen_ has joined #u-boot
Antilokis has joined #u-boot
EdSwarthout has quit [Ping timeout: 265 seconds]
Lokis has quit [Ping timeout: 245 seconds]
sdfgsdfg has quit [Quit: ZzzZ]
EdSwarthout has joined #u-boot
<Antilokis>
Hello, when I execute my bootcmd manually from u-boot console kernel loads and starts ok, however when I the autoboot execute the same command it gives me “prefetch abort”. Any idea what could be wrong here? (https://paste-bin.xyz/19816)
fdanis_away is now known as fdanis
EdSwarthout has quit [Ping timeout: 256 seconds]
pbergin has joined #u-boot
EdSwarthout has joined #u-boot
mckoan|away is now known as mckoan
milkylainen has joined #u-boot
flyback has quit [Ping timeout: 245 seconds]
flyback has joined #u-boot
guillaume_g has joined #u-boot
sszy has joined #u-boot
tre has joined #u-boot
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
matthias_bgg has joined #u-boot
mmu_man has joined #u-boot
guillaume_g has quit [Ping timeout: 252 seconds]
guillaume_g has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
<wyre>
the point is that ... I'm not sure if when I build an image for this MACHINE ... u-boot is included in the .wic image
wenwuZhang has joined #u-boot
<wyre>
which I'm using to flash my sdcard
<wyre>
according to the hw manual of my testing carrier board https://github.com/engicam-stable/u-boot-engicam-nxp when I close the jumper JM2 ... I'm booting from the SD card, and I'm not sure if this means that u-boot it's also loaded from the SD card
<wyre>
or I'm always loading the u-boot flashed in NAND but the environment for u-boot is fetched from the SD card
<wyre>
I've noticed the environment changes depending on if I close the jumper or not
<wyre>
but I'm not sure if is just the env or the whole u-boot
wenwuZhang has quit [Ping timeout: 256 seconds]
pbergin has quit [Quit: Leaving]
pgreco has quit [Ping timeout: 252 seconds]
pgreco has joined #u-boot
wenwuZhang has joined #u-boot
wenwuZhang has quit [Ping timeout: 256 seconds]
mmu_man has quit [Ping timeout: 245 seconds]
frieder has joined #u-boot
wenwuZhang has joined #u-boot
wenwuZhang has quit [Remote host closed the connection]
guillaume has quit [Quit: Konversation terminated!]
Lokis has joined #u-boot
frieder has quit [Remote host closed the connection]
sstiller has quit [Remote host closed the connection]
Antilokis has quit [Ping timeout: 245 seconds]
guillaume has joined #u-boot
guillaume is now known as guillaume_g
<LeSpocky>
hello
camus has quit [Quit: camus]
v0|d has quit [Remote host closed the connection]
Antilokis has joined #u-boot
Lokis has quit [Ping timeout: 256 seconds]
<milkylainen>
LeSpocky: \o/
<milkylainen>
dt memory node breakage? :)
<LeSpocky>
milkylainen: just playing with u-boot 'fdt' command
<milkylainen>
mkay.
<LeSpocky>
so far I loaded the dtb from ubifs to memory
<LeSpocky>
then `fdt addr ${fdt_addr_r}` and `fdt memory 0x20000000 0x6000000` (on a board with more than 0x6000000) and then `bootz ${kernel_addr_r} - ${fdt_addr_r}`
<LeSpocky>
however kernel still reported full memory size 0x08000000 / 131072K
<LeSpocky>
according to `fdt print /memory` the node was changed
<LeSpocky>
and bootz reports to use fdt from the address I loaded it to
<LeSpocky>
how is that supposed to work?
<milkylainen>
kernel only relies on dt? no atags, cmdline or other funny business?
<LeSpocky>
don't know O:-)
<milkylainen>
old board definitions?
<LeSpocky>
I should dig into that atags direction probably
<milkylainen>
And you haven't compiled kernel with builtin dt? (ARM?)
<LeSpocky>
yes arm, no dt built into the kernel, u-boot loads it
<LeSpocky>
bootz
<milkylainen>
And linux actually sees a changed dt memory node?
<LeSpocky>
not sure yet, I'm trying to find out how to prove that
<LeSpocky>
`cat /proc/device-tree/memory/reg` is empty :-/
<milkylainen>
I dunno if the firmware devicetree node is in /sys for you to use dtc on?
<milkylainen>
But it sounds to me like either the memory node is wrong or something hasn't cared for it.
<LeSpocky>
from code reading I would guess U-Boot does fixup of memory node already … that means it could be sufficient to set the correct memory size in dram_init() and I'm done … will try that next week
matthias_bgg has quit [Quit: Leaving]
Lokis has joined #u-boot
Antilokis has joined #u-boot
Lokis has quit [Ping timeout: 256 seconds]
guillaume_g has quit [Quit: Konversation terminated!]