Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
livebox:beagleboneporting [2014/02/11 09:05] – brett | livebox:beagleboneporting [2015/03/13 04:29] (current) – [Beagle bone notes] brett | ||
---|---|---|---|
Line 4: | Line 4: | ||
Notes on porting the HAH for the beagle bone. These notes really aren't for consumption by anybody but me as reminders for things I did whilst playing around on the Beagle Bone. | Notes on porting the HAH for the beagle bone. These notes really aren't for consumption by anybody but me as reminders for things I did whilst playing around on the Beagle Bone. | ||
+ | The Angstrom distribution was just too warty for my liking and I moved everything to UBUNTU which also allows the Raspberry PI and other embedded boards to also join the fun. | ||
+ | |||
+ | < | ||
===== Validating the cross compiler works ===== | ===== Validating the cross compiler works ===== | ||
Line 235: | Line 238: | ||
</ | </ | ||
- | ==== connman is fucked | + | ===== connman is shit ===== |
- | This service is not ready for the prime time and personally | + | Connman has no right to be used on MY embedded hardware, yeah yeah I know all the argument about fall back and what if the network isn't etc etc... But really I don't give a shit, if the network is not up we are hosed. |
+ | |||
+ | I don't want connman | ||
I want this -> http:// | I want this -> http:// | ||
- | How to remove connman and revert to traditional, might I add sane, network interface start up. | + | How to remove connman and revert to traditional network interface start up. |
< | < | ||
Line 283: | Line 288: | ||
</ | </ | ||
+ | ===== dmesg log filled with hdmi messages? ===== | ||
+ | |||
+ | After running the Beaglebone for a while you may notice messages like this | ||
+ | |||
+ | < | ||
+ | [drm: | ||
+ | </ | ||
+ | |||
+ | in the log called with dmesg. It's not really a problem unless you are trying to debug but still annoying. | ||
+ | |||
+ | To stop these edit the uEnv.txt file on the FAT partition (not uEnv.txt in /boot) | ||
+ | |||
+ | Mount the partition | ||
+ | < | ||
+ | mount / | ||
+ | </ | ||
+ | |||
+ | edit the uEnv.txt file to remove the drm_debug part | ||
+ | < | ||
+ | nano / | ||
+ | </ | ||
+ | |||
+ | and remove drm.debug=7 | ||
+ | |||
+ | Save the file: | ||
+ | < | ||
+ | Ctrl-X, Y | ||
+ | </ | ||
+ | |||
+ | Unmount the partition: | ||
+ | < | ||
+ | umount /mnt/card | ||
+ | </ | ||
+ | |||
+ | Reboot the board: | ||
+ | < | ||
+ | shutdown -r now | ||
+ | </ | ||
+ | |||
+ | ===== backing up the BeagleBone Black eMMC ===== | ||
+ | |||
+ | After you have got the BBB up and running how you like it, backing up is always a good idea. | ||
+ | |||
+ | You can of course back up the ini settings, plugboard scripts etc using the web GUI but I like to keep a backup of the entire eMMC. | ||
+ | |||
+ | There are a few methods to be found on the 'net that require the use of a script on a microSD card. This is ideally the best way but requires | ||
+ | stopping the BBB (and if SWMBO is expecting things to happen, that's never good) | ||
+ | |||
+ | So here is an option to use dd over ssh to backup to another PC (in my case a mac) | ||
+ | |||
+ | on the BBB | ||
+ | < | ||
+ | sudo dd if=/ | ||
+ | </ | ||
+ | |||
+ | n.b. the block size is set on the BBB using bs=1M but on the mac HAS to be bs=1m (lowercase) (I'm not sure if this is the case :) on a pc) | ||
+ | |||
+ | To restore. This needs to be done after booting from an SD card to free up the eMMC | ||
+ | The eMMC is then mmcblk1 not mmcblk0 | ||
+ | < | ||
+ | ssh themac@192.168.0.X "dd of=/ | ||
+ | </ | ||
+ | |||
+ | Then power down, remove the SD card and reboot. |