bootkernel1=ubi read $loadaddr part.safe; bootm $loadaddr#$itb_config
bootkernel2=ubi read $loadaddr part.old; bootm $loadaddr#$itb_config
meraki_boot=run set_ubi; run bootkernel1; run bootkernel2
ram_uboot=dhcp 0x82200000 u-boot.bin; go 0x82200000
set_ubi=set mtdids nand0=nand0; set mtdparts mtdparts=nand0:0x7300000@0xc00000(ubi); ubi part ubi
setenv bootcmd 'your commands here' for multiple commands or e.g.
setenv bootcmd bootm for a single one followed by
saveenv to save the environment.
saveenv comes back with error no command found
Then the manufacturer has modified uboot. You could try simply
help and see, if there's anything relevant, but it may also be that the manufacturer has disabled the ability to save the environment entirely from uboot's prompt.
LADYBUG # help
? - alias for 'help'
base - print or set address offset
bootm - boot application image from memory
chpart - change active partition
cmp - memory compare
cp - memory copy
crc32 - checksum calculation
echo - echo args to console
env - environment handling commands
exit - exit script
false - do nothing, unsuccessfully
fdt - flattened device tree utility commands
fuseipq - fuse QFPROM registers from memory
go - start application at address 'addr'
help - print command description/usage
i2c - I2C sub-system
imxtract- extract a part of a multi-image
loop - infinite loop on address range
md - memory display
mm - memory modify (auto-incrementing address)
mtdparts- define flash/nand partitions
mtest - simple RAM read/write test
mw - memory write (fill)
nand - NAND sub-system
nboot - boot from NAND device
nm - memory modify (constant address)
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
setenv - set environment variables
showvar - print local hushshell variables
source - run script from memory
test - minimal test like /bin/sh
true - do nothing, successfully
uartrd - uartrd read from second UART
uartwr - uartwr to second UART
ubi - ubi commands
version - print monitor, compiler and linker version
help env, maybe there's something useful.
LADYBUG # help env
env - environment handling commands
Hmh, well, that's not very useful. There isn't much else you can do other than taking a full dump of uboot and searching the dump for words that look like they could be commands and it's not guaranteed that there even are any commands that
help didn't already list.
I posted the dump of the serial output but not sure what to do with it really. If I could get some devs that know about LADYBUG uboot and how to get this going that would be awesome. I hate getting this far and have "nothing"
I was talking about dumping the actual uboot partition's contents, not the serial output.
ahh I can do that. How should I share the file?
Another option would be to boot openwrt again, install uboot-envtools, and try to change the uboot settings from within openwrt.
it is installed but now how do I use it to update the uboot?
Same way, printenv, setenv and saveenv.
Will need to make sure it points the the correct partition 1st, but I guess you can tell by simply running printenv from openwrt.
/bin/ash: printenv: not found
Might be fw_printenv, etc, no openwrt device access atm, cannot check.
Cannot parse config file '/etc/fw_env.config': No such file or directory
I think this is your issue. Try adding
DEVICE_DTS_CONFIG := config@3
target/linux/ipq40xx/image/generic.mk. Either put it in the mr33 section or create a new one for the mr74.
I'm not actually building the image. I am using premade images from a mr33 that has openwrt on it. You would have to walk me thru this because I am very new to this level of openwrt and embedded devices