On 2014-10-03, peter green wrote:
> I started looking for ways to make the boot script detect whether it was
> running on the boundary u-boot or the debian u-boot. There is apparently
> a u-boot variable called "ver" but unfortunately neither the debian or
> the boundary u-boot had it turned on.
Pretty much a one-liner in include/configs/nitrogen6x.h:
/* Miscellaneous configurable options */
+#define CONFIG_VERSION_VARIABLE
There may be other variables set in the debian environment that aren't
present in the shipped u-boot, although if you've ever run saveenv, it
may always read your saved environment. Running "env default -a" will
revert to the default environment settings of the running u-boot, but
won't change the saved environment, so isn't persistant unless you save
it... which is annoying if you always want to run the defaults.
> setenv bootargs console=${console},${baudrate} root=${mmcroot}
...
> unfortunately after the "starting kernel" message there was no further
> output on serial and the system did not appear on the network. I tried
> various changes to the commands (loading the dtb at a higher address,
> trying the sabrelite dtb instead, changing the console device to 0
> instead of the 1 it defaulted to) but to no avail.
What exactly are ${console} and ${baudrate} set to? It looks like the
default is console=ttymxc1 and baudrate=115200 ...
You could also try building the version from experimental, on the off
chance it fixed some bugs. That's the version (2014.10) it would most
likely get added to in the debian packaging anyways.
live well,
vagrant
Attachment:
pgp99ZTxt7O8t.pgp
Description: PGP signature