Recent Posts

Pages: 1 ... 8 9 [10]
91
Deutsch / Re: openssl Problme
« Last post by rgmhtt on November 29, 2017, 04:24:35 pm »
Another option is to get your certificate from:

https://letsencrypt.org/

92
General Discussion / Re: CubieTruck Plus boot from SATA hard drive
« Last post by aragorn2101 on November 27, 2017, 06:27:26 am »
Ok, I see.

Yeah, I'm also going to buy the smallest possible microSD and move the uBoot there.

Many thanks for your help. Now we understand better how booting works on these devices.
I'll certainly try the uboot-tools.

Best regards.

;D
94
General Discussion / Re: CubieTruck Plus boot from SATA hard drive
« Last post by rgmhtt on November 27, 2017, 06:13:43 am »
It is much more than a MBR of 512 bytes,  The uboot is equivalent to an i386 BIOS.  The Cubietruck one I have here  for 10/26/17 is 545.6KB.  So your dd is much larger than moving a MBR.

I use the cheapest, smallest mSD card I can get for this purpose, and just dd the more.

I just uploaded the 10/26/17 Cubietruck uboot:

http://www.htt-consult.com/~rgm/cubieboard/u-boot-CT-10-2016-sunxi-with-spl.bin

You can try that in place of the Cubie2 I have in my guide.

BTW, on Fedora/Centos, you install uboot-tools and there there is a directory (somewhere) with ALL the current various board uboots...
95
You have this rom that works perfectly. Luckily someone made backup.

I have to agree, this board has the worst community that I ever see in this type of projects.
96
General Discussion / Re: CubieTruck Plus boot from SATA hard drive
« Last post by aragorn2101 on November 27, 2017, 03:31:19 am »
Thank you so much, rgmhtt.

It worked. I actually had a small misunderstanding from your first reply. I made the bootable microSD and transfered the root filesystem to a SATA drive. But I deleted only the root filesystem partition from the microSD and the partition mmcblk1p1 was still there (with the uImage). That's why the kernel panic: it was looking for the root filesystem on the microSD itself.

That link you posted did the trick. Now I understand. The "MBR" of the microSD does the work. So, I put the Linaro image on the microSD again and opened it with fdisk, and deleted all partitions, after transfering contents to SATA drive. It booted and used the SATA drive. Great.

Just one last question out of curiosity: if I have to transfer that uBoot to another microSD, can I use dd and read the first 512 bytes like I would do with a MBR hard disk?
97
General Discussion / Re: installing ubuntu to cubietruck plus NAND or SD card
« Last post by jatink on November 27, 2017, 12:15:32 am »
Thank you! very nice, clear and helpful post. keep posting more articles on DevOps Training
Thanks
98
Deutsch / Re: openssl Problme
« Last post by harvey186 on November 26, 2017, 09:32:50 am »
thx, I will try
99
General Discussion / Re: CubieTruck Plus boot from SATA hard drive
« Last post by rgmhtt on November 26, 2017, 08:56:53 am »
Another thought.

Your distro may be using the original Cubie uboot, not the independent sunxi uboot.  You would know this if your WiFi and Bluetooth work.  These were never 'cracked' by the open community.  The original uboot does not know how to switch to the sata, and a kernel that works with the original uboot would not know how to interact with the open sunxi uboot.  You would have to check the sunxi uboot site for Linaro support, or the Linaro web site.

100
General Discussion / Re: CubieTruck Plus boot from SATA hard drive
« Last post by rgmhtt on November 26, 2017, 08:23:45 am »
Again, I use only Fedora and Centos.  In fact I am one of the armv7hl testers for these distros.

There are clear instructions on the Fedora arm site and Centos about this.  Plus I have it on my website:

http://medon.htt-consult.com/Centos7-armv7.html

I currently do not have a separate CubieTruck uboot on my site, but I can put one there for you.  When you boot up, what uboot version is reported to the console?

Allwinner A20 uboot for some time has 'know' that if there are no partitions on the mSD card, to look for sata or usb (though I have not tried usb for a long time).  I don't think they goot the nrand partitions working for booting...

It is all in the uboot.  see what my console looks like booting a Cubie2:


U-Boot SPL 2016.09.01 (Oct 19 2016 - 13:46:44)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1


U-Boot 2016.09.01 (Oct 19 2016 - 13:46:44 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Cubietech Cubieboard2
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
SCSI:  Target spinup took 0 ms.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c50000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
Hit any key to stop autoboot:  2  1  0
switch to partitions #0, OK
mmc0 is current device
** Invalid partition 1 **
scanning bus for devices...
  Device 0: (0:0) Vendor: ATA Prod.: WDC WD3200BPVT-8 Rev: 01.0
            Type: Hard Disk
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
Found 1 device(s).

Device 0: (0:0) Vendor: ATA Prod.: WDC WD3200BPVT-8 Rev: 01.0
            Type: Hard Disk
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
... is now current device
Scanning scsi 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf

Pages: 1 ... 8 9 [10]