Firefly Open Source Community

   Login   |   Register   |
New_Topic
Print Previous Topic Next Topic

Building boot-image for Firefly Reload

62

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
62

Building boot-image for Firefly Reload

Posted at 3/28/2018 22:11:52      View:5828 | Replies:8        Print      Only Author   [Copy Link] 1#
HI

I am trying to build a new boot-image for Firefly Reload board without success. I am using the mkbootimg-script, but i have now glue how to set up correct parameters. I have tried for example the following:
mkbootimg --kernel /rockchip-linux/kernel/arch/arm/boot/zImage --ramdisk initrd.img -o boot_v4.img.  It build a new file, but when I flashed it onto eMMC memory of the Filrefly Reload board into boot-partition, board does not boot up.

I have also used the following longer parameter settings for mkbootimg:

mkbootimg --base 60400000 --pagesize 16384 --ramdisk_offset 62000000 --second_offset 60f00000 --tags_offset 60088000 --kernel /rockchip-linux/kernel/arch/arm/boot/zImage --ramdisk ramdisk.cpio.gz --second /rockchip-linux/kernel/resource.img -o boot_v4.img

This script made on new boot_v4.img, but board does not boot up.  I have forced to step back and flash old boot_original.img into boot-partiton of the board. This boot up normally!

So my question is, how can I make a suitable boot-file for Firefly Reload board?

Reply

Use props Report

792

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
792
Posted at 3/29/2018 14:38:10        Only Author  2#
try to run (truncate -s "%4" initrd.img) first , and mkbootimg again
Reply

Use props Report

62

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
62
Posted at 3/30/2018 01:12:44        Only Author  3#
I build a new initrd.img and I truncate it with parameters -s %4.  Then I made a new boot_29.img using the mkbootimg-script. Then I flashed it on the eMMC memory of the Firefly Reload board.  What I noticed is that this boot image was much shorter in size than original boot_original.img, which is the only one, which works.  I cannot make a new bootable image for Firefly Reload.

My question is:

What are the exact steps in order to make new boot-image for Firefly Reload board?

Reply

Use props Report

792

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
792
Posted at 3/30/2018 09:49:16        Only Author  4#
Pentti12 Posted at 3/30/2018 01:12
I build a new initrd.img and I truncate it with parameters -s %4.  Then I made a new boot_29.img usi ...

mkbootimg --kernel $ZIMAGE --ramdisk $INITRD --second $LINUX_RESOURCE_IMG -o $LINUX_BOOT_IMG initrd-ubunturoot.rar (2.6 MB, Down times: 3)



try this


Reply

Use props Report

62

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
62
Posted at 4/1/2018 02:44:04        Only Author  5#
Hi

I tried both initrd-variants, my own build and initrd-ubunturoot.img, whichout success.  The serial console printout is attached (my own initrd.img build):

DDR Version 1.00 20141007
In
Channel a: DDR3 200MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Channel b: DDR3 200MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Memory OK
Memory OK
OUT


U-Boot 2014.10-RK3288-01 (Jan 21 2015 - 16:36:44)

CPU: rk3288
CPU's clock information:
    arm pll = 600000000HZ
    periph pll = 297000000HZ
    ddr pll = 200000000HZ
    codec pll = 384000000HZ
Board:  Rockchip platform Board
DRAM:  Found dram banks:1
Adding bank:0000000000000000(0000000080000000)
128 MiB
storage init OK!
Using default environment

GetParam
check parameter success
Unknow param: MACHINE_MODEL:rk3288!
Unknow param: MACHINE_ID:007!
Unknow param: MANUFACTURER:RK3288!
Unknow param: PWR_HLD: 0,0,A,0,1!
no adc node
light power led: bank-16777215 pin-255
can't find dts node for ricoh619
can't find dts node for act8846
can't find dts node for rk808
can't find dts node for rk818
Can't find dts node for fuel guage cw201x
SecureBootEn = 0, SecureBootLock = 0
empty serial no.
checkKey
vbus = 1
no fuel gauge found
no fuel gauge found
read logo_on switch from dts [0]
no fuel gauge found
failed to find part:misc
misc partition not found!
Hit any key to stop autoboot:  0
kernel   @ 0x02000000 (0x00785710)
ramdisk  @ 0x04bf0000 (0x002747dc)
Secure Boot state: 0
bootrk: do_bootm_linux...
   Loading Device Tree to 0481a000, end 0482b246 ... OK
Add bank:0000000000000000, 0000000080000000

Starting kernel ...

So I need more detailed instructions how to build working boot.img for Firefly Reload board!
Reply

Use props Report

62

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
62
Posted at 4/6/2018 15:19:47        Only Author  6#
The Firefly Reload Board does not enter to loading kernel.  It stops forever waiting to start kernel.  

What can I do to solve this issue?
Reply

Use props Report

792

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
792
Posted at 4/8/2018 09:12:40        Only Author  7#
Pentti12 Posted at 4/6/2018 15:19
The Firefly Reload Board does not enter to loading kernel.  It stops forever waiting to start kernel ...

flash the whole officail image and replace the linux-boot.img you complie.
Reply

Use props Report

62

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
62
Posted at 4/12/2018 01:09:10        Only Author  8#
Can you state exact steps for making new linux-boot.img?
Reply

Use props Report

792

Credits

10

Prestige

10

Contribution

advanced

Rank: 4

Credits
792
Posted at 4/13/2018 14:46:46        Only Author  9#
Pentti12 Posted at 4/12/2018 01:09
Can you state exact steps for making new linux-boot.img?

http://en.t-firefly.com/doc/product/info/253.html
take a look above , and the key step of the 4th post i do.
there is a attach file in the 4th post.
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