主题 : 分享tiny4412,emmc烧录u-boot, 支持fastboot模式烧写emmc 复制链接 | 浏览器收藏 | 打印
级别: 新手上路
UID: 87100
精华: 0
发帖: 12
金钱: 60 两
威望: 12 点
贡献值: 0 点
综合积分: 24 分
注册时间: 2013-01-30
最后登录: 2014-07-21
10楼  发表于: 2014-07-12 23:55
按照你说的改了,从SD启动之后,emmc认成了mmc 0,但是用fastboot烧写之后,选择emmc启动,重新上电,感觉还是没擦掉superboot,明天看看怎么回事。

Hit any key to stop autoboot:  0
TINY4412 # mmcinfo 0
Device: S5P_MSHC4
Manufacturer ID: 15
OEM: 100
Name: M4G1Y
Tran Speed: 0
Rd Block Len: 512
MMC version 4.0
High Capacity: Yes
Size: 3728MB (block: 7634944)
Bus Width: 8-bit
Boot Partition Size: 2048 KB
TINY4412 # mmcinfo 1
Device: S3C_HSMMC2
Manufacturer ID: 2
OEM: 544d
Name: SD16G
Tran Speed: 0
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Size: 15296MB (block: 31326208)
Bus Width: 4-bit
Boot Partition Size: 0 KB
TINY4412 # fdisk -c 0 320 2057 520
Count: 10000
fdisk is completed

partion #    size(MB)     block start #    block count    partition_Id
   1           695          6070812         1424478          0x0C
   2           320           134244          656304          0x83
   3          2057           790548         4213770          0x83
   4           520          5004318         1066494          0x83
TINY4412 # fatformat mmc 0:1
Start format MMC&d partition&d ...
Partition1: Start Address(0x5ca21c), Size(0x15bc5e)
size checking ...
Under 8G
write FAT info: 32
Fat size : 0x56f
Erase FAT region..................
Partition1 format complete.
TINY4412 # fastboot
[Partition table on MoviNAND]
ptn 0 name='fwbl1' start=0x1000A len=N/A (use hard-coded info. (cmd: movi))
ptn 1 name='bl2' start=N/A len=N/A (use hard-coded info. (cmd: movi))
ptn 2 name='bootloader' start=N/A len=N/A (use hard-coded info. (cmd: movi))
ptn 3 name='tzsw' start=N/A len=N/A (use hard-coded info. (cmd: movi))
ptn 4 name='kernel' start=N/A len=N/A (use hard-coded info. (cmd: movi))
ptn 5 name='ramdisk' start=N/A len=0x6800(~27262976KB) (use hard-coded info. (cmd: movi))
ptn 6 name='system' start=0x1000A len=0x501D8(~336027648KB)
ptn 7 name='userdata' start=0x1000A len=0x202605(~-2137517056KB)
ptn 8 name='cache' start=0x1000A len=0x822FF(~546044928KB)
ptn 9 name='fat' start=0x1000A len=0xADE2F(~729332736KB)
OTG cable Connected!
Received 27 bytes: getvar:partition-type:fwbl1
Received 24 bytes: getvar:max-download-size
Received 17 bytes: download:00002000
Starting download of 8192 bytes

downloading of 8192 bytes finished
Received 11 bytes: flash:fwbl1
flashing 'fwbl1'
writing FWBL1 ..device 0 Start 1, Count 16
MMC write: dev # 0, block # 1, count 16 ... 16 blocks written: OK
completed
partition 'fwbl1' flashed
Received 25 bytes: getvar:partition-type:bl2
Received 24 bytes: getvar:max-download-size
Received 17 bytes: download:00003800
Starting download of 14336 bytes

downloading of 14336 bytes finished
Received 9 bytes: flash:bl2
flashing 'bl2'
writing BL2 ..device 0 Start 17, Count 32
MMC write: dev # 0, block # 17, count 32 ... 32 blocks written: OK
completed
partition 'bl2' flashed
Received 32 bytes: getvar:partition-type:bootloader
Received 24 bytes: getvar:max-download-size
Received 17 bytes: download:00048224
Starting download of 295460 bytes
Received 36 bytes:

downloading of 295460 bytes finished
Received 16 bytes: flash:bootloader
flashing 'bootloader'
writing bootloader..device 0 Start 49, Count 656
MMC write: dev # 0, block # 49, count 656 ... 656 blocks written: OK
completed
partition 'bootloader' flashed
Received 26 bytes: getvar:partition-type:tzsw
Received 24 bytes: getvar:max-download-size
Received 17 bytes: download:00017000
Starting download of 94208 bytes

downloading of 94208 bytes finished
Received 10 bytes: flash:tzsw
flashing 'tzsw'
writing 0 TrustZone S/W.. Start 705, Count 320
MMC write: dev # 0, block # 705, count 320 ... 320 blocks written: OK
completed
partition 'tzsw' flashed
Received 28 bytes: getvar:partition-type:kernel
Received 24 bytes: getvar:max-download-size
Received 17 bytes: download:00431090
Starting download of 4395152 bytes
....
省略后面kernel root的烧写log。

最后选择emmc启动,感觉superboot没有擦掉,其他的擦掉了。

Superboot-4412 V1.6(20140317) by FriendlyARM

Booting from eMMC
boot error, Kernel/RAM-disk not recognized
级别: 新手上路
UID: 105548
精华: 0
发帖: 12
金钱: 60 两
威望: 12 点
贡献值: 0 点
综合积分: 24 分
注册时间: 2014-06-27
最后登录: 2019-01-03
11楼  发表于: 2014-07-13 09:33
烧一下ramdisk看看
级别: 新手上路
UID: 105548
精华: 0
发帖: 12
金钱: 60 两
威望: 12 点
贡献值: 0 点
综合积分: 24 分
注册时间: 2014-06-27
最后登录: 2019-01-03
12楼  发表于: 2014-07-13 09:35
按任意键能进uboot终端吗
级别: 新手上路
UID: 87100
精华: 0
发帖: 12
金钱: 60 两
威望: 12 点
贡献值: 0 点
综合积分: 24 分
注册时间: 2013-01-30
最后登录: 2014-07-21
13楼  发表于: 2014-07-13 13:13
我是整个都烧写了
fastboot flash fwbl1 E4412_N.bl1.bin
fastboot flash bl2 bl2.bin
fastboot flash bootloader u-boot.bin
fastboot flash tzsw E4412_tzsw.bin
fastboot flash kernel zImage
fastboot -w
fastboot flash ramdisk ramdisk-u.img
fastboot flash system system.img
pause
fastboot reboot
烧完之后从emmc启动,按任意键不能进入uboot终端,感觉uboot没有烧进去。
级别: 新手上路
UID: 87100
精华: 0
发帖: 12
金钱: 60 两
威望: 12 点
贡献值: 0 点
综合积分: 24 分
注册时间: 2013-01-30
最后登录: 2014-07-21
14楼  发表于: 2014-07-19 12:36
楼主,请教一个问题:
从原理图上看4片256MB的DDR3都接在了DMC0上,那地址空间应该是0x4000_0000 ~ 0x7FFF_FFFF,但是大家有没有注意到\board\samsung\tiny4412\config.mk中CONFIG_SYS_TEXT_BASE = 0xc3e00000,最后u-boot.map也是以0xc3e00000开始的,这是怎么回事?
而且我把CONFIG_SYS_TEXT_BASE = 0xc3e00000改成其他的都不行。
[ 此帖被fpgafans在2014-07-19 12:47重新编辑 ]
级别: 新手上路
UID: 87100
精华: 0
发帖: 12
金钱: 60 两
威望: 12 点
贡献值: 0 点
综合积分: 24 分
注册时间: 2013-01-30
最后登录: 2014-07-21
15楼  发表于: 2014-07-20 16:38
引用第14楼fpgafans于2014-07-19 12:36发表的  :
楼主,请教一个问题:
从原理图上看4片256MB的DDR3都接在了DMC0上,那地址空间应该是0x4000_0000 ~ 0x7FFF_FFFF,但是大家有没有注意到\board\samsung\tiny4412\config.mk中CONFIG_SYS_TEXT_BASE = 0xc3e00000,最后u-boot.map也是以0xc3e00000开始的,这是怎么回事?
而且我把CONFIG_SYS_TEXT_BASE = 0xc3e00000改成其他的都不行。

这个找到原因了,是因为开了mmu的原因,实施上0x4000_0000 ~ 0x5000_0000被映射到了0xc000_0000 ~ 0xd000_0000上去。
*無鈳取玳
级别: 论坛版主
UID: 27
精华: 12
发帖: 5398
金钱: 40120 两
威望: 17929 点
贡献值: 71 点
综合积分: 11036 分
注册时间: 2008-01-16
最后登录: 2014-11-22
16楼  发表于: 2014-07-20 22:20
支持开源精神,干得好!
"If you have an apple and I have an apple and we exchange apples, then you and I will
still each have one apple. But if you have an idea and I have an idea and we exchange
these ideas, then each of us will have two ideas."
级别: 新手上路
UID: 95812
精华: 0
发帖: 45
金钱: 225 两
威望: 45 点
贡献值: 0 点
综合积分: 90 分
注册时间: 2013-08-26
最后登录: 2019-03-08
17楼  发表于: 2014-09-11 17:58
楼主,我照着你的方法做了可以引导Android系统正常启动,但是我引导Linux系统的话就出现问题无法正常启动,请教下引导Linux和Android有什么区别
级别: 新手上路
UID: 95812
精华: 0
发帖: 45
金钱: 225 两
威望: 45 点
贡献值: 0 点
综合积分: 90 分
注册时间: 2013-08-26
最后登录: 2019-03-08
18楼  发表于: 2014-09-13 09:47

 回 楼主(ahai518) 的帖子

想问你前面的4个分区主要是什么用处和后面的fastboot出现的kernel  system...等分区有什么区别?
级别: 新手上路
UID: 108634
精华: 0
发帖: 7
金钱: 40 两
威望: 8 点
贡献值: 0 点
综合积分: 14 分
注册时间: 2014-10-01
最后登录: 2014-10-11
19楼  发表于: 2014-10-01 08:18
楼主问一下,我这个启动的时候会出现类似以下的错误信息:
求救,谢谢!

<4>rtl8192cu: Unknown symbol ieee80211_frequency_to_channel (err 0)
[    6.900000] rtl8192cu: Unknown symbol ieee80211_frequency_to_channel (err 0)
<4>rtl8192cu: Unknown symbol wiphy_free (err 0)
[    6.915000] rtl8192cu: Unknown symbol wiphy_free (err 0)
init: untracked pid 213 exited
[    6.955000] init: untracked pid 213 exited
init: untracked pid 106 exited
[    7.055000] init: untracked pid 106 exited
init: untracked pid 283 exited
[    7.055000] init: untracked pid 283 exited
init: untracked pid 300 exited
[    7.065000] init: untracked pid 300 exited
init: untracked pid 303 exited
[   11.470000] init: untracked pid 303 exited
init: untracked pid 535 exited
[   11.475000] init: untracked pid 535 exited
init: untracked pid 524 exited
[   11.480000] init: untracked pid 524 exited
init: untracked pid 522 exited
[   11.525000] init: untracked pid 522 exited
init: untracked pid 537 exited
[   11.535000] init: untracked pid 537 exited
init: untracked pid 536 exited
[   11.620000] init: untracked pid 536 exited
init: untracked pid 538 exited
[   11.625000] init: untracked pid 538 exited
init: untracked pid 598 exited
[   11.630000] init: untracked p