Jump to content

[Cubieboard2] [kernel 4.9.7-sunxi & uboot 2017.01-armbian] not possible to boot on SD


Jean-Marc

Recommended Posts

Hi,

With current cubieboard2 image on SD class 10,

local@solo:~$ time sudo dd if=/tmp/Armbian_5.25_Cubieboard2_Debian_jessie_next_4.9.7.img of=/dev/sdb bs=4k
326656+0 enregistrements lus
326656+0 enregistrements écrits
1337982976 octets (1,3 GB) copiés, 317,544 s, 4,2 MB/s

 

 

not possible to boot on cubieboard2.

Please find following log

 

=> =>
U-Boot SPL 2017.01-armbian (Feb 02 2017 - 02:16:44)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2017.01-armbian (Feb 02 2017 - 02:16:44 +0100) 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:  SATA link 0 timeout.
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
Hit any key to stop autoboot:  0
6944 bytes read in 170 ms (39.1 KiB/s)
scanning bus for devices...
Found 0 device(s).

Device 0: not available
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... 2 USB Device(s) found

USB device 0: unknown device
ethernet@01c50000 Waiting for PHY auto negotiation to complete.. done
Speed: 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.15.2 (4 ms)
*** Warning: no boot file name; using 'C0A80F02.img'
Using ethernet@01c50000 device
TFTP from server 0.0.0.0; our IP address is 192.168.15.2
Filename 'C0A80F02.img'.
Load address: 0x42000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-02-c5-06-42-04-4b
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80F02
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80F0
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80F
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Speed: 100, full duplex
*** ERROR: `serverip' not set
Config file not found
Speed: 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.15.2 (3 ms)
Using ethernet@01c50000 device
TFTP from server 0.0.0.0; our IP address is 192.168.15.2
Filename 'boot.scr.uimg'.
Load address: 0x43100000
Loading: *
CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.7 | VT102 | Déconnecté |

 

 

 

 

 

Thanks in advance for your help

Link to comment
Share on other sites

4 hours ago, Honor said:

Same problem, any  fix? I have a banana pro!

 

How much of this document have you read and took into consideration?

https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card

If you can't boot anything, than other rear HW issues are also possible - broken SD card slot for example.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines