Jump to content
MACscr

How do we get 1080p in Ubuntu?

Recommended Posts

Short answer is I don't know. I think it has to do with the following file:

/sys/class/disp/disp/attr/sys

***********

screen 0:
hdmi output mode(5) fps:60.6 1280x 720
err:   0 skip:   0
   BUF    enable ch[1] lyr[0] z[0] prem[N] a[globl 255] fmt[  0] fb[1280, 720;1280, 720;1280, 720] crop[   0,   0,1280, 720] frame[  13,   7,1254, 705] addr[43100000,       0,       0] flags[0x       0] trd[0,0]
acquire: 0, 25.5 fps
release: 0, 25.5 fps
display: 0, 25.5 fps

************End of file*****

There is a link image for arches (was pcDunio8) that describes the different screen modes and gives instructions to change it for that model. The UNO is different but my guess is that screen mode 6 to 10 is the one you want if there is anything in common with the other build. However if you change that in the above file it will probably screw up what ever that buffer string is doing. That will need the new resolution 1920 x 1080. I expect they played around with  it already and had trouble with it because 25.5 is a bit slow for frames per second. Adding resolution might require and even slower frame rate. Then again I'm just guessing. If I knew what I was doing I'd play around with it myself and get back to you.  Kind of interested in finding out the details to the same question.

Share this post


Link to post
Share on other sites

http://wiki.lxde.org/en/LXRandr

normally in this environment, one would change resolution with the xrandr at a command line or from a menu selection to change temporarily.

one could make it permanent after reboot here

sudo leafpad /etc/xdg/lxsession/LXDE/autostart

with something on the last line added like

@xrandr --auto --output DVI-1 --primary --mode 1680x1050 --left-of DVI-0

 

but that doesn't work on these 14.04 prebuilt images.

there is a script to change on the uno3 but that's not this.

board-config.sh is the filename & /usr/bin/ is where it's located. check it out, there's other settings that you can change.

.

one could edit the sys_config.fex, convert it to it's binary format & replace it

this is the section to change resolution

;screenx_output_mode  (used for hdmi output, 0:480i 1:576i 2:480p 3:576p 4:720p50)
;                     (5:720p60 6:1080i50 7:1080i60 8:1080p24 9:1080p50 10:1080p60)

screen0_output_mode      = 10 for 1080p60.

 

not a simple 'click here & save' solution right now.

 

-steph

 

-edit. i see Drake has pointed out where it's at.  i didn't look past what was in the sys_config.fex - maybe it's easier to change?

just took a look at the ubuntu 12.04 image, same sys file says hdmi output mode(10) fps:60.6 1920x1080 but it's running at 720 just as the 14.04 images.

Share this post


Link to post
Share on other sites

I are trying to change the sys_config.fex to 1080p display, but it doesn't work. Seemly it is not easy to get 1080P resolution.

i've used these.

windows...

https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/fex-bin-convertor-windows

linux...

https://github.com/linux-sunxi/sunxi-tools

 

did you mean that it just does not want to use 1080p?

Share this post


Link to post
Share on other sites

I was watching the pcDuino8 Uno boot and it seems to me that it is booting in 1080p. The text is very clear on my HDMI monitor compared to the fuzzy LXDE desktop. 

a solution could be convert your magic.bin to .fex - above links work for this.  it will show in that section i pasted above what it is.  mine was 720p 50hz pal.

if you are in US i'd change it to 60hz & ntsc but newer monitors shouldn't have a problem on display.

speaking of display, i'm assuming nobody has attempted to put a lcd type screen on there.  that's something else you need to change.  it's screen1_output_mode option & if i remember correctly, it was same 720p50 but sreen0 was default.  just adding that as an observation.

this is done manually something like this...

http://www.imajeenyus.com/computer/20130301_android_tablet/android/fex2bin_etc.html

 

ideal solution would be to have a user-friendly clicky GUI that would change it, test changes, reboot if necessary.

 

another solution would be to use a magic.bin with hard coded settings you want to change it to.  this is what others use in this type of environment to make this change currently.  you select which one you want with what resolution when you are installing linux on the device.

Share this post


Link to post
Share on other sites

im fine with manual as long as it works reliably. 

i agree completely.     looking forward to seeing some progress with this uno8... perhaps some threads of 'this doesn't work out of the box & why it doesn't, what is the possibility of it being fixed & by whom, is it possible & just not implemented here, and of course, what are the development goals regarding the OS and their timeline?

get it sorted out why the base image needs so much work, what are the possibility for each to be fixed.  you're not going to find mainline kernel support yet or full video support until either Allwinner decides to change their policy or someone takes it upon themselves or more likely a code dump. 

i'd like to get a copy of the development environment linksprite is making the images in the first place.  if there will be none provided or it's coming in six months it should be stated as such.  the uno8 has a lot of potential from what i've seen, but not with the software provided.   we are apparently early adopters of this board.

 

i think the most likely solution for us is to either find someone to modify the build environment of one of the SDK i posted links to in other thread or wait or figure out how to modify it ourselves.

i don't mind learning how, it's very well documented already elsewhere & google doesn't complain about translating & i've learned from it so i believe it's the same other than scripts that you either have to recreate or just type stuff out & of course hardware specific changes.  this link has their specific hardware that's used in the uno8.

https://s3.amazonaws.com/pcduino/Hardware/pcDuino8_Uno/pcduino8_uno_v01_201508.pdf

 

please try the edit in the mean time & post your results on editing the script.bin from one of the posted images & i'll do the same & see if we both come up with the same thing, it seems not many are working on this other than just the plugging in of *duino type modules.  i'll suggest not to try on the posted 12.04 image unless you want to fail before trying.  another suggestion, i did the same thing with a bin file from similar booting board that's working & compared side by side.  much easier for me anyways, most of this is totally new to me btw. :)

 

-stephan

Share this post


Link to post
Share on other sites

ok. there seems to be an issue on the script.bin on at least the ones i tested.  i checked these two images of 14.04 & the 12.04 posted https://s3.amazonaws.com/pcduino/Images/pcduino8/pcDuino8Uno/pcduino8_ubuntu14.04_20160102_preinstalled_opencv2.4.11.img.7z

https://s3.amazonaws.com/pcduino/Images/pcduino8/pcDuino8Uno/pcduino8_ubuntu_14.04_20160102.img.7zand https://s3.amazonaws.com/pcduino/Images/pcduino8/pcDuino8Uno/pcduino8_ubuntu_12.04_20150927.7z

for whatever reason, the bin will not convert to fex.  the 12.04 is too small to be legit & i get a malformed data error trying to convert on the other two listed.

when this is corrected or confirmed, i'll change the above to reflect it.

 

this is the method that i use to change stuff from the start.  this is done on the uno8 booted with the 2nd image listed above.  this assumes you have internet access to apt-get & get some files.

at some point, familiarize yourself with what options are.  not all options work on all boards so don't just go changing stuff.  there are tests you can run on the uno8 to help you with some you parameters, others are researched.

this is just in the context of manually changing a video resolution setting.

note: this covering only to do with the resolution, but getting your fex to edit is done for other reasons as well.

http://linux-sunxi.org/Fex_Guidespecifically section [disp_init]

A FEX file defines various aspects of how the SoC works. It configures the GPIO pins and sets up DRAM, Display, etc parameters.

ready?

first is a prerequisite: libusb-1.0

sudo apt-get install libusb-1.0-0-dev

then we git some tools, make them for our use.

mkdir sunxi
cd sunxi
git clone git://github.com/linux-sunxi/sunxi-tools.git
cd sunxi-tools
make

next, mount 2nd partition to a directory we create & copy script.bin from the sd card partition into the folder with the above tools.

sudo mkdir /mnt/mmcpart2
sudo mount /dev/mmcblk0p2 /mnt/mmcpart2
cp /mnt/mmcpart2/script.bin ./

this is being done on the uno8 in a ubuntu environment but just as a notice, don't edit fex or text files with windows notepad.  besides not displaying line items correctly, it modifies them in a bad way.  if you find yourself wanting to edit text in windows, use Notepad++ or something similar.

next we convert script.bin to a text-based script.fex for editing.

sudo chmod 777 script.bin
./bin2fex script.bin > ./script.fex
sudo leafpad script.fex

this is the moment you were waiting for.  depending on what resolution you wanted your selection could be different.

refer to the above address Fex Guide as comment section doesn't show everything & sometimes isn't there or not English.

screen0_output_mode = 10

don't forget to save if you make changes.

convert modified script.fex back to script.bin & put back onto partition unmount the partition. then reboot for changes to take affect.

./fex2bin script.fex > ./script.bin
sudo cp ./script.bin /mnt/mmcpart2/
sudo umount /mnt/mmcpart2
sudo reboot

for whatever reason my script.bin is saying it's corrupt & it's not working :huh:

that is how i do it from the sd card you booted up on in this environment.

you also can mount the same image you would flash the sd card with & pull the script.bin that way or pull it from android but i think you would need SU & the android image does not default with it.

i'll try it again from the beginning & from an image file & post results.

 

if Youkee or somebody with an Uno8 would try this as well & confirm if there is an issue & fix if necessary.

 

you don't have to actually make changes to your fex file if you just want to see it's contents.  i've translated the chinese from inside mine to english and added comments.  if you add comments, the line has to start with a semicolon & treat all options as being case sensitive.  if it's lower-case, leave it that way.

Share this post


Link to post
Share on other sites

here's the problem & a solution. well, sorta...

the script.bin file seems to has been corrupted at some point.

this image has working 1080p but it's got other issues so maybe convert the script.bin from this to the newer image as a temporary fix.

https://s3.amazonaws.com/pcduino/Images/pcduino8/pcDuino8Uno/pcduino8_ubuntu_14.04_20151019.7z

-steph

 

 

try to extract your bin file & convert it to fex without errors, & take a look at it, it's something in this environment you should be able to do.

 

...edit...

although that image has 1080p, there are errors in the script.bin file as i saw on the others stated above.

i'll post a separate thread on it since it's a problem across the hardware & not just this video issue.

 

i will go thru the methods i've used to make one & see if any are realistic to give instructions on,

it would be easy if someone at linksprite could post a clean copy of the fex file with a notice of don't use it unless you read & understand the directions on it. :)

Share this post


Link to post
Share on other sites

I tried the Fex file conversion thing without any success at all. The mount command was kind of freaky I think it made a hall of mirrors effect in the file system. 

So far there is only one choice. Navigate to the menu and choose the one option.  

I didn't change the sys file because I haven't found an alternate bit of code to put in there. I was more interested in that script.bin and learning how to make my own from scratch but no one has this listed as a target board. That makes it a big job for people who really know what they are doing called disassembly.  It is possible for a company that makes a board like this to include the stuff that goes into the script.bin file as a text file next to it. That is not going to happen. So at this point you just have to trust that the resolution provided is the best possible resolution.

Share this post


Link to post
Share on other sites

Me too. MACscr. Makes me mad. Seems like the board should be able to do it.  The fact that the GUI takes you to places that are grayed out is particularly irksome. On one hand we are locked out of something we bought, and locked into helping in develop it. On the other hand it is still a big opportunity to learn something undeniably useful that few people know. That is how to compile onto a totally new platform like what they do at the yocto project or sunxi project. However they do advertise that engineers would answer your questions. 

 

Stephan, I noticed somewhere in the process that the tools were using the sun4i thingy-ma-bob instead of the sun8i. So I think that is why it isn't converting. Not necessarily "malformed" as it says. I have to help my son with a school project so I'm putting this aside for a bit. If there was a place to =sun8i  that is what I would try. :(  Otherwise I wish I could copy and paste into that sys file something more appropriate just to see what would happen.

 

Edit so I have been looking for clues. I went to the sources index pages and downloaded the config files and unpacked the config file and had a read. Board config.sh file uses whiptail to reduce the size of the screen posted in /etc/screen.conf then it writes something to /usr/bin/setwindow

I could only look at the script.bin with a hex editor and could not convert it. Did wonder about the possibility of this build using a device tree configuration which is a whole other ball of wax. Maybe could invoke whiptale or edit the /etc/screen.conf. Looked all over the net and only get more confused.

Share this post


Link to post
Share on other sites

I helped myself and bootet Linksprite's image on my Banana Pi M3 (it's necessary to exchange boot0 since there the SoC ID is checked and when wrong boot0 stops -- for details please see http://forum.linksprite.com/index.php?/topic/4516-lm-sensors-no-worky/&do=findComment&comment=12084)

 

Also please have a look at lines 133 and 153 in the boot log: http://pastebin.com/GSsdyuAw

 

Since Banana Pi M3's hardware is different I created another script.bin from a fex file and put it on the 2nd partition of the SD card. Then stopped u-boot autoboot and tried to load it manually. Unfortunately then the boot gets stuck: http://pastebin.com/9nqnzvyE

 

The uEnv.txt contents seem not to fit u-boot code and it also seems script.bin is never read. Unfortunately the script_extractor binary I tried to use segfaults so I've no clue how to read out sys_config.fex stuff really being used.

 

Since the Linksprite guys refrain from publishing sources I'll refrain from buying Linksprite products starting from now on.

 

Regarding 1080p I would have a look at the fbset package and put the necessary fbset call in /etc/rc.local

Share this post


Link to post
Share on other sites

tKaiser thanks for looking at it.  Would a device tree type build affect the output?

I was having trouble with getting the script bin file to convert. Skills could be I don't know how to run a c program. Though bin2fex seemed to run. Said "malformed" file.  I 

 

open config.fex, maybe it is not exist
attched ok, mgr0<-->device1, type=4, mode=4----
ready to set mode
[      1.146]finally, output_type=0x4, output_mode=0x4, screen_id=0x0, disp_para=0x404
fail to find part named env
Using default environment

 

 'cat /proc/cmdline' yeilds: console=ttyS0, 115200 console=tty1 root=/dev/mmcblk0p3 init=/init

 

I tried the script-extractor tool to look at sys_config.fex. Not sure whats going on with that. I compiled it and got a a.out executable which I ran but could not find the output. Sorry I'm pretty new at this. 

Share this post


Link to post
Share on other sites

Why do you fiddle around with script.bin if it won't be read anyway?

 

It seems the u-boot code they use is incomplete or at least fails to read script.bin on the 2nd partition (simply try it out, rename or remove script.bin and see what happens). The script-extractor tool is meant to read out DRAM contents to get the real values of sys_config.fex used (to be able to generate a fex file and/or adjust the settings).

 

Unless Linksprite stops violating the GPL and provides the BSP sources it's useless to investigate further.

Share this post


Link to post
Share on other sites

I found a discussion about cubieboard on a google chat Q&A:

 

Still need to try that booting without the script.bin file even present. In a similar vein I found this link:

 

https://groups.google.com/forum/#!topic/beagleboard/77IuIt1OCss

 

It is about uImage not being read on /boot. They say that an uImage file is used but not the one in the /boot folder. So mounting the boot partition as Stephan describes in his other post on converting to FEX , can be done while the board is running to edit the "real" uImage file. Anyway it is still an open question as to how you get it to read the conveniently editable uImage file. I would like to play around with the stuff they talk about in the above link.

 

I had to use my extra screen for other things and haven't had a chance to settle down to burn and test SD images. To try reading FEX with the older images. (My script.fex was empty)  Also the compilation of device tree vs compilation of an image is still a big learning curve for me. Linaro, Yocto, Sunxi sites all have instructions and they are mostly for other boards.

Instructions for FEX http://linux-sunxi.org/Retrieving_device_information#Reading_memory_information_from_registers

Instructions for DTS device tree http://linux-sunxi.org/Device_Tree

Share this post


Link to post
Share on other sites

I helped myself and bootet Linksprite's image on my Banana Pi M3 (it's necessary to exchange boot0 since there the SoC ID is checked and when wrong boot0 stops -- for details please see http://forum.linksprite.com/index.php?/topic/4516-lm-sensors-no-worky/&do=findComment&comment=12084)

 

Also please have a look at lines 133 and 153 in the boot log: http://pastebin.com/GSsdyuAw

 

Since Banana Pi M3's hardware is different I created another script.bin from a fex file and put it on the 2nd partition of the SD card. Then stopped u-boot autoboot and tried to load it manually. Unfortunately then the boot gets stuck: http://pastebin.com/9nqnzvyE

 

The uEnv.txt contents seem not to fit u-boot code and it also seems script.bin is never read. Unfortunately the script_extractor binary I tried to use segfaults so I've no clue how to read out sys_config.fex stuff really being used.

 

Since the Linksprite guys refrain from publishing sources I'll refrain from buying Linksprite products starting from now on.

 

Regarding 1080p I would have a look at the fbset package and put the necessary fbset call in /etc/rc.local

Lines 140, 141 show that there is no FASTBOOT MBR in the image. It sees 0 partitions. linux-sunxi has a utility to build this (like Allwinner's version of sfdisk.)

 

They somehow forgot to run the fastboot partition utility/step on the Uno's image.

 

The STB/its image has this at a constant address on the boot media. It's old, old 2011-09 u-boot boots the kernel by loading an entire 64MB *FASTBOOT* partition into memory (remember H8 skips boot1 -- so u-boot is loaded by the BSP)

 

This is on the linux-sunxi wiki somewhere around the A20 boot process and then the H8's differences.

 

The Uno is then skipping uEnv.txt because it also needs the FASTBOOT MBR to find the *RAW* "ENV" partition -- so it uses the static environment compiled into it. You may even be able to interrupt the boot process, change the environment, and then save changes directly back to the static/global variable in u-boot's blob at either +80 or +1600 blocks (IIRC.)

Share this post


Link to post
Share on other sites

I played a bit around today with an Armbian rootfs and the latest fixes SinoVoip has in their BSP (they learned how to let u-boot read files into RAM: script.bin/uEnv.txt support actually working!). I also tried to patch the kernel up to 3.4.110 (since we have tons of fixes already in our repo), but that just worked out up until 3.4.42, then the 1st patch didn't apply correctly: http://forum.armbian.com/index.php/topic/474-quick-review-of-banana-pi-m3/?p=5840

 

I then combined both and booted this pseudo Armbian image. Works and also uEnv.txt/script.bin will work when stored at the right location. So you unfortunate Linksprite customers are able to use the Banana Pi M3 BSP github repo to fix the problems you suffer from (or did the Linksprite folks realised in the meantime how to support script.bin? In case they don't it's outlined at the end of this mini tutorial how to deal with the situation, the dd if=u-boot.fex of=/dev/$sdcard bs=1k seek=16400 approach).

 

Anyway: I thought about providing this OS image to you users but since I tested the whole Armbian boot process (board auto detection on 1st boot, automatic rootfs resizing, password resets, SSH key regeneration and so...) now the image is definitely too large (16 GB) and the pcDuino8 Uno isn't worth the efforts as long as Linksprite doesn't publish BSP sources.

 

BTW: Replies won't be read. I will quit here as long as Linksprite violates the GPL and does not provide at least the crappy BSP sources.

Share this post


Link to post
Share on other sites

BTW: I already deleted the crap from my build host but decided to provide an archive to cure existing OS images for Banana Pi M3 which might also work with H8 boards too since boot0 won't be overwritten. Instructions and path to archive here: http://linux-sunxi.org/Banana_Pi_M3#Images

 

The used kernel config is this here. So in case anyone want to try it out, grab an OS image from Linksprite for H8 and follow the aforementioned instructions (you might also untar the kernel modules after the first boot). I would suspect you end up with an OS image containing a few more fixes (at least kernel 3.4.42 instead of 3.4.39) and support for uEnv.txt and script.bin. If that works you know that you simply can use the Banana Pi M3's BSP, adjust kernel config or whateher you want and cure your Linksprite OS images this way unless they realise how moronically it is to not release their BSP sources.

 

EDIT: Doesn't work since for whatever reason the Linksprite OS images have a different partition layout:

root@linaro-alip:/lib/modules# cat /proc/partitions 
major minor  #blocks  name

 179        0    7761920 mmcblk0
 179        1      35840 mmcblk0p1
 179        2      32768 mmcblk0p2
 179        3    7692288 mmcblk0p3

 

 

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
[mmc]: mmc driver ver 2014-8-11 15:06:39
[mmc]: ***Try SD card 0***
[mmc]: SD/MMC Card: 4bit, capacity: 7580MB
[mmc]: vendor: Man 00035344 Snr 1013290e
[mmc]: product: SU08G
[mmc]: revision: 8.0
[mmc]: ***SD/MMC 0 init OK!!!***
sdcard 0 init ok
ERROR! NOT find the head of uboot.
The size of uboot is 000d8000.
sum=2a137265
src_sum=2a137265
Succeed in loading uboot from sdmmc flash.
Ready to disable icache.
Jump to secend Boot.
[      0.319]

U-Boot 2011.09-rc1-00000-ge7e0a33-dirty (Mar 02 2016 - 18:57:15) Allwinner Technology 

[      0.328]version: 2.1.0
normal mode
[      0.407]pmbus:   normal or secure os
ready
[      0.411]PMU: AXP81X
[      0.413]PMU: AXP81X found
bat_vol=215, ratio=100
[      0.419]PMU: dcdc2 900
[      0.421]PMU: pll1 1008 Mhz
AXI0=336 Mhz,PLL_PERIPH =1200 Mhz AHB1=200 Mhz, APB1=100 Mhz 
set power on vol to default
dcdc1_vol = 3300, onoff=1
dcdc2_vol = 900, onoff=1
dcdc3_vol = 900, onoff=1
dcdc4_vol = 900, onoff=1
dcdc6_vol = 900, onoff=1
aldo1_vol = 1800, onoff=0
aldo2_vol = 1800, onoff=1
aldo3_vol = 3000, onoff=1
eldo2_vol = 1800, onoff=0
dldo1_vol = 3300, onoff=0
dldo2_vol = 3300, onoff=0
dldo3_vol = 2500, onoff=1
dldo4_vol = 2800, onoff=0
fldo2_vol = 900, onoff=1
gpio0_vol = 3300, onoff=1
gpio1_vol = 3300, onoff=1
find power_sply to end
supply=dcdc1
axp=axp81x, supply=dcdc1, vol=3300
reg addr=0x1c20b04, value=0xd, pmu_vol=3300
supply=dcdc1
axp=axp81x, supply=dcdc1, vol=3300
reg addr=0x1c20b08, value=0xd, pmu_vol=3300
supply=dldo3
axp=axp81x, supply=dldo3, vol=1800
reg addr=0x1c20b0c, value=0x0, pmu_vol=1800
supply=dcdc1
axp=axp81x, supply=dcdc1, vol=3300
reg addr=0x1c20b10, value=0xd, pmu_vol=3300
supply=dcdc1
axp=axp81x, supply=dcdc1, vol=3300
reg addr=0x1c20b14, value=0xd, pmu_vol=3300
supply=dcdc1
axp=axp81x, supply=dcdc1, vol=3300
reg addr=0x1c20b18, value=0xd, pmu_vol=3300
supply=dcdc1
axp=axp81x, supply=dcdc1, vol=3300
reg addr=0x1c20b1c, value=0xd, pmu_vol=3300
supply=aldo3
axp=axp81x, supply=aldo3, vol=3000
reg addr=0x1f02f00, value=0xa, pmu_vol=3000
config gpio bias voltage finish
vbus exist
no battery, limit to dc
ac100 reg 0x00 = 0x101
ac100 reg 0xd0 = 0x0
ac100 reg 0xd1 = 0x0
fel key old mode
run key detect
no key found
no key input
dram_para_set start
dram_para_set end
[      1.650]DRAM:  2 GiB
relocation Offset is: 75af7000
user_gpio config
user_gpio ok
gic: normal or no secure os mode
script config pll_de to 504 Mhz
script config pll_video1 to 297 Mhz
Not Found clk pll_video in script 
enable power vcc-hdmi-18, ret=0
DRV_DISP_Init end
[      1.815]boot_disp.output_disp=1
[      1.818]boot_disp.output_type=3
[      1.822]boot_disp.output_mode=10
[      1.825]fetch script data boot_disp.auto_hpd fail
disp1 device type(4) enable
attched ok, mgr1<-->device1, type=4, mode=10----
ready to set mode
workmode = 0
MMC:     0
[      1.840][mmc]: mmc driver ver 2015-04-13 14:50:00
[      1.845][mmc]: get sdc_phy_wipe fail.
[      1.849][mmc]: get sdc0 sdc_erase fail.
[      1.853][mmc]: get sdc_f_max fail,use default 50000000Hz
[      1.859][mmc]: get sdc_ex_dly_used fail,use default dly
[      1.864][mmc]: SUNXI SD/MMC: 0
[      1.877][mmc]: *Try SD card 0*
[      1.924][mmc]: CID 0x3534453 0x55303847 0x80101329 0xe00d669
[      1.929][mmc]: mmc clk 50000000
[      1.932][mmc]: SD/MMC Card: 4bit, capacity: 7580MB
[      1.937][mmc]: boot0 capacity: 0KB,boot1 capacity: 0KB
[      1.943][mmc]: ***SD/MMC 0 init OK!!!***
[      1.947][mmc]: erase_grp_size:0x1WrBlk * 0x200 = 0x200 Byte
[      1.953][mmc]: secure_feature 0x0
[      1.956][mmc]: secure_removal_type  0x0
[      1.960]sunxi flash init ok
[      1.965][mmc]: MMC Device 2 not found
[      1.969][mmc]: Can not find mmc dev
[      1.972][mmc]: read first backup failed in fun sdmmc_secure_storage_read line 1854
sunxi_secstorage_read fail
get secure storage map err
sunxi secure storage is not supported
private partition is not exist
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_mmc
key 0
recovery key high 10, low 8
cant find fstbt value
no misc partition is found
to be run cmd=run setargs_mmc boot_normal
serial is: 00000000000000000000
mount part name 
[disk_read_fs] no the partition
cant open script.bin, maybe it is not exist
WORK_MODE_BOOT
board_status_probe
[      2.036]power trigger
bat_exist=0
[      2.039]no battery exist
sunxi_bmp_logo_display
sunxi flash error: cant get part 0 offset
** Can't read from device 0 **

** Unable to use sunxi_flash 0:1 for fatload **
sunxi bmp info error : unable to open logo file bootlogo.bmp
[      2.060]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# 

 

 

Share this post


Link to post
Share on other sites
Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×