On Thu, Aug 06, 2015 at 12:53:10PM +0200, Average Joe wrote: > Recently I bought a Cubieboard 2 with hope that I'll be able to run OpenBSD > on it. The armv7 page says the board is supported and all the devices I hoped > to use are listed as supported. > Installation instructions seemed dead simple. However, I am > struggling for two days already trying to boot this thing up and have gotten > nowhere. > > I want to install the snapshot version of OpenBSD, so according > to INSTALL.armv7 I did: > # dd if=miniroot-cubie-58.fs of=/dev/rsd3c bs=1m > > After inserting the uSD card into the board and powering it up the following > appears on the serial console: > > HELLO! BOOT0 is starting! > boot0 version : 3.0.0 > dram size =1024 > sum=0x01be1e3a > src_sum=0x01be1e3a > Ready to disable icache. > Jump to secend Boot. > [ 0.132] > > U-Boot 2011.09-rc1-00003-ge89ab14-dirty (Jan 03 2014 - 12:57:33) > Allwinner Technology > > [ 0.142]version: 1.1.0 > [ 0.145]pmbus: ready > [ 0.249]PMU: AXP209 > [ 0.252]PMU: AXP20x found > [ 0.255]PMU: bat ratio = 100 > [ 0.258]after set, dcdc2 =1400mv > [ 0.262]PMU: dcdc2 1400 > [ 0.264]PMU: pll1 912 Mhz > boot_clock = 912 > dcdc2_vol = 1400 > [ 0.272]after set, dcdc2 =1400mv > dcdc3_vol = 1250 > ldo2_vol = 3000 > ldo3_vol = 2800 > ldo4_vol = 2800 > power_start = 0 > storage_type = -1 > usb_recovery = 1 > find power_sply to end > fel key old mode > run key detect > no key found > no key input > dram_para_set start > dram_para_set end > [ 0.308]DRAM: 1 GiB > relocation Offset is: 35b23000 > donn't initialize ther user_gpio (main_key:boot_init_gpio) > DRV_DISP_Init: opened > [ 0.522]boot_disp.output_type=4 > [ 0.526]boot_disp.output_mode=4 > [ 0.529]boot_disp.auto_hpd=1 > workmode = 0 > [ 1.833]NAND: NAND_UbootInit > NB1 : enter NAND_LogicInit > nand : get id_number_ctl from script, 3 > not burn nand partition table! > NB1 : nand_info_init fail > [ 5.447]nand init fail > set to recovery > try sprite_led_gpio config > sprite_led_gpio start > sunxi sprite begin > screen_width = 800 > screen_height = 480 > bar x1: 200 y1: 200 > bar x2: 600 y2: 280 > read mbr failed > sprite update error: no data part found > read mbr failed > sprite update error: read image start error > sprite update error: current card sprite failed > now hold the machine > fail to find part named env > Using default environment > > In: serial > Out: serial > Err: serial > --------fastboot partitions-------- > mbr not exist > base bootcmd=run setargs_nand boot_normal > bootcmd set setargs_nand > key 0 > recovery key high 6, low 4 > cant find fstbt value > no misc partition is found > to be run cmd=run setargs_nand boot_normal > the part isn't exist > WORK_MODE_BOOT > WORK_MODE_BOOT > [ 5.541]Hit any key to stop autoboot: 0 > cant find part named boot > sunxi_flash - sunxi_flash sub-system > > Usage: > sunxi_flash read command parmeters : > parmeters 0 : addr to load(hex only) > parmeters 1 : the name of the part to be load > [parmeters 2] : the number of bytes to be load(hex only) > if [parmeters 2] not exist, the number of bytes to be load is the size > of the part indecated on partemeter 1 > boota: bad boot image magic, maybe not a boot.img? > sunxi# > > Apart from noticing truly horrible English and typing skills I do > not see where things went wrong. > > The only thing that tickles me is that INSTALL.armv7 document says > that miniroot-cubie-58.fs in the release folder is for Cubieboard 1 > version which, I guess, may cause some problems even though > Cubie 1 and 2 are very similar machines (according to official > Cubieboard website). > If this is the case and I have the wrong miniroot filesystem, how do > I get/make the correct one for Cubieboard 2? > If not, what else might cause the system not to boot? > > P.S. This is my first time posting to a mailing list of any kind, > please feel free to make suggestions on how I can do it > better the next time. > > Kind regards, > Viktor
Because these boards use u-boot life is much more painful than it otherwise would be. The miniroots have board specific u-boot firmware included in them because most boards need the firmware to be on removeable media. If you can manage to tftp boot bsd.rd.SUNXI.umg you'll avoid some of the madness. It seems the allwinner provided u-boot doesn't set up the atags structure and uses it's own way of booting so you'll likely need to use a version based on the main u-boot repository. It should be possible to dd the miniroot-cubie-58.fs to an sd card then dd if=u-boot-sunxi-with-spl.bin of=/dev/rsd3c bs=1024 seek=8 over the top assuming sd3 is the sd card to replace the version of u-boot included in the miniroot. An untested attempt to do this with a cubieboard2 u-boot 2015.07 image can be found here: http://jsg.id.au/openbsd/miniroot-cubie2-58.fs cubieboard2 u-boot 2015.07 file http://jsg.id.au/openbsd/u-boot-sunxi-with-spl.bin
