On Thursday, July 14, 2016 at 8:18:37 PM UTC+2, William Hermans wrote: > > Well, I used apt-get install. I traced back the command entered when >> examining .bash_history: >> *# sudo apt-get install linux-image-4.1.15-bone-rt-r18 * > > > So you say it just failed, and when you examined the second stage uEnv.txt > file the uname_r variable had not changed to reflect the upgrade ? What > kind of power supply are you using, and how much do you have running on > the board ? > > Anyway, using APT is the correct way to install a kernel on Debian. > Period. Not just for this hardware, but in general. So I would say that you > just experienced a glitch that is not usually that happens when upgrading. > But when I tell you that I've not experienced this myself in 3.5 years of > using this board . . . that's not entirely accurate. I've experienced a few > glitches here, and there. I just never dug into what happened. Instead I > just tried again, and it worked . . . So maybe nothing is 100% perfect, but > it does work if you keep at it. > > Heres a tip though. Whenever flashing a new image, or doing anythign like > upgrading the kernel. Disconnect, and / or turn off everything non > essential. Peripheral wise. ethernet, and eMMC should be fine, but passed > that turn every thing else off. >
Thanks William, I dod not expext a failre either doing apt upgrade / installs of kernels either. Not sure about the uEnv.txt. My /boot directory shows: bash-4.3$ ls -la total 33192 drwxr-xr-x. 4 root root 4096 Jul 11 18:04 . drwxr-xr-x. 21 root root 4096 Jan 24 23:38 .. -rw-r--r--. 1 root root 134233 Jan 12 2016 config-4.1.15-bone-rt-r18 -rw-r--r--. 1 root root 154972 Jan 21 21:22 config-4.1.15-ti-rt-r43 drwxr-xr-x. 4 root root 4096 Jul 11 18:03 dtbs -rw-r--r--. 1 root root 4245828 Jul 11 18:04 initrd.img-4.1.15-bone-rt-r18 -rw-r--r--. 1 root root 4177318 Jun 20 12:12 initrd.img-4.1.15-ti-rt-r43 -rw-r--r--. 1 root root 4096241 Jun 15 19:26 initrd.img-4.1.15-ti-rt-r43.old-dkms -rw-r--r--. 1 root root 492 Jan 25 00:41 SOC.sh -rw-r--r--. 1 root root 3034732 Jan 12 2016 System.map-4.1.15-bone-rt-r18 -rw-r--r--. 1 root root 3371694 Jan 21 21:22 System.map-4.1.15-ti-rt-r43 drwxr-xr-x. 2 root root 4096 Jan 24 23:38 uboot -rw-r--r--. 1 root root 1652 Jul 11 18:04 uEnv.txt -rwxr-xr-x. 1 root root 6932296 Jan 12 2016 vmlinuz-4.1.15-bone-rt-r18 -rwxr-xr-x. 1 root root 7800752 Jan 21 21:22 vmlinuz-4.1.15-ti-rt-r43 So uEnv.txt seems to be updated at the time by the apt-get install, and both the old and new kernel are available. Start of uEnv.txt is: bash-4.3$ sudo head uEnv.txt #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 uname_r=4.1.15-bone-rt-r18 #uuid= #dtb= ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..) ##BeagleBone Black: HDMI (Audio/Video) disabled: #dtb=am335x-boneblack-emmc-overlay.dtb But, you mentioned something else, that got me thinking: after backing up the sd card and writing a new image to the sd-card, it failed first pass (no booting BBG whatsever I tried). Flashed the image again, and then my BBG booted. So now I start to suspect my sd card actually. Time for new sd card to make sure. I'll be watching the power supply as well; I'm using a 6600 mAh Lipoly with an Adafruit 500mA Power charge and adapter (if interested: first glimpse of my project page here <http://catch22heller.blogspot.nl/p/blog-page.html>). I'm not 100% convinced on the power supply as well with occasional drops during booting. So maybe I'l go for micro-usb power supply for "mission critical" changes to the image to ensure correct upgrades and only use the battery when testing the entire setup with stepper drivers and motors. T Thanks for your suggestions. Will check john3909's remarks later as well and see if I get the PRU's working with uio/prussdrv.h and the selected kernel. -- 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/03ba76ad-1d89-4c0d-877c-23f52b6dcdc7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
