Difference between revisions of "Loading JFFS2 Images Onto a Board"

From wiki.emacinc.com
Jump to: navigation, search
m (Added guiding info on what to write.)
m (by SoM Type: added note)
Line 38: Line 38:
  
 
=== by SoM Type ===
 
=== by SoM Type ===
 +
 +
'''Don't forget the SOM-3517'''
  
 
== SoM-9260M ==
 
== SoM-9260M ==

Revision as of 23:54, 6 November 2013

TODO: {{#todo:Add some text (11.06.13-08:24->MW+)(11.06.13-17:55->MD+)|Michael Welling|oe 4,oe 5,mw,md,InProgress}}

Background

Basic Info of what needs to go here The bootloader pulls images over the network from a tftp server to program them into flash, and ... etc etc.

Here's a link to a page to configure a tftp server on your machine: ____

You can get our standard filesystem images here: ___

You can use this to program filesystem images you have created yourself, using the guides here ___ and here ___

General

There are some common steps involved with programming any type of SoM. First, you need to get an IP address for your SoM by doing...

Then, you need to set the IP address of the tftp server like so...

If you want to see the configuration of your bootloader, these commands will show you...

The bootloader has help built in. Do these things to learn more...

NOTE: If you want to put this information in a/the general uBoot page and link to it, that works too. But make sure they know they need to perform those steps.


Full Examples


Show some examples of performing every step, from start to boot. Our most common products would be best to use for this, so the 9g45 and the 9G20, I believe, would be the best ones to show.

This would also be a good place to note that they may have to change their video settings for their board, or set other kernel commandline arguments. You can link them to documentation for the kernel for this. The video settings information would be good to have in the quick reference section below, though. A quick reference by carrier type section, for our standard carriers, would be a good place for this. Also, anything else that you can think of that might be specific to a carrier should be there. Alternatively, maybe we should have a different page for this. That way, we could share it across different pages for different image types. If you choose that route, then the page will need to be "bragged about" here, so that people will be sure to look at the page rather than e-mailing us, "my screen doesn't work." You will probably also want to figure out a better formatting than the quick bit I added here.


Quick Reference

by SoM Type

Don't forget the SOM-3517

SoM-9260M

U-Boot> tftp 0x20000000 som-9260m-rootfs.jffs2
U-Boot> protect off all
U-Boot> erase 0x10400000 0x11ffffff
U-Boot> cp.b 0x20000000 0x10400000 ${filesize}

SoM-9G20M

U-Boot> tftp 0x20000000 som-9g20m-rootfs.jffs2
U-Boot> nand erase
U-Boot> nand write.jffs2 0x20000000 0x0 ${filesize}

SoM-9G45M

U-Boot> tftp 0x74000000 som-9g45m-rootfs.jffs2
U-Boot> nand erase
U-Boot> nand write.jffs2 0x74000000 0x0 ${filesize}

SoM-9M10M

U-Boot> tftp 0x74000000 som-9m10m-rootfs.jffs2
U-Boot> nand erase
U-Boot> nand write.jffs2 0x74000000 0x0 ${filesize}

SoM-9307M

Redboot> fis unlock -f 0x60000000 -l 0x1fdffff
Redboot> load -r -v -b 0x300000 -h 10.0.2.60 som-9307m-rootfs.jffs2
Redboot> fis create -b 0x300000 -l 0x1c00000 jffs2

IPAC-9302

Redboot> fis unlock -f 0x60000000 -l 0x1fdffff
Redboot> load -r -v -b 0x300000 -h 10.0.2.60 ipac-9302-rootfs.jffs2
Redboot> fis create -b 0x300000 -l 0x1c00000 jffs2