element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products
  • More
Raspberry Pi
Blog Update process to enable to full 512MB RAM
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
GPIO Pinout
Raspberry Pi Wishlist
Comparison Chart
Quiz
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: fustini
  • Date Created: 14 Nov 2012 6:07 PM Date Created
  • Views 1911 views
  • Likes 1 like
  • Comments 6 comments
Related
Recommended
  • raspi-config
  • rev_2
  • raspberry_pi
  • revision_2
  • rpi
  • 512mb
  • raspbian
  • linux

Update process to enable to full 512MB RAM

fustini
fustini
14 Nov 2012

Hello - I thought it might be helpful to highlight the process of updating a SD card to take advantage of the full 512MB on the new Raspberry Pi (Rev 2.0).  I am using an element14 pre-programmed SD card .  It contains Raspbian "Wheezy" with kernel and firmware from July 15th (per modification dates in /boot).  This is recent enough to boot the 512MB Rev 2.0 model, but only 256MB of the 512MB RAM will be recognized.

 

After booting the Pi, you can access the command prompt (called the "shell" in Linux) using LXTerminal.  You can launch that application by clicking in the lower left hand corner to open the programs menu (where the start menu would be in Windows), selecting the Accessories group and then clicking LXTerminal.

 

Before updating the Pi, you'll need to make sure that your Raspberry Pi has a Internet connection.  To start the update, enter the following command into the terminal window (based on instructions from a previous discussion thread):

sudo apt-get update && sudo apt-get install raspi-config libraspberrypi*

You should see output similar to the following:

pi@raspberrypi ~ $ sudo apt-get update && sudo apt-get install raspi-config libraspberrypi*

Hit http://archive.raspberrypi.org wheezy InRelease

Hit http://mirrordirector.raspbian.org wheezy InRelease

Hit http://archive.raspberrypi.org wheezy/main armhf Packages

Ign http://archive.raspberrypi.org wheezy/main Translation-en

Get:1 http://mirrordirector.raspbian.org wheezy/main armhf Packages [7378 kB]

Get:2 http://mirrordirector.raspbian.org wheezy/contrib armhf Packages [23.3 kB]

Get:3 http://mirrordirector.raspbian.org wheezy/non-free armhf Packages [47.8 kB]

Get:4 http://mirrordirector.raspbian.org wheezy/rpi armhf Packages [14 B]

Ign http://mirrordirector.raspbian.org wheezy/contrib Translation-en

Ign http://mirrordirector.raspbian.org wheezy/main Translation-en

Ign http://mirrordirector.raspbian.org wheezy/non-free Translation-en

Ign http://mirrordirector.raspbian.org wheezy/rpi Translation-en

Fetched 4 B in 47s (0 B/s)                                                                                                                                   

Reading package lists... Done

Reading package lists... Done

Building dependency tree      

Reading state information... Done

Note, selecting 'libraspberrypi0' for regex 'libraspberrypi*'

Note, selecting 'libraspberrypi-bin' for regex 'libraspberrypi*'

Note, selecting 'libraspberrypi-dev' for regex 'libraspberrypi*'

Note, selecting 'libraspberrypi-doc' for regex 'libraspberrypi*'

The following extra packages will be installed:

  raspberrypi-bootloader triggerhappy

The following NEW packages will be installed:

  triggerhappy

The following packages will be upgraded:

  libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0 raspberrypi-bootloader raspi-config

6 upgraded, 1 newly installed, 0 to remove and 192 not upgraded.

Need to get 64.7 MB of archives.

After this operation, 14.1 MB disk space will be freed.

Do you want to continue [Y/n]? y

Get:1 http://archive.raspberrypi.org/debian/ wheezy/main libraspberrypi-dev armhf 1.20121025-1 [561 kB]

Get:2 http://mirrordirector.raspbian.org/raspbian/ wheezy/main triggerhappy armhf 0.3.4-2 [31.2 kB]

Get:3 http://archive.raspberrypi.org/debian/ wheezy/main libraspberrypi-doc armhf 1.20121025-1 [31.4 MB]

Get:4 http://archive.raspberrypi.org/debian/ wheezy/main libraspberrypi-bin armhf 1.20121025-1 [121 kB]                                                      

Get:5 http://archive.raspberrypi.org/debian/ wheezy/main libraspberrypi0 armhf 1.20121025-1 [384 kB]                                                         

Get:6 http://archive.raspberrypi.org/debian/ wheezy/main raspberrypi-bootloader armhf 1.20121025-1 [32.3 MB]                                                 

Get:7 http://archive.raspberrypi.org/debian/ wheezy/main raspi-config all 20121028 [6654 B]                                                                  s

Fetched 64.7 MB in 3min 0s (359 kB/s)                                                                                                                       

perl: warning: Setting locale failed.

perl: warning: Please check that your locale settings:

          LANGUAGE = (unset),

          LC_ALL = (unset),

          LC_TIME = "en_US.UTF-8",

          LC_MONETARY = "en_US.UTF-8",

          LC_ADDRESS = "en_US.UTF-8",

          LC_TELEPHONE = "en_US.UTF-8",

          LC_NAME = "en_US.UTF-8",

          LC_MEASUREMENT = "en_US.UTF-8",

          LC_IDENTIFICATION = "en_US.UTF-8",

          LC_NUMERIC = "en_US.UTF-8",

          LC_PAPER = "en_US.UTF-8",

          LANG = "en_GB.UTF-8"

    are supported and installed on your system.

perl: warning: Falling back to the standard locale ("C").

locale: Cannot set LC_ALL to default locale: No such file or directory

(Reading database ... 56308 files and directories currently installed.)

Preparing to replace libraspberrypi-dev 1.20120714-1 (using .../libraspberrypi-dev_1.20121025-1_armhf.deb) ...

Unpacking replacement libraspberrypi-dev ...

Preparing to replace libraspberrypi-doc 1.20120714-1 (using .../libraspberrypi-doc_1.20121025-1_armhf.deb) ...

Unpacking replacement libraspberrypi-doc ...

Preparing to replace libraspberrypi-bin 1.20120714-1 (using .../libraspberrypi-bin_1.20121025-1_armhf.deb) ...

Unpacking replacement libraspberrypi-bin ...

Preparing to replace libraspberrypi0 1.20120714-1 (using .../libraspberrypi0_1.20121025-1_armhf.deb) ...

Unpacking replacement libraspberrypi0 ...

Preparing to replace raspberrypi-bootloader 1.20120714-1 (using .../raspberrypi-bootloader_1.20121025-1_armhf.deb) ...

Adding 'diversion of /boot/bootcode.bin to /usr/share/rpikernelhack/bootcode.bin by rpikernelhack'

Adding 'diversion of /boot/fixup.dat to /usr/share/rpikernelhack/fixup.dat by rpikernelhack'

Adding 'diversion of /boot/fixup_cd.dat to /usr/share/rpikernelhack/fixup_cd.dat by rpikernelhack'

Adding 'diversion of /boot/kernel.img to /usr/share/rpikernelhack/kernel.img by rpikernelhack'

Adding 'diversion of /boot/kernel_cutdown.img to /usr/share/rpikernelhack/kernel_cutdown.img by rpikernelhack'

Adding 'diversion of /boot/kernel_emergency.img to /usr/share/rpikernelhack/kernel_emergency.img by rpikernelhack'

Adding 'diversion of /boot/start.elf to /usr/share/rpikernelhack/start.elf by rpikernelhack'

Adding 'diversion of /boot/start_cd.elf to /usr/share/rpikernelhack/start_cd.elf by rpikernelhack'

Unpacking replacement raspberrypi-bootloader ...

Selecting previously unselected package triggerhappy.

Unpacking triggerhappy (from .../triggerhappy_0.3.4-2_armhf.deb) ...

Preparing to replace raspi-config 20120715 (using .../raspi-config_20121028_all.deb) ...

Unpacking replacement raspi-config ...

Processing triggers for man-db ...

locale: Cannot set LC_ALL to default locale: No such file or directory

Setting up raspberrypi-bootloader (1.20121025-1) ...

Memory split is now set in /boot/config.txt.

You may want to use raspi-config to set it

Removing 'diversion of /boot/bootcode.bin to /usr/share/rpikernelhack/bootcode.bin by rpikernelhack'

Removing 'diversion of /boot/fixup.dat to /usr/share/rpikernelhack/fixup.dat by rpikernelhack'

Removing 'diversion of /boot/fixup_cd.dat to /usr/share/rpikernelhack/fixup_cd.dat by rpikernelhack'

Removing 'diversion of /boot/kernel.img to /usr/share/rpikernelhack/kernel.img by rpikernelhack'

Removing 'diversion of /boot/kernel_cutdown.img to /usr/share/rpikernelhack/kernel_cutdown.img by rpikernelhack'

Removing 'diversion of /boot/kernel_emergency.img to /usr/share/rpikernelhack/kernel_emergency.img by rpikernelhack'

Removing 'diversion of /boot/start.elf to /usr/share/rpikernelhack/start.elf by rpikernelhack'

Removing 'diversion of /boot/start_cd.elf to /usr/share/rpikernelhack/start_cd.elf by rpikernelhack'

Setting up libraspberrypi0 (1.20121025-1) ...

No existing /etc/asound.conf, creating one with preferred config

Setting up libraspberrypi-dev (1.20121025-1) ...

Setting up libraspberrypi-doc (1.20121025-1) ...

Setting up libraspberrypi-bin (1.20121025-1) ...

Setting up triggerhappy (0.3.4-2) ...

Error opening '/dev/input/event*': No such file or directory

Setting up raspi-config (20121028) ...

 

Following the update, the raspi-config configuration utiltity can now be run to set desired amount of memory that with be allocated for the CPU versus the GPU.  In the terminal, enter the command:

sudo raspi-config

Select the "memory_split" menu item using the down arrow key and press enter:

image

This will open the memory allocation configuration screen.  On this screen, you can input the amount of memory (e.g. RAM) that you want to allocate to the GPU (graphics processor):

image

The remaining memory is then allocated to the CPU (general purpose processor).  The default is 64 MB for the GPU which would leave 448 MB for the CPU on the 512MB Rev 2.0 Raspberry Pi.  Allocating more memory to the GPU may improve performance for some 3D graphics or media applications.  However, this may reduce the number of applications that can be run at once and also reduce the performance for other types of programs.

 

After choosing the desired value, select the <Ok> button and hit Enter.  Finally select the <Finish> button on the main menu and select <Yes> when asked if the system should reboot.

 

Following the reboot, launch LXTerminal and enter this command to open a system performance utility called "top":

top

 

The utility should appear similar to this screenshot:

image

Notice the hilighted text "448996" just right of "KiB Mem:" which indicates that the system is using the full 512MB memory less the 64MB allocated the GPU.

 

Cheers,

Drew

  • Sign in to reply

Top Comments

  • HBrydon
    HBrydon over 13 years ago in reply to HBrydon +1
    [I am answering my own question] I have a B2 RPi and I am running the 2012-08-08-wheezy-armel (Debian) image, which does not recognize memory beyond 256MB. Here is what I did in an attempt to get all 512MB…
  • HBrydon
    HBrydon over 13 years ago in reply to HBrydon +1
    [This is Dec 17] It seems that you can now skip the above step. I haven't verified completely yet but it appears that the Debian Wheezy maintainers have updated the boot loader so you don't need to do…
  • Former Member
    Former Member over 12 years ago +1
    Thanks @Drew Fustini for the great article! This worked just as you said. I was in contact with Element 14 because I thought they sent me the wrong version, and was about to get real pissed. Rocking the…
Parents
  • HBrydon
    HBrydon over 13 years ago

    [This is Nov 16] I have a type B2 board with Debian Wheezy.  It does not see more than 256MB, before or after doing the Debian version of the above sequence.  Is there any info on when I might be able to use all 512MB with it?  I'd like to use the Oracle JDK so reverting to Raspbian Wheezy isn't a good choice for me.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
Comment
  • HBrydon
    HBrydon over 13 years ago

    [This is Nov 16] I have a type B2 board with Debian Wheezy.  It does not see more than 256MB, before or after doing the Debian version of the above sequence.  Is there any info on when I might be able to use all 512MB with it?  I'd like to use the Oracle JDK so reverting to Raspbian Wheezy isn't a good choice for me.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
Children
  • HBrydon
    HBrydon over 13 years ago in reply to HBrydon

    [I am answering my own question] I have a B2 RPi and I am running the 2012-08-08-wheezy-armel (Debian) image, which does not recognize memory beyond 256MB.

     

    Here is what I did in an attempt to get all 512MB to work:

     

    On my windows machine, I got a second SD card and loaded the 2012-10-28-wheezy-raspbian image on it, made a copy of the files that are visible to Windows and stored them in a temporary directory (on hard disk).  [These seemed to be the files present in /boot when linux runs.]  I loaded the SD card containing my "existing" 2012-08-08-wheezy-armel image, created a subdirectory "NewFiles" and copied the saved files to it.  I rebooted my RPi with this card, went to /boot and (TADA!) the stored files are in /boot/NewFiles.  I saved the existing "/boot" files to "/boot/OldFiles" and moved all "/boot/NewFiles" to "/boot".  Following reboot (it booted!!), the RPi now recognized that it has 512MB memory.  I haven't tested everything but it is looking good.  Hopefully the next 'wheezy-armel' image will have this fixed so we don't have to do this workaround.  I used an SD card from my camera and lost some pictures that were not backed up but, alas, I got my RPi running better...

     

    It seems that on Windows, the only files visible on the SD card are the files in the linux /boot directory but nothing else in the linux file system.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • fustini
    fustini over 13 years ago in reply to HBrydon

    Thanks for adding this tip for those using armel

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • HBrydon
    HBrydon over 13 years ago in reply to HBrydon

    [This is Dec 17] It seems that you can now skip the above step. I haven't verified completely yet but it appears that the Debian Wheezy maintainers have updated the boot loader so you don't need to do the kluge I describe above. To update your Pi to the latest software, go to command prompt and:

     

      sudo apt-get update

      sudo apt-get upgrade

     

    and your boot files should now be updated for 2012-08-08-wheezy-armel. I would expect that any later builds will also have this fix.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube