Looks like u-boot is having trouble then. I’ll look into that later (at work now).
What is the uboot exactly? Is it the bootloader? If so, what does the uboot button? Thank you for all your help
-baskwo
u-boot is the bootloader that loads the Linux kernel and passes possibly required parameters onto it. It can also preload some other required data to the RAM of the system before loading/booting the Linux kernel. I am not quite sure what the uboot button does. but I have a feeling it puts the processor into a specific state. Possibly for loading software through the USB interface before actually booting.
As for your problem, I’m beginning to have some suspicions about win32 Disk imager. Another user seems might have made his SD cards unusable for booting the BPi with it. The “proper” way to put one of these images onto an SD cars is to use “dd” in linux (or any UNIX-like system), using that to write the data directly onto the main partition of your SD card.
This is the way I copied the shrunk image to my SD card and it works just fine for me…
Ohh I see 
I only have to do : dd if=file of=/dev… ? No other parameters?
To speed up the process it’s handy to set the transfer block size to 1 MB by adding the parameter bs=1M to the dd command line. But yes, that’s all you need to do.
So I wrote my sd card with the dd command without the bs parameter and it does the same. shutting down after like 10 seconds. There is the commands I did with output : https://gyazo.com/43330e0f0a19b46eb29b9e440c369bd0
If sdb is your SD card, that should be quite right.
Do you think I should try to reinstall u-boot on my sd card? I could follow the arch guideline for that.
You can try it, but I cannot guarantee you success. I’d recommend you get a USB TTL serial converter to see what’s happening during the u-boot phase.
Alright, thank you I’ll buy one as fast as I can for now I’ll try to reinstall u-boot on my sd-card or try an other img! Thank you for your help I’ll keep you informed!
So I have a USB TTL serial converter. And I’m using Putty to read it on Windows. I’m getting some infos but it is really weird : https://gyazo.com/405233a2c101098c0a795519e3a1cda8 I also tried on linux with screen and I got this : https://gyazo.com/56c6cba981013253b97f131b72b7939a So I wonder if it’s the right program to do so and I’f I’m use it correctly.
Looks like you might have the wrong serial port settings. The settings I use are: 115200 baud, 8 bit data, no parity, 1 stopbit (115200 8N1) Flow control: none
Does this output have any moment that it pauses? There is a point in the u-boot sequence where you can stop it from continuing. Here’s a snippet from the boot loader where I actually interrupted it (this is the actual shrunk image you’re trying as well): > WORK_MODE_BOOT > board_status_probe > [ 1.154]pre sys mode > sunxi_bmp_logo_display > [ 1.279][mmc]: blkcnt should not be 0 > [ 1.297]fetch script data boot_disp.output_disp fail > [ 1.302]screen_id =1, screen_width =1280, screen_height =720 > [ 1.308]frame buffer address 46400000 > [ 1.312]Hit any key to stop autoboot: 0
I tried with : screen /dev/ttyUSB0 115200,cs8,-parentb,-cstopb and it output the same thing.
It seems to have a little pause 2-3 seconds
Hmm, I tried the same and worked 100% fine for me. I don’t know how to help you any further without physical access to your system. The fact that you are getting output on the serial port (even though it’s garbled) tells me that it’s hooked up correctly. I hope someone else has some ideas for you.
Well if you want I can setup ssh access to my arch vm and we can talk on Discord or whatever so I can move the sd card if you want! (But I would understand if you don’t haha) By the way it might be my usb to ttl converter the problem because it my boss that gave me that and it’s an homemade usb to ttl. I have ordered one from internet supposed to arrive in 2 weeks.
I’m not going to give you remote support. I’m a professional embedded Linux developer, but this is just a hobby project. In the mean time you can see where the byte differences between your image file and SD card are using the “cmp” utility with something like: dd if=/dev/sdc bs=1M count=3856 | cmp -l 2016-05-14-dietpi-preview-bpi-m3-sd-emmc.img.new -
All good men I understand you 
I’ll try that this weekend because I have a huge week!
@NoKey Hey I have some news. I received my usb to ttl converter and now I can see easily what is outputting so it was my converter that was not good.
This is the output I have : http://pastebin.com/VRpeW3dD Can you help me figure out what is the problem?
Hmmmm. I’ve looked over the data several times now and from what I can see from it, it looks like sometimes you either miss characters or maybe there are two parrallel processes busy writing output. Take these 2 lines for example:
[ 3.829452] tialized 3.830686] Driver for 1-wire Dallas netw: HCI UART 2.2
The first line starts OK with the timestamp in between block braces [ 3.829452], but then we geta partial word: tialized. Clearly it should say either <some text> initialized or Initialized <some text> Then the second line starts with a partial timestamp: 3.830686]; where has the opening block brace gone to? Then it continues with Driver for 1-wire Dallas netw what should really say in full: Driver for 1-wire Dallas network protocol. (see BPI-M3-bsp/linux-sunxi/drivers/w1/w1.c line 1010). The line then finishes with : HCI UART 2.2 which comes from BPI-M3-bsp/linux-sunxi/drivers/bluetooth/hci_ldisc.c line 527, which is also partially gabled because that shoud say HCI UART driver ver 2.2 in full. This is just full of weirdness.
Your last readable timestamp seems to be [ 4.460111], so here’s what happens on my system roundabout then: [ 4.187227] sd init ok [ 4.200214] sunxi_i2c_do_xfer()945 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x38) [ 4.220203] sunxi_i2c_do_xfer()945 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x38) [ 4.240189] sunxi_i2c_do_xfer()945 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x38) [ 4.260195] sunxi_i2c_do_xfer()945 - [i2c0] incomplete xfer (status: 0x20, dev addr: 0x38) [ 4.309584] [mmc]: sdc2 set ios: clk 0Hz bm PP pm UP vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.562950] [mmc]: sdc1 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.580040] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.600845] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 52, RTO !! [ 4.601682] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 52, RTO !! [ 4.601704] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.604168] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.606055] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 8, RTO !! [ 4.606075] Try sdio [ 4.606890] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 5, RTO !! [ 4.607715] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 5, RTO !! [ 4.608540] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 5, RTO !! [ 4.609365] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 5, RTO !! [ 4.609385] *******************Try sd ******************* [ 4.610200] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 55, RTO !! [ 4.611028] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 55, RTO !! [ 4.611855] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 55, RTO !! [ 4.612683] [mmc]: *** sunxi_mci_dump_errinfo(L824): smc 2 err, cmd 55, RTO !! [ 4.612702] Try mmc [ 4.612710] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.613113] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.613196] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.613276] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.615741] [mmc]: sdc2 set ios: clk 400000Hz bm OD pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.671217] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.683170] [mmc]: sdc2 set ios: clk 400000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.683580] [mmc]: sdc2 set ios: clk 25000000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.683666] [mmc]: sdc2 set ios: clk 25000000Hz bm PP pm ON vdd 3.3V width 1 timing LEGACY(SDR12) dt B [ 4.683742] [mmc]: sdc2 set ios: clk 25000000Hz bm PP pm ON vdd 3.3V width 1 timing MMC-HS(SDR20) dt B [ 4.683791] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 1 timing MMC-HS(SDR20) dt B [ 4.683872] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 1 timing MMC-HS(SDR20) dt B [ 4.683948] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing MMC-HS(SDR20) dt B [ 4.684076] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing MMC-HS(SDR20) dt B [ 4.684146] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B [ 4.684197] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B [ 4.684264] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B [ 4.684337] mmc1: new high speed DDR MMC card at address 0001 [ 4.684728] mmcblk1: mmc1:0001 8WPD3R 7.28 GiB [ 4.684870] mmcblk1boot0: mmc1:0001 8WPD3R partition 1 4.00 MiB [ 4.685023] mmcblk1boot1: mmc1:0001 8WPD3R partition 2 4.00 MiB [ 4.686464] mmcblk1: p1 p2 p3 < p5 p6 p7 p8 p9 p10 p11 p12 p13 > [ 4.686509] mmcblk1: p1 size 10117120 extends beyond EOD, truncated [ 4.688792] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B [ 4.690911] mmcblk1boot1: unknown partition table [ 4.691503] [mmc]: sdc2 set ios: clk 50000000Hz bm PP pm ON vdd 3.3V width 8 timing UHS-DDR50 dt B [ 4.692533] mmcblk1boot0: unknown partition table [ 4.692735] *******************mmc init ok ******************* [ 4.760829] no red_led, ignore it! [ 4.877420] Registered led device: green_led [ 4.990878] Registered led device: blue_led [ 5.071654] scsi 0:0:0:0: Direct-Access USB TO I DE/SATA Device 0016 PQ: 0 ANSI: 4 [ 5.073468] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 5.076093] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled [ 5.077216] sd 0:0:0:0: [sda] Asking for cache data failed [ 5.077222] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 5.080968] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled [ 5.081965] sd 0:0:0:0: [sda] Asking for cache data failed [ 5.081972] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 5.081979] sd 0:0:0:0: [sda] Attached SCSI disk [ 5.142062] Registered led device: sunxi_respiration_lamp [ 5.167014] usbcore: registered new interface driver usbhid [ 5.175097] usbhid: USB HID core driver [ 5.181785] ac100_probe,line:2917 [ 5.204615] asoc: ac100-aif1 <-> pri_dai mapping ok [ 5.212405] asoc: ac100-aif2 <-> bb-voice-dai mapping ok [ 5.220350] ------------audio_hmic_irq---------- [ 5.230037] asoc: ac100-aif1 <-> sec_dai mapping ok [ 5.239875] asoc: ac100-aif3 <-> bb-voice-dai mapping ok [ 5.248096] asoc: ac100-aif2 <-> bb-voice-dai mapping ok [ 5.261235] asoc: sndhdmi <-> sunxi-hdmiaudio.0 mapping ok [ 5.270371] IPv4 over IPv4 tunneling driver [ 5.277642] TCP: cubic registered [ 5.283527] Initializing XFRM netlink socket [ 5.290923] NET: Registered protocol family 10 [ 5.298865] IPv6 over IPv4 tunneling driver [ 5.306242] NET: Registered protocol family 17 [ 5.313469] NET: Registered protocol family 15 [ 5.320759] Bluetooth: RFCOMM TTY layer initialized [ 5.328367] Bluetooth: RFCOMM socket layer initialized [ 5.336302] Bluetooth: RFCOMM ver 1.11 [ 5.342652] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 5.350723] Bluetooth: BNEP filters: protocol multicast [ 5.358618] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 5.367373] lib80211: common routines for IEEE802.11 drivers [ 5.375701] lib80211_crypt: registered algorithm ‘NULL’ [ 5.383624] Registering the dns_resolver key type [ 5.390910] libceph: loaded (mon/osd proto 15/24, osdmap 5/6 5/6) [ 5.399955] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 [ 5.410566] ThumbEE CPU extension supported. [ 5.417378] Registering SWP/SWPB emulation handler [ 5.424761] sunxi_bootup_extend_init: bootup extend disable(default) [ 5.434668] cmdline,disp= [ 5.439670] [HDMI] power vcc-hdmi-18 [ 5.447057] rtc_gettime(333): read time 1970-1-1 1:0:14 [ 5.454966] rtc0 rtc0: setting system clock to 1970-01-01 01:00:14 UTC (3614) [ 5.465856] sunxi_get_soc_bin: slow chip [ 5.472795] CPU Budget:Register notifier [ 5.479234] CPU Budget:register Success [ 5.485568] sunxi-budget-cooling sunxi-budget-cooling: Cooling device registered: thermal-budget-0 [ 5.501402] =========GPS========= :gsp not used in configuration
Then the last couple of lines look like u-boot starting again (highliting the bits I see back in your log): HELLO! BOOT0 is starting! boot0 version : 4.0.0 rtc[1] value = 0x00010000 rtc[2] value = 0x00020000 rtc[3] value = 0x00030000 DRAM DRIVE INFO: V1.0 DRAM Type =7 (2:DDR2,3:DDR3,6:LPDDR2,7:LPDDR3) DRAM normal_mode value: 00000001 DRAM CLK =672 MHZ PMU: AXP81X ddr voltage = 1200 mv using ic A83T using axp AXP813 DRAM zq value: 00003bfb dram size =2048 card boot number = 0 card no is 0 sdcard 0 line count 0
So, for now the best guess I can make from this garbled data is that something goes badly wrong while initializing your emmc flash. And that there is a problem with your serial port; either the USB converter or the one on the BPI. Sorry I could not bring you any happier news.
Alright, so I bought a 16GB microsd card and now I can see a normal linux start but it is still restarting.
Here is the log : http://pastebin.com/BMz3uiMa I’m gonna try an other image as I have now 16GB but I would like to use dietpi
Thanks for your help
EDIT: I tried Debian and it does the same.