Re: switch the cubie miniroot to cubieboard2
- Original Message -
> si...@slackware.it [si...@slackware.it] wrote:
> > Speaking as a Cubieboard owner here ;-)
> > Would it be too much hassle to provide both images? (and a pony!)
> >
>
> It's fairly easy to take a miniroot image for a similar board, and
> adapt it to your board.
Thanks for the tutorial!
>
> Since both the Cubieboard and Cubieboard2 are Allwinner based,
> the miniroot's general structure does not change.
>
> 1. Install u-boot-2016.07p1 from ports/packages (packages if you don't
> want to wait all day)
>
> 2. Examine /usr/src/distrib/armv7/ramdisk/install.md and find
> a similar board (same or similar chipset).
>
> 3. Find the proper u-boot/dtb stuff in /usr/local/share/u-boot
>
> 4. Download the miniroot image for a board that has the same
> or similar chipset to your board
>
> 5. vnconfig vnd0 miniroot.fs
>
> 6. Install proper u-boot image to the miniroot image. The install.md
> file tells you how to copy the proper u-boot/dtb over. For instance,
> Cubieboard is Allwinner A10/A20, and my Lime is A20.
>
> install.md says:
>
> cubie)
> dd if=$_mdec/u-boot-sunxi-with-spl.bin of=${_disk}c \
> bs=1024 seek=8 >/dev/null 2>&1
>
> So, to get my Lime or Lime2 working, I do this:
>
> dd if=/usr/local/share/u-boot/A20-OLinuXino-Lime2/u-boot-sunxi-with-spl.bin
> of=/dev/rvnd0c bs=1024 seek=8
>
> (Note: Lime and lime2 bootloaders will appear to work on both boards,
> but if you don't use the right one, the Realtek ethernet PHY will
> not be properly initialized.)
>
> 7. vnconfig -u vnd0
>
> 8. Write miniroot.fs to your SD card
>
> You don't have to use vnd, but this is conceptually simpler
> and less error prone than trying to chop it up with dd.
>
> Chris
>
--
Marco Bonetti
Re: switch the cubie miniroot to cubieboard2
si...@slackware.it [si...@slackware.it] wrote:
> Speaking as a Cubieboard owner here ;-)
> Would it be too much hassle to provide both images? (and a pony!)
>
It's fairly easy to take a miniroot image for a similar board, and
adapt it to your board.
Since both the Cubieboard and Cubieboard2 are Allwinner based,
the miniroot's general structure does not change.
1. Install u-boot-2016.07p1 from ports/packages (packages if you don't
want to wait all day)
2. Examine /usr/src/distrib/armv7/ramdisk/install.md and find
a similar board (same or similar chipset).
3. Find the proper u-boot/dtb stuff in /usr/local/share/u-boot
4. Download the miniroot image for a board that has the same
or similar chipset to your board
5. vnconfig vnd0 miniroot.fs
6. Install proper u-boot image to the miniroot image. The install.md
file tells you how to copy the proper u-boot/dtb over. For instance,
Cubieboard is Allwinner A10/A20, and my Lime is A20.
install.md says:
cubie)
dd if=$_mdec/u-boot-sunxi-with-spl.bin of=${_disk}c \
bs=1024 seek=8 >/dev/null 2>&1
So, to get my Lime or Lime2 working, I do this:
dd if=/usr/local/share/u-boot/A20-OLinuXino-Lime2/u-boot-sunxi-with-spl.bin
of=/dev/rvnd0c bs=1024 seek=8
(Note: Lime and lime2 bootloaders will appear to work on both boards,
but if you don't use the right one, the Realtek ethernet PHY will
not be properly initialized.)
7. vnconfig -u vnd0
8. Write miniroot.fs to your SD card
You don't have to use vnd, but this is conceptually simpler
and less error prone than trying to chop it up with dd.
Chris
Re: switch the cubie miniroot to cubieboard2
Speaking as a Cubieboard owner here ;-) Would it be too much hassle to provide both images? (and a pony!) -- Marco Bonetti
Re: switch the cubie miniroot to cubieboard2
On Wed, Aug 31, 2016 at 07:26:27AM -0400, Ted Unangst wrote: > Jonathan Gray wrote: > > Now that the A20 works it likely makes sense to switch > > the cubie miniroot from the A10 based cubieboard1 to the A20 > > based cubieboard2 which more people seem to have? > > forgive the insane question, but does this imply that it > doesn't work on the a10 board? The u-boot and dtb images are in most cases only for a single board. So we either need to create board specific miniroots or require people to add u-boot and dtb before booting install images and after install. With u-boot being either at a raw offset or on the fat fs depending on the board type. This is because these machines don't have firmware in a rom in most cases, so we can't create a single install image. So yes, switching the miniroot to use the cubieboard2 specific u-boot will result in it not working on cubieboard1.
Re: switch the cubie miniroot to cubieboard2
Jonathan Gray wrote: > Now that the A20 works it likely makes sense to switch > the cubie miniroot from the A10 based cubieboard1 to the A20 > based cubieboard2 which more people seem to have? forgive the insane question, but does this imply that it doesn't work on the a10 board?
switch the cubie miniroot to cubieboard2
Now that the A20 works it likely makes sense to switch
the cubie miniroot from the A10 based cubieboard1 to the A20
based cubieboard2 which more people seem to have?
Index: distrib/armv7/miniroot/cubie/Makefile
===
RCS file: /cvs/src/distrib/armv7/miniroot/cubie/Makefile,v
retrieving revision 1.3
diff -u -p -r1.3 Makefile
--- distrib/armv7/miniroot/cubie/Makefile 5 Jun 2016 14:53:23 -
1.3
+++ distrib/armv7/miniroot/cubie/Makefile 31 Aug 2016 10:30:14 -
@@ -1,7 +1,7 @@
BOARD= cubie
PLATFORM=SUNXI
-UBOOT= Cubieboard
+UBOOT= Cubieboard2
DTBS=\
- sun4i-a10-cubieboard.dtb
+ sun7i-a20-cubieboard2.dtb
.include "${.CURDIR}/../Makefile.inc"
Index: distrib/armv7/ramdisk/install.md
===
RCS file: /cvs/src/distrib/armv7/ramdisk/install.md,v
retrieving revision 1.40
diff -u -p -r1.40 install.md
--- distrib/armv7/ramdisk/install.md5 Jun 2016 15:35:38 - 1.40
+++ distrib/armv7/ramdisk/install.md31 Aug 2016 10:30:14 -
@@ -46,7 +46,7 @@ md_installboot() {
*AM335x*) _plat=am335x;;
*'OMAP3 BeagleBoard'*) _plat=beagle;;
*OMAP4*)_plat=panda;;
- *Cubieboard*) _plat=cubie;;
+ *'Cubietech Cubieboard2'*) _plat=cubie;;
*Cubox-i*|*HummingBoard*) _plat=cubox;;
*Wandboard*)_plat=wandboard;;
*Nitrogen6*|*'SABRE Lite'*) _plat=nitrogen;;
Index: distrib/armv7/ramdisk/list
===
RCS file: /cvs/src/distrib/armv7/ramdisk/list,v
retrieving revision 1.21
diff -u -p -r1.21 list
--- distrib/armv7/ramdisk/list 5 Jun 2016 15:12:56 - 1.21
+++ distrib/armv7/ramdisk/list 31 Aug 2016 10:30:14 -
@@ -129,8 +129,8 @@ COPY/usr/local/share/dtb/arm/omap3-beag
COPY /usr/local/share/dtb/arm/omap3-beagle-xm.dtb
/usr/mdec/beagle/omap3-beagle-xm.dtb
COPY /usr/local/share/dtb/arm/omap3-beagle.dtb
/usr/mdec/beagle/omap3-beagle.dtb
-COPY /usr/local/share/u-boot/Cubieboard/u-boot-sunxi-with-spl.bin
/usr/mdec/cubie/u-boot-sunxi-with-spl.bin
-COPY /usr/local/share/dtb/arm/sun4i-a10-cubieboard.dtb
/usr/mdec/cubie/sun4i-a10-cubieboard.dtb
+COPY /usr/local/share/u-boot/Cubieboard2/u-boot-sunxi-with-spl.bin
/usr/mdec/cubie/u-boot-sunxi-with-spl.bin
+COPY /usr/local/share/dtb/arm/sun7i-a20-cubieboard2.dtb
/usr/mdec/cubie/sun7i-a20-cubieboard2.dtb
COPY /usr/local/share/u-boot/omap4_panda/MLO /usr/mdec/panda/MLO
COPY /usr/local/share/u-boot/omap4_panda/u-boot.img
/usr/mdec/panda/u-boot.img
Index: distrib/notes/armv7/contents
===
RCS file: /cvs/src/distrib/notes/armv7/contents,v
retrieving revision 1.10
diff -u -p -r1.10 contents
--- distrib/notes/armv7/contents30 Dec 2015 23:48:59 - 1.10
+++ distrib/notes/armv7/contents31 Aug 2016 10:30:14 -
@@ -11,7 +11,7 @@ TopPart
miniroot-cubie-{:--:}OSrev.fs
A miniroot filesystem to be used for
- installation; Cubieboard1 version.
+ installation; Cubieboard2 version.
miniroot-cubox-{:--:}OSrev.fs
A miniroot filesystem to be used for
