On 2014-12-29, Ian Campbell wrote: > Given the beaglebone specific findfdt which Robert links to above
Several other ti platforms also use findfdt, FWIW.
> could we add a check to bootscr.beaglebone which refuses to boot on a
> white? (looks like we can look at $board_name directly).
Yes, that should work. The standard boot command runs findfdt before
loading the boot script. So, something along these lines:
diff --git a/bootscript/bootscr.beaglebone b/bootscript/bootscr.beaglebone
index a0e5121..1d079f8 100644
--- a/bootscript/bootscr.beaglebone
+++ b/bootscript/bootscr.beaglebone
@@ -1,4 +1,14 @@
-# boot script for BeagleBone
+# boot script for BeagleBone Black
+
+# BeagleBone white uses a different .dtb file, and flash-kernel is
+# currently unable to support multiple .dtb files.
+if test "${board_name}" = "A335BONE"
+then
+ echo "BeagleBone white detected, unsupported platform."
+ echo "Exiting in 10 seconds..."
+ sleep 10
+ exit
+fi
setenv device mmc
setenv partition ${bootpart}
Although, ideally, this case should be detected before the user reboots,
so they can manually tweak /etc/flash-kernel/ to use a customized boot
script.
live well,
vagrant
signature.asc
Description: PGP signature
