Hello, I know that took some time out to type up and make known to everyone (including myself). First off, thank you.
... Secondly, yea boy! I always wondered what was going on while I was updating/upgrading/writing new images to BBB. I remember having trouble w/ newer machines b/c they were flashed "who knows when" and all while S2/Boot buttons were pressed, adding support for SD Cards, and saving particular info. as back up gave me the willies. Anyway, nice support. I thought I would add some encouragement to not stop at this point. Seth P.S. But like with what Mr. Dennis was saying, all this can be trying on newer kernels/images w/out supportive ideas for older kernels/images. Wheezy is when I jumped in to this hoopla. I knew exactly nothing about anything. Now, w/ time and effort (and reading some ideas), I have grown accustomed to be catered w/ already "born" images. BBB! On Monday, August 24, 2020 at 1:24:47 PM UTC-5 Dennis Bieber wrote: > On Mon, 24 Aug 2020 01:36:03 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user > steaksandwich86-re5...@public.gmane.org wrote: > > >Hi, > > > >I have a Beaglebone Black running kernel 3.8 (I think - I don't have > access > >to the BBB at the moment, so this is from memory). > >I am using this with a cape to drive a custom display. > > > >I am pretty sure it's booting from SD card, which has multiple partitions > >(one labelled rootfs and not visible to windows, and one that windows can > > 3.8 AND a dual partition... That is positively ANCIENT. Probably Debian > Wheezy, though maybe Debian Jessie in early releases. Wheezy was Debian v7, > Jessie v8, Stretch v9, and Buster (current release) is Debian v10. > > Wheezy has been out of support for years, Jessie support ended this > summer, and even Stretch is fading away. https://wiki.debian.org/LTS > > There have been many changes since Wheezy. Among them -- dropping the > FAT partition (a virtual READ-ONLY FAT) is created once the system boots -- > primarily so one can read the getting-started information); Change from > kernel loading device tree overlays to u-boot loading device tree overlays; > u-boot automatically detecting an SD card for booting if it is present, > instead of having to hold down the boot-select button. > > So... First confirm what device is used for booting (if you have to > hold down the boot-select to boot, it is quite likely the SD card). If it > is booting from eMMC, this gets more difficult -- you will need to save any > customizations for the display onto other media, as updates will basically > wipe out the eMMC. If it IS the SD card, I would recommend you seal that > card in a plastic holder so you don't damage it. THEN: > > Obtain a more up-to-date OS image http://beagleboard.org/latest-images > Note: if your display makes use of Xwindow features -- IE, a GUI > desktop, you'll need to find an LXQT image > https://elinux.org/Beagleboard:Latest-images-testing#Latest_Images_Testing > > Write it to a NEW 8+ GB (Balena Etcher is current preferred tool for > this). > > Insert it into the Beagle. Given the age of your system, you will > likely have to use the boot-select when booting it. Make sure you have a > network connection. SSH into the Beagle. > > Run sudo /opt/scripts/tools/grow-partition.sh (check the > spelling, I'm writing from memory since I did this for something like 8 SD > cards a few days ago). Reboot (again, you will likely need to hold down the > boot-select). This step makes the full SD card available, especially useful > if using an LXQT image (they've gotten to where there isn't any really user > space left in 4GB). > > Run sudo apt update > Run sudo apt upgrade (to make sure the card image is > up-to-date). > > I suggest, at this point, after you've configured the OS (set up any > customizations in .bashrc .bash-aliases, etc. and run > sudo apt install ... for any packages you /know/ are needed) you now > edit the /boot/uEnv.txt and uncomment the last line. This turns > the card into a flasher. > > Make sure the Beagle is connected to a wall-wart power supply via > barrel connector -- USB connections may not provide enough power for > reliable flashing. Reboot (holding boot-select if needed). It should boot > and go into eMMC flashing mode (LEDs sweeping left/right). Let it run until > it shuts down by itself. > > REMOVE the SD card (if you leave it in, it will just reflash the > Beagle). > > Boot the Beagle -- this will be running from eMMC. You can now insert > the SD card, and mount it (or if you have some other Linux system, mount it > there). Go back into /boot/uEnv.txt and recomment the last line. This > disables the flasher mode, and makes the SD card a normal boot image. And > since you've flashed the eMMC, it should now have the updated u-boot which > will automatically use the SD card for booting if it is installed. > > Now -- getting your existing application to work on the new card (or > eMMC) is something I can't help you with. If it used a custom device tree > overlay, you'll have to edit /boot/uEnv.txt to add the overlay to one of > the overlay slots (uncomment slot, change file path). If it requires > special drivers, you may have to see if a driver is available via apt > install... (You see why I said save the original SD card). > > NOTE: while the new u-boot will automatically attempt booting from an > SD card -- the change between kernel device tree loading to u-boot device > tree loading means your old card may be a problem. u-boot will try to load > device trees from your card, and then when the kernel starts it will try to > load the same device trees -- you likely will need the boot-select button > to force usage of the old SD card u-boot. > > > -- > Dennis L Bieber > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c9a2359b-25dd-446a-9246-06d5a84b316en%40googlegroups.com.
