4412 Development Board TF card making Uboot

Transferred from: http://topeetboard.com

Hardware: Ttm itop 4412 Elite & TF Card

Software: System comes with terminal can

First of all, we should be aware that the TF/SD card can be regarded as a completely blank "white paper", the reason for partitioning, partition format is only in this "white paper" some specific location to write some data to indicate the partition, partition format.

Second, we should also be aware that in the TF/SD boot mode, Exynos 44,121 power on, the internal irom from the tf/sd of the 1th block (No. 512 byte start) to read 8KB of data to the internal Iram, and then from the internal Iram 0 address to start running.

The principle is clear, then first of all need to tf/sd low-level format- all block Write 0x00 .

1, connect TF/SD card, open terminal

Use the ls/dev/sd* command to view all the disks connected to your computer.

Question: Why not use the DF command here?

The reason is that if your TF/SD card has only one partition but the partition is corrupted, or there are multiple partitions but there is no identifiable partition, then the DF command is unable to see the TF/SD card, so it is the ultimate solution to list the devices directly at the beginning of all SD under Dev.

(1) Assume that your TF/SD card has only one partition, regardless of whether the partition is damaged or not, the phenomenon should be something like this:

Before inserting the TF/SD card:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/7F/F5/wKioL1cy352yUB6aAABQh0InNPM653.jpg "title=" Picture 1.jpg "alt=" wkiol1cy352yub6aaabqh0innpm653.jpg "/>

After inserting the TF/SD card:

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/7F/F7/wKiom1cy3sbBPvOUAABct1dmBME441.jpg "title=" Picture 2.jpg "alt=" wkiom1cy3sbbpvouaabct1dmbme441.jpg "/>

It is obvious that the/DEV/SDB is the object of the subsequent operation of this article.

(2) Assuming that your TF/SD card already has multiple partitions, whether or not these partitions are damaged, the behavior should be something like this:

Before inserting the TF/SD card:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/7F/F7/wKiom1cy3tGB-lOZAABYPAUdRWg089.jpg "title=" Picture 3.jpg "alt=" wkiom1cy3tgb-lozaabypaudrwg089.jpg "/>

After inserting the TF/SD card:

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/7F/F7/wKiom1cy3tqhZLAzAABmQODGfxI358.jpg "title=" Picture 4.jpg "alt=" wkiom1cy3tqhzlazaabmqodgfxi358.jpg "/>

There are 5 more devices, but we will still use/DEV/SDB as an object for subsequent operations in this article.

Note: I here is/dev/sdb, but there may be/dev/sdc and other symbols, must be based on the device name you actually appear to do the following, otherwise it may damage the system partition, it is very important, remember!!!

2. Use 16 binary mode to open TF card to view data (skip)

We use the Linux self-contained command hexdump to view the data in the TF/SD card:

The command is:

sudo hexdump-n 1048576/dev/sdb

Where-n 1048576 means that the first 1m=1024*1024=1048576 bytes of data are printed.

The results of the execution (partial) are as follows:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7F/F7/wKiom1cy3uPTFC4YAAHBpF2dpr8908.jpg "title=" Picture 5.jpg "alt=" wkiom1cy3uptfc4yaahbpf2dpr8908.jpg "/>

* Represents the content of 0x00, in order to save space pretending to omit.

3, empty the TF card forward 1MB data

Since 4412 of the uboot size is basically hundreds of KB in magnitude, the clear 1MB space is sufficient, note that the empty is not formatted, but to fill 0x00.

We use the system/dev under the zero device, clear 0 tf/sd card front 1MB.

The results of the implementation are as follows:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7F/F5/wKioL1cy38uQVYzzAABx7QaRyf4632.jpg "title=" Picture 6.jpg "alt=" wkiol1cy38uqvyzzaabx7qaryf4632.jpg "/>

The count=2000 here represents emptying 2000 blocks, and one block=512b,2000 is exactly 1MB.

Again hexdump view TF/SD card data, found:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M02/7F/F7/wKiom1cy3vXxsHSXAABR_GexNQA623.jpg "title=" Picture 7.jpg "alt=" wkiom1cy3vxxshsxaabr_gexnqa623.jpg "/>

The first 1MB space successfully cleared 0x00.

4. Burn Write Uboot startup file

Here, we are burning the files to be written as U-boot-itop-4412.bin this file.

Terminal Execution Command:

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M01/7F/F7/wKiom1cy3v3SjVNEAABq49zVkfU338.jpg "title=" Picture 8.jpg "alt=" wkiom1cy3v3sjvneaabq49zvkfu338.jpg "/>

If the input file address, as you u-boot-itop-4412.bin the actual address of this file, the of the output address, the actual device number of your TF/SD card is subject to.

Here, you can insert the TF/SD card into the Development Board to power up, in order to prove that we are burning, we do the following.

5, confirm burn write correct (can skip)

we need to make sure that from the first block of the TF/SD card, it is true that the U-boot-itop-4412.bin this file has been correctly burned, and the following is a comparison of the commands used Hexdump.

Here, in order to display the convenience, only print the first 5KB data, found that the bin file is correctly copied to the SD card at 512 bytes:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/7F/F5/wKioL1cy3-mi8pffAAaRbOgaRKc563.jpg "title=" Picture 9.jpg "alt=" wkiol1cy3-mi8pffaaarbogarkc563.jpg "/>

6, the TF card to the Development Board, dial switch select TF start, power up:

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/7F/F5/wKioL1cy3_bTmVj_AACJGzObR8A450.jpg "title=" Picture 10.jpg "alt=" wkiol1cy3_btmvj_aacjgzobr8a450.jpg "/>

Done.

4412 Development Board TF card making Uboot