Firefly Open Source Community

   Login   |   Register   |
New_Topic
Print Previous Topic Next Topic

[Hardware] Mass-production of EMMC images

27

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
27

【Hardware】 Mass-production of EMMC images

Posted at 3/26/2019 16:16:00      View:5440 | Replies:5        Print      Only Author   [Copy Link] 1#
Hi

I have a project in which I need to flash several EMMC images (16GB) for the ROC-RK3328-CC. I am running Ubutun 16.04 and I want to make an .img file which all my custom tools installed, and afterwards flash several EMMC's with this image. And so far I have not found any way of doing this.

So far I have only had succes flashing the raw Ubuntu 16.04 linked inside the documentation. I have not been able to flash my custom version. Can anyone help me do this?
I have tried using both the AndroidTool for windows and rkdeveloptool to flash my custom image to a blank EMMC. The flash is succesfull both the board wont boot  afterwards.

I hope someone can help me as this is a major issue for my project.
Reply

Use props Report

1396

Credits

0

Prestige

0

Contribution

vip

Rank: 6Rank: 6

Credits
1396
Posted at 3/27/2019 16:07:02        Only Author  2#
Hi @bga,  how do you pack your custom image?

Did you follow the guide at:
http://wiki.t-firefly.com/ROC-RK ... mpile_firmware.html  ?
Reply

Use props Report

27

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
27
Posted at 3/29/2019 16:09:39        Only Author  3#
hi @penguin

Yes I am following excatly that guide. And using the rkdeveloptool to flash the EMMC. For the Linux root filesystem I am using an .img file I created from an SD card with linux 16.04 previously plugged into a RK3328-cc. My idea was to install the basic 16.04, power up the firefly and install all my custom applications. and then copy the content of this SD card into many EMMC cards. Is this idea wrong? Might this be my issue?
Reply

Use props Report

1396

Credits

0

Prestige

0

Contribution

vip

Rank: 6Rank: 6

Credits
1396
Posted at 4/1/2019 10:59:22        Only Author  4#
hi @bga
You need a serial-to-usb adapter hooked to the uart debug port to see all the u-boot and kernel boot messages.
Without the log, I cannot tell what happened.
Reply

Use props Report

27

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
27
Posted at 4/11/2019 15:40:34        Only Author  5#
Hi @penguin

I finally got the UART debugger, and I get the following message when booting the device:


DDR version 1.06 20170424
In
DDR4
786MHz
Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
ddrconfig:14
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, 178
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=14910MB
FwPartOffset=2000 , 2000
SdmmcInit=0 2
StorageInit ok = 21135
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xa539c
RunBL31 0x10000
NOTICE:  BL31: v1.3(debug):f947c7e
NOTICE:  BL31: Built : 09:28:45, May 31 2017
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initialized
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE init                                                                                                                                                                                                                                             ialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

U-Boot 2017.09-gc58a816 (Mar 29 2019 - 08:35:09 +0100)

Model: Firefly ROC-RK3328-CC
DRAM:  2 GiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
Card did not respond to voltage select!
mmc_init: -95, time 10
*** Warning - No block device, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Firefly ROC-RK3328-CC
misc_init_r
cpuid=55524b50303130313400000000031b14
serial=3cf0f5335646df8
roc-rk3328-cc late init ...
Net:   No ethernet found.
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
GPT: last_usable_lba incorrect: 1D687DE > 1d1f000
part_get_info_efi: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0xA6B619CC7822D86 != 0x545241502                                                                                                                                                                                                                                             0494645
Reply

Use props Report

1396

Credits

0

Prestige

0

Contribution

vip

Rank: 6Rank: 6

Credits
1396
Posted at 4/16/2019 16:42:39        Only Author  6#
hmm, from the last lines of your log:

GPT: last_usable_lbaing incorrect: 1D687DE > 1d1f000
part_get_info_efi: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0xA6B619CC7822D86 != 0x545241502                  


It seems that the GPT partition table is wrong.
Could you post all the commands ( creating the firmware and flashing) , and the result?
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list