Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2022.04, v2022.07-rc2 are OUT / Merge Window is CLOSED / Release v2022.07 is scheduled for 4 July 2022 / http://www.denx.de/wiki/U-Boot / Channel archives at https://libera.irclog.whitequark.org/u-boot
zar_ has quit [Quit: No Ping reply in 180 seconds.]
kallisti5 has quit [Ping timeout: 260 seconds]
mmu_man has quit [Ping timeout: 240 seconds]
thopiekar has quit [Ping timeout: 252 seconds]
thopiekar has joined #u-boot
thopiekar has quit [Ping timeout: 276 seconds]
NonaSuomy has joined #u-boot
kallisti5 has joined #u-boot
thopiekar has joined #u-boot
<NonaSuomy> How do these memory values translate? Right now I have U-Boot booting the normal kernel and ramdisk. If I wanted to load the recovery kernel instead how would I change the u-boot values for that? Also if I want to rip stuff out of these locations how do I form dd commands to do that? (Backup ENV settings etc) https://pastebin.com/raw/9T5rRRyk
mps has quit [Ping timeout: 276 seconds]
akaWolf has quit [Ping timeout: 240 seconds]
srk- has joined #u-boot
srk has quit [Ping timeout: 252 seconds]
srk- is now known as srk
srk- has joined #u-boot
srk has quit [Ping timeout: 276 seconds]
srk- is now known as srk
vagrantc has quit [Quit: leaving]
littlebobeep has quit [Ping timeout: 240 seconds]
littlebobeep has joined #u-boot
mps has joined #u-boot
NonaSuomy has quit [Ping timeout: 276 seconds]
littlebobeep has quit [Ping timeout: 240 seconds]
mckoan|away is now known as mckoan
frieder has joined #u-boot
littlebobeep has joined #u-boot
sszy has joined #u-boot
frieder has quit [Ping timeout: 248 seconds]
guillaume_g has joined #u-boot
ldevulder has joined #u-boot
frieder has joined #u-boot
ilunev has joined #u-boot
Epakai_ has joined #u-boot
Epakai has quit [Ping timeout: 260 seconds]
onio has joined #u-boot
monstr has joined #u-boot
ladis has joined #u-boot
apritzel has joined #u-boot
___nick___ has joined #u-boot
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 276 seconds]
ldevulder has quit [Quit: Leaving]
crb has quit [Ping timeout: 272 seconds]
crb has joined #u-boot
mmu_man has joined #u-boot
torez has joined #u-boot
behanw has joined #u-boot
ldevulder has joined #u-boot
broonie has joined #u-boot
<broonie> khilman: Is there any CI for amlogic u-boot I can look at? I'm trying to get to the bottom of some issues with some le potato boards.
ilunev has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
thopiekar has quit [Quit: Likely restarting quassel...]
thopiekar has joined #u-boot
___nick___ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
___nick___ has joined #u-boot
ladis has quit [Quit: Leaving]
<khilman> I think Neil had some setup awhile ago, but not sure if it's still running.
<khilman> narmstrong: ^^^ ?
<narmstrong> Nop no setup but we plan to set up one
GNUtoo has quit [Ping timeout: 240 seconds]
<narmstrong> We only build and package weekly
littlebobeep has quit [Ping timeout: 240 seconds]
<khilman> broonie: What issues are you having? I know we had some issues on several amlogic boards recently where we had to update the u-boot load addrs used since the kernel image size was getting so big.
<broonie> khilman: Taking a synchronous abort (level 0 translation fault IIRC) trying to boot kernels other than the test job kernel. I'm already using the new addresses from montjoie - they're working fine with an older u-boot image/firmware I built ~a month ago.
<narmstrong> broonie: it reminds I made a revert of https://source.denx.de/u-boot/u-boot/-/commit/f33a2c1bd0fb371511a485cac1f182ba50db51be because it caused "Synchronous Abort" handler, esr 0x96000210 while loading ramdisk
NonaSuomy has joined #u-boot
GNUtoo has joined #u-boot
littlebobeep has joined #u-boot
mckoan is now known as mckoan|away
<broonie> narmstrong: That smells very similar - I was seeing an EC of 0x96000004-but I do have the revert already in my tree so something different.
<broonie> Somewhere after "Loading Device Tree to..." in my case, but before Starting kernel...
<narmstrong> broonie: can you give me the load address, kernel image format and boot steps so I can try to reproduce ?
<narmstrong> broonie: thx
mmu_man has quit [Ping timeout: 272 seconds]
* broonie tried both vendor and upstream TF-A for BL31 - didn't seem to be making any difference.
vagrantc has joined #u-boot
<mps> would be nice to be fixed in next stable release
mmu_man has joined #u-boot
<NonaSuomy> How would you go about injecting a newly oversized uImage into the existing boot image? If the stock uImage was 2.2MB and now your compile is 4MB etc?
sjg1_ has joined #u-boot
ccaione_ has joined #u-boot
adeepv_ has joined #u-boot
paulbarker_ has joined #u-boot
mithro_ has joined #u-boot
pratyush_ has joined #u-boot
southey2 has joined #u-boot
pavelow_ has joined #u-boot
mlaga97_ has joined #u-boot
mkst1r has joined #u-boot
eloy_ has joined #u-boot
elafon_ has joined #u-boot
doppo_ has joined #u-boot
cyrozap-ZNC has joined #u-boot
adeepv has quit [*.net *.split]
mlaga97 has quit [*.net *.split]
lovesegfault[m] has quit [*.net *.split]
Tartarus has quit [*.net *.split]
mvaittin has quit [*.net *.split]
cpackham[m] has quit [*.net *.split]
JBB[m] has quit [*.net *.split]
pratyush has quit [*.net *.split]
doppo has quit [*.net *.split]
elafon has quit [*.net *.split]
mkstr has quit [*.net *.split]
sjg1 has quit [*.net *.split]
ccaione has quit [*.net *.split]
mithro has quit [*.net *.split]
eloy has quit [*.net *.split]
pavelow has quit [*.net *.split]
cyrozap has quit [*.net *.split]
paulbarker has quit [*.net *.split]
foxtrot has quit [*.net *.split]
pratyush_ is now known as pratyush
southey2 is now known as foxtrot
sjg1_ is now known as sjg1
ccaione_ is now known as ccaione
paulbarker_ is now known as paulbarker
mithro_ is now known as mithro
<marex> NonaSuomy: in Linux ... make uImage
JBB[m] has joined #u-boot
mvaittin has joined #u-boot
cpackham[m] has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
lovesegfault[m] has joined #u-boot
Tartarus has joined #u-boot
macromorgan has joined #u-boot
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 256 seconds]
mmu_man has joined #u-boot
apritzel has quit [Ping timeout: 260 seconds]
sszy has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
mlaga97_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
mlaga97 has joined #u-boot
<NonaSuomy> marex right now I'm doing this to inject the uImage into the current sdcard sudo dd if=~/code/linux-2.6.35.2/arch/arm/boot/uImage of=/dev/mmcblk0 bs=512 seek=2048
<NonaSuomy> if my uImage is over the original size (2.2MB) it tosses up an error.
<NonaSuomy> If it's smaller than 2.2MB then it's fine
<marex> why are you writing kernel image to such offset ?
<NonaSuomy> I was wondering if there was a safer way of injecting a uImage into a running build that could be any size
<marex> use filesystem
<NonaSuomy> ?
<marex> copy file to filesystem and then load it in U-Boot and bootm it
<NonaSuomy> That won't work becuase the existing system has an external watchdog and when I try to load anything basic it gets triggered after 30 seconds
<marex> loading file from filesystem shouldn't take so long
<NonaSuomy> It's not about it's loading time. It's about that nothing will stop the external watchdog from triggering if its not loading the rest of devices files after that.
<marex> you should be able to ping the wdt manually if nothing else ...
<marex> just mw <wdt register>
<marex> just mw <wdt register> <value>
<NonaSuomy> Yeah the version of uboot on the device doesn't have the multi i2c config enabled. So I can't switch to dev 0 to send any watchdog commands.
<marex> oh, right, that
<marex> load the kernel and start it quickly then ?
<marex> that should be doable below 30 seconds
<marex> (well, in the worst case, you can always use mw to poke the i2c IP to do the i2c access)
<NonaSuomy> ?
apritzel has joined #u-boot
sobkas has joined #u-boot
<marex> NonaSuomy: mw -- memory write
<marex> it's effectively command line wrapper around writel() function
<marex> so you could use series of 'mw' commands to send the I2C transfer and ping the WDT
<marex> or you can even bitbang the I2C using GPIO block, by poking its DR register
<NonaSuomy> Ideally I would have to have some sort of visual of what those values are already to know what I'm poking at.
<NonaSuomy> for example I would need to do these commands
<NonaSuomy> Doc:
<NonaSuomy> WM8321G Address R16388(4004h) Watchdog, Bit 14 WDOG_DEBUG, Default 0, Watchdog Pause 0=Disable 1=Enabled (halts the watchdog timer for system debugging) Protected by user key
<NonaSuomy> This would show if you can't modify the watchdog bit without the code
<NonaSuomy> i2c dev 0
<NonaSuomy> i2c probe
<NonaSuomy> i2c md.w 0x34 0x4008 -> default value is 0x0000
<NonaSuomy> We have to write a magic value 0x9716 to this register, to allow writes to WDOG_DEBUG etc.
<NonaSuomy> MX50_ARM2 U-Boot > i2c mm.w 0x34 0x4008 0x9716
<NonaSuomy> Print out the bit set for 4004
<NonaSuomy> MX50_ARM2 U-Boot > i2c md.w 0x34 0x4004
<NonaSuomy> Then you should be abled to activate the watchdog debug mode
<NonaSuomy> MX50_ARM2 U-Boot > i2c mm.w 0x34 0x4004 (change bit 14 of whatever you get from above to 1)
<NonaSuomy> What would that look like with what you speak of?
<marex> I would probably figure out which SoC pins is SDA and SCL and then just flip them ... SDA+SCL high, set SDA, SCL low, SCL high, set SDA, SCL low, SCL high ... and so on
monstr has quit [Remote host closed the connection]
<NonaSuomy> right...
<NonaSuomy> You should have just said a robot walks into a bar and says 01101111 01110101 01100011 01101000
foxtrot has quit [Remote host closed the connection]
southey2 has joined #u-boot
southey2 is now known as foxtrot
michalkotyla has quit [Remote host closed the connection]
michalkotyla has joined #u-boot
ldevulder has quit [Quit: Leaving]
sobkas has quit [Quit: sobkas]
___nick___ has quit [Ping timeout: 272 seconds]
<marex> NonaSuomy: the joke is rather fitting, except in your case, see https://www.ti.com/lit/an/slva704/slva704.pdf Figure 6 and chapter 3.1
<marex> (write is easier)
<marex> in the MX50 RM, you want to look at "GPIO" block and "DR" register in there
<marex> and possibly IOMUXC , make sure the SDA/SCL GPIOs are set to AF GPIO
<marex> they might be AF I2C
<hanetzer> re: the DM driver model. the probe function gets called when you request a particular driver yeh?
NonaSuomy has quit [Ping timeout: 240 seconds]
<marex> hanetzer: thats part of it
<marex> also if you request a service from a driver which is not probe()d yet
redbrain has quit [Read error: Connection reset by peer]
redbrain has joined #u-boot
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
matthias_bgg has quit [Ping timeout: 248 seconds]
stefanro has quit [Ping timeout: 248 seconds]
vagrantc has quit [Quit: leaving]
onio has quit [Ping timeout: 260 seconds]
apritzel has quit [Ping timeout: 272 seconds]
stefanro has joined #u-boot