View source for Beagleboard:Updating The Software

=Checking The Angstrom Image Version=

You should check the version of the image on the microSD card used to flash the card by opening the ID.txt file in the FAT partition. It should look something like this:

'''CLoud9 GNOME Image 2013.06.20'''

The last 10 characters on the right are the date of the release of the image. 2013=year 06=month 20=day<br>

You can also check the eMMC image that has been flashed by opening the same file in the FAT partition labeled BEAGLEBONE from the desktop or from the board when connected to a PC as a USB Drive.

You can find a much more detailed description of this and other ways to do it at http://www.crashcourse.ca/wiki/index.php/Examining_your_BBB_install_version . It is well worth the visit!

You should also check the version of the software on the eMMC by plugging the board into a PC USB port, waiting for the storage device to be mounted, and reading the ID.TXT file as indicated above.<br>
It is suggested that you do this to see if your board needs updating or not.

=Flashing the eMMC=

There is a Linux version of the process as well that does not rely on these images. It describes how the flashing process works.<br>
If used, it is up to the user to make sure the correct files are used in the process. You can find information on this process at [http://www.crashcourse.ca/wiki/index.php/BBB_software_update_process Linux SW Update Method]
<br>

==Equipment==

You will need a [http://simple.wikipedia.org/wiki/MicroSD microSD] card of 4GB or greater. You can find them at many stores that carry electronic equipment like cameras.<br>

You will need a *[http://en.wikipedia.org/wiki/Memory_card_reader USB based card reader] for the next step. You can find them at many stores that carry electronic equipment like cameras. You insert the microSD card into the card reader and the card reader into a USB port on your PC.<br>

It is recommended that a 5 VDC power supply of 1A or a powered USB HUB be used.<br>
<br>
Current during the flash process can exceed 500mA in some instances which can cause the USB power to shutdown from a PC or laptop.<br>
You can also use a [https://www.sparkfun.com/products/11456 5V Wall Wart] power adapter with a USB port on it as long as it can deliver 1A.<br>
Do not flash the board with the Ethernet cable attached. The Ethernet connections uses more current.<br>

==Procedure==

1) Download the image file of choice by clicking on the links below and saving it to a directory of choice on your PC. '''ALL''' images are eMMC flasher images that will flash the eMMC. They are not images to be used to boot from the uSD expecting a desktop or anything close to a good experience. They are for flashing only. They do contain on them an image that is flashed onto the eMMC during the flashing process.<br>

*[https://s3.amazonaws.com/angstrom/demo/beaglebone/BBB-eMMC-flasher-2013.09.04.img.xz Production Image 2013.09.04]<br>

There are several key fixes in this release. (Originally the 2013.08.21 release).<br>

 -The HDMI timing generation was changed. This appears to have greatly improved the HDMI timings. Even the Atrix lapdock is working.<br>
 -The uSD card detection is now working. This allows for a SD card to be added for additional storage.<br>

 
 [koen@rrMBP v2012.12]$ ./oebb.sh changelog 20130903-1822..20130904-0815
  Changes to meta-openembedded in between 20130903-1822..20130904-0815
 Koen Kooi (1):
      oscam: bump SRCREV
 Changes to meta-beagleboard in between 20130903-1822..20130904-0815
  Koen Kooi (1):
      linux-mainline 3.8: disable USB suspend for beaglebone
 Changes to meta-beagleboard in between 20130731-1646..20130814-1410
  Koen Kooi (6):
      linux-mainline 3.8: add support for GPS protocape
      linux-mainline 3.8: pps-gpio: add pinctrl support
      linux-mainline 3.8: enable ath9k_htc
      linux-mainline 3.8: convert SPI capes to SPIdev
      linux-mainline 3.8: bebopr cape fixes
      linux-mainline 3.8: beaglebone HDMI rework
 Changes to meta-ros in between 20130731-1646..20130814-1410
  Lukas Bulwahn (25):
      test-reports: adding a test report that shows the libpoco problem
      libpoco: including an external recipe for the poco library
      libpoco: replacing our recipe by the external one
      libpoco: replacing license string causing warnings by common OpenEmbedded license string
      libpoco: updating to current version 1.4.6p1
      libpoco: using recipe name for pcre library instead of its alias
      libpoco: formatting the recipe
      libpoco: adding a patch to link correctly with pcre
      refering to new test reports
      README: acknowledge contribution and origin of libpoco recipe
      dynamic-reconfigure: adding patch to resolve path (resolving #126)
      catkin: correcting the downloadfilename that was missed before
      python-netifaces: initial recipe
      rosgraph: adding runtime dependency (resolves #131)
      roslaunch: adding runtime dependency (resolves #132)
      rospack: improving runtime dependencies (resolves #116)
      libpoco: openssl required for libpoco when compiling pcl-ros
      cleaning up recipes-devtools/python recipes
      catkin class includes BBCLASSEXTENDS
      roscpp-core: collected common definition in .inc file
      ros: removing superfluous definitions
      images: cleaned and renamed image recipe
      tuning newlines
      README: was updated to hydro; core-image was renamed
      CONTENTS: adjusted to current state and tuned formatting
  herbrechtsmeier (3):
      Merge pull request #129 from bulwahn/libpoco
      Merge pull request #133 from bulwahn/roscore-running
      Merge pull request #140 from bulwahn/master
  vmayoral (1):
      initial ros-tutorials and common-tutorials recipes (resolves #124)
  Changes to openembedded-core in between 20130731-1646..20130814-1410
  Jonathan Liu (1):
      cups: remove /var/run from package as cupsd will populate it on startup
  Martin Jansa (1):
      cups: add PACKAGECONFIG for avahi
  Saul Wold (4):
      cups: Update to 1.6.1
      cups: remove old patch files
      cups: Update to 1.6.2
      cups: Update to 1.6.3
  Stefan Herbrechtsmeier (1):
      cmake.bbclass: Don't use packages from the native build machine


*[https://s3.amazonaws.com/angstrom/demo/beaglebone/BBB-eMMC-flasher-2013.06.20.img.xz Updated Image 2013.06.20]<br>

Changes to meta-beagleboard in between 20130615-1105..20130620-1157

 Khem Raj (1):
      linux-mainline-3.8: Fix random segfaults and boot issues seen with gcc-4.8
 Koen Kooi (8):
      Merge pull request #5 from kraj/master
      contrib: bone-flash-tool: verify some files after flashing
      contrib: bone-flash-tool: mount VFAT partition in sync mode
      bone101: update to latest git
      bonescript: update to latest git
      bonescript: fix do_install
      contrib: bone-flash-tool: check bootloader integrity
      u-boot-denx: work around EEPROMs filled with zeroes
 Changes to meta-ti in between 20130615-1105..20130620-1157
 Koen Kooi (3):
      bone101: update to latest git
      bonescript: update to latest git
      bonescript: fix do_install
 Changes to meta-ros in between 20130615-1105..20130620-1157
 Lukas Bulwahn (5):
      common-msgs: initial commit of all common messages
      image-transport: initial commit
      angles: initial commit
      tf: initial commit
      rostest: rostest depends on rostest-native (resolves #83)
 Stefan Herbrechtsmeier (2):
      genlisp: Setup python script path during runtime via find_program
      gencpp: Setup python script path during runtime via find_program
 herbrechtsmeier (3):
      Merge pull request #93 from bulwahn/image-transport
      Merge pull request #94 from bulwahn/tf
      Merge pull request #97 from bulwahn/rostest-depends-on-rostest-native-v2

*[https://s3.amazonaws.com/angstrom/demo/beaglebone/BBB-eMMC-flasher-2013.06.06.img.xz Updated Image 2013.06.06]

Changes to meta-angstrom in between 20130527-1549..20130606-0749

 Koen Kooi (5):
      contrib: add more angstrom wallpapers
      libgnome: update wallpaper to include yocto compatible logo
      connman: add angstrom specific settings
      images: add connman-angstrom-settings to connman based images
      fixmac: a udev rule to generate a random MAC address when needed for eth* devices
 Changes to meta-openembedded in between 20130527-1549..20130606-0749
 Koen Kooi (2):
      xbmc: add patch to make 'ld-is-gold' work with configure
      xbmc: convert to PACKAGECONFIG and fix runtime dependencies
 Stefan Herbrechtsmeier (1):
      libtinyxml: Add native support and use relative paths
 Changes to meta-beagleboard in between 20130527-1549..20130606-0749
 Koen Kooi (17):
      contrib: bone-flash-tool: add emmc and mmc imaging scripts
      contrib: bone-flash-tool: update emmc flasher script
      contrib: bone-flash-tool: fix mmc-prepare script untar function
      contrib: bone-flash-tool: delete stray flasher scripts if present
      linux-mainline 3.8: add virtual capes for beaglebone
      linux-mainline 3.8: add support for TT3201 CAN cape
      linux.inc: install capebus dts files next to the dtbo files in /lib/firmware
      xserver-xf86-config: add config for beaglebone
      beaglebone: switch to xf86-video-modesetting
      linux-mainline 3.8: add support for MPU6050
      contrib: bone-flash-tool: mount improvements
      linux-mainline 3.8: fix LCD4 button polarity, add SPI1 CS example
      linux-mainline 3.8: fix LCD3 key polarity and DRM oopses
      linux-mainline 3.8: fix LCD7 key polarity
      linux-mainline 3.8: add DT GPIO helper
      linux-mainline 3.8: add fix for HDMI non audio modes and HDMI no audio virtual cape
      linux-mainline 3.8: remove hardcoded -I/usr/local/include from libtraceevent
 Changes to meta-ti in between 20130527-1549..20130606-0749
 Koen Kooi (2):
      xserver-xf86-config: switch ti33x to xf86-video-modesetting
      cloud9-gnome-image: include connman-angstrom-settings
 Changes to openembedded-core in between 20130527-1549..20130606-0749
 Denis 'GNUtoo' Carikli (1):
      boost: Activate zlib and bzip2 because they now work.
 Jonathan Liu (2):
      xf86-video-modesetting: upgrade to 0.7.0
      xf86-video-modesetting: backport fix for graphics corruption
 Khem Raj (1):
      boost: Upgrade 1.51 -> 1.52
 Lukas Bulwahn (1):
      site/common: deactivate a runtime check for ipv6-support in python >=2.7.1 that fails when cross-compiling
 Robert Yang (1):
      recipes-support: replace virtclass-native(sdk) with class-native(sdk)
 Samuel Stirtzel (1):
      boost: Use PARALLEL_MAKE for bjam
 Saul Wold (1):
      boost: Update to 1.53.0
 Stefan Herbrechtsmeier (1):
      boost: Add real native support


*[https://s3.amazonaws.com/angstrom/demo/beaglebone/BBB-eMMC-flasher-2013.05.27.img.xz Updated Image 2013.05.27]
 
 Power Button Support
 RS-232: DT overlay present, untested
 RS485: Not supported
 CAN: DT overlay present, untested
 TT CAN: Patches available from manufacturer, untested
 Weather: DT overlay present, only tested on BBW
 Audio: DT overlay present, only tested on BBW
 LCD3: DT overlay present, tested on BBW and BBB
 LCD4: DT overlay present, tested on BBW and BBB, needs pinmux changes for up/down
 LCD7: DT overlay present, tested on BBW, weird behaviour on BBB. Possible mux related
 Camera: DT overlay present, resetctrl integration. Triggers memory corruption on BBW, works on BBB
 Memory:
        * eMMC: DT overlay present, tested on BBW
        * NAND: no support
        * NOR: no support
 DVI-D: DT overlay present, tested on BBW
 DVI-D + audio: DT overlay, tested on BBW
 TIWI: No DT bindings for wilink driver, Balaji (TI) + Luca (TI) are working on that

OLD IMAGES
----
These are older images left for convenience if you need to go back a revision or two. The last numbers refer to a date of the image. i.e 2013=Year 05=month 08=day. Use these as a revision of the image. <br>

*[https://s3.amazonaws.com/angstrom/demo/beaglebone/BBB-eMMC-flasher-2013.06.20.img.xz Previous Production Image 2013.06.20]<br>
*[http://dominion.thruhere.net/koen/angstrom/beaglebone/BBB-eMMC-flasher-2013.05.08.img.xz Old Production Image 2013.05.08]<br>
*[http://dominion.thruhere.net/koen/angstrom/beaglebone/BBB-eMMC-flasher-2013.04.13-DDR3-400MHz.img.xz Old Production Image 2013.04.13]   -This version does not support audio over HDMI.<br>
*[http://dominion.thruhere.net/koen/angstrom/beaglebone/BBB-eMMC-flasher-2013.04.12.img.xz Pre-Production eMMC Flasher_2013.04.12]<br>
*[http://dominion.thruhere.net/koen/angstrom/beaglebone/BBB-eMMC-flasher-2013.04.11.img.xz Pre-Production eMMC ProductionFlasher_2013.04.11]<br>
*[http://dominion.thruhere.net/koen/angstrom/beaglebone/BBB-eMMC-flasher-2013.04.10.img.xz Pre-Production eMMC ProductionFlasher_2013.04.10]<br>

2) Unzip the file you downloaded to a directory on your PC using [http://www.7-zip.org/ 7-zip]. This file will be used to create the SD card that will be used to flash the eMMC on the board.<br>

3) Download the [https://wiki.ubuntu.com/Win32DiskImager DiskImager] software to copy the unzipped image file to the microSD card from the directory on your PC where you unzipped the file.<br>

4) Unzip the above downloaded software into a folder on the PC. If you choose, you can use the same folder as the program to be flashed is in.<br>

5) Run the WinDiskImager application. A small window will appear.<br>
  If you have questions on how to use the program, you can go to [https://launchpad.net/win32-image-writer Help]<br> 

6) Select the drive number that corresponds to the SD card reader you plugged in by clicking on the Device box with a letter in it. MAKE SURE YOU SELECT THE CORRECT DRIVE LETTER.<br> 

7) Select the file from the directory that you unzipped the new image to by clicking on the folder icon next to the Device box.<br>

8) Select the write option to start the writing process.<br>

9) When finished, remove the microSD card from the reader. Insert the newly created microSD card into the board.<br>

   MAKE SURE THE ETHERNET CABLE AND ANY USB DEVICES ARE UNPLUGGED FROM THE BOARD.

10) Hold switch S2 '''(Boot Switch, see picture below)''' down by pressing on it and holding it while plugging in the power cable.<br>

11) Continue to hold the button until the first User LED comes on. <br>


[[File:CONN_REVA5A.jpg]]


 
12) The board will start flashing the eMMC and the LEDs will flash to show activity. It will take about 45 minutes to flash the board.<br>

13) When all four LEDS are on steady, the eMMC is flashed.<br>

14) Remove the power from the board by removing the power cable. <br>
 
15) Remove the microSD card from the board.<br>
 
16) Reapply the power to the board by plugging in the cable.<br>

17) Board should boot.<br>

=Image For Booting From microSD=
There are periodic images that are available that can be used to create a microSD card that will allow you to boot direct from the microSD slot.<br>
These images may not be the same as the production image. They are provided for convenience.<br>

   To force a boot from the microSD card, delete the MLO file in the FAT partition of the eMMC.<br>
   You can access this when the board is connected over the USB cable and it appears as a thumbdrive.<br>


==Equipment==

You will need a [http://simple.wikipedia.org/wiki/MicroSD microSD] card of 4GB or greater. You can find them at many stores that carry electronic equipment like cameras.<br>

You will need a *[http://en.wikipedia.org/wiki/Memory_card_reader USB based card reader] for the next step. You can find them at many stores that carry electronic equipment like cameras. You insert the microSD card into the card reader and the card reader into a USB port on your PC.<br>

==Procedure==

1) Download the image file of choice by clicking on the links below and saving it to a directory of choice on your PC.<br>

[https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.08.21.img.xz SD Boot 2013.08.21] Current Production Image<br>
[https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.06.img.xz SD Boot 2013.06.06]<br>
[https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.05.28.img.xz SD Boot 2013.05.28]<br>
[http://dominion.thruhere.net/koen/angstrom/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.05.24.img.xz SD Boot 2013.05.24]<br>

2) Unzip the file you downloaded to a directory on your PC using [http://www.7-zip.org/ 7-zip]. This file will be used to create the SD card that will be used to flash the eMMC on the board.<br>

3) Download the [https://wiki.ubuntu.com/Win32DiskImager DiskImager] software to copy the unzipped image file to the microSD card from the directory on your PC where you unzipped the file.<br>

4) Unzip the above downloaded software into a folder on the PC. If you choose, you can use the same folder as the program to be flashed is in.<br>

5) Run the WinDiskImager application. A small window will appear.<br>
  If you have questions on how to use the program, you can go to [https://launchpad.net/win32-image-writer Help]<br> 

6) Select the drive number that corresponds to the SD card reader you plugged in by clicking on the Device box with a letter in it. MAKE SURE YOU SELECT THE CORRECT DRIVE LETTER.<br> 

7) Select the file from the directory that you unzipped the new image to by clicking on the folder icon next to the Device box.<br>

8) Select the write option to start the writing process.<br>

9) When finished, remove the microSD card from the reader. Insert the newly created microSD card into the board.<br>

10)Apply the power to the board by plugging in the cable.<br>

11) Board should boot.<br>

=Reported Issues=

We have had a few cases where it appears that attempts to flash the board were caused by an improperly formatted microSD card.<br>
This can be resolved by performing the following steps on the microSD card before copying the image to it using the Diskimager software.<br>

1) Download the HP Formatting tool from one of the following locations<br>
  [HP Format Tool Ver 2.18 http://www.pcworld.com/downloads/file/fid,64963-page,1/description.html]<br>
  [HP Format Tool Ver 2.18 http://files.extremeoverclocking.com/file.php?f=197]<br>
  [HP Format Tool Ver 2.18 http://hp-usb-disk-storage-format-tool.software.informer.com/]<br>
  [HP Format Tool Ver 2.0.6 http://www.4shared.com/rar/9mNWV4Vl/HP_USB_Disk_Storage_Format_Too.html]<br>
2) Decompress the verification image file using [http://www.7-zip.org/ 7-zip]. <br>
3) Insert the microSD card writer/reader into the Windows machine.<br> 
4) Insert 4GB microSD card into the reader/writer. <br>
5) Run the HPFormatter tool and format the SD card for FAT or FAT32.<br>
<blockquote>         NOTE: In Windows 7 you will need to run this in administrator mode by right clicking and select "Run as Administrator"<br>
               Under Windows XP, the format options are FAT32 and NTFS. Select FAT32.<br>
               Under Windows 7, the format options are FAT and NTFS. Select FAT.<br>
               You may see different operation for some reason where FAT32 or FAT may or not be there. You can select FAT or FAT32.<br>

         NOTE: Make sure you select the drive letter of the uSD and not some other drive!!!<br>
</blockquote>
6) Close the HPFormatter tool when done.<br>
7) Remove the microSD card from the writer/reader.
8) Follow the steps above to create your flasher microSD card.

Return to the *[[Beagleboard:BeagleBoneBlack#Updating_the_eMMC_Software | Main Page]]