-
Posts
17 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Mario Ernesto Villarreal
-
-
UPDATE: yup, the armbian kernel is not recognizing the NAND, because I have installed the kernel from h3droid, it boots and recognizes the 2nd MMC if inserted.
EDIT: Well, at least it is booting, I hope there's a fix for a mainline kernel for this
-
Interesting, flashed back AGAIN the old image, but flashed your uboot, mounted and copied the sunvell file, and when booting, this appears:
Starting kernel ... Error: unrecognized/unsupported machine ID (r1 = 0x00000000). Available machine support: ID (hex) NAME 00001029 sun8i Please check your kernel config and/or bootloader.
Seems to be that the uboot doesn't have the machine id defined?
EDIT: Manually setting machid in uboot with 1029 worked
setenv machid 1029 saveenv
But armbian can't find the emmc... is the kernel making troubles? Will check
-
2 minutes ago, TheLinuxBug said:
re-writing H3Droid
I was doing it on the meantime... yup, it worked again, will try to recover it. Thanks!
-
10 minutes ago, TheLinuxBug said:
few times
Well.. tried to recover uboot writing to memory, and I made a rookie mistake hahaha and the sdcard is not booting. How many few times?
-
Well, initially, it hangs on:
U-Boot SPL 2017.07-00494-g19d1f1a-dirty (Aug 30 2017 - 15:37:08)
DRAM: 1024 MiB
Failed to set core voltage! Can't set CPU frequency
Trying to boot from MMC1
I am trying to check if I can reprogram uboot from here
-
It is not booting from the sdcard just soldered to the uart to try to fix it
-
Ok, I get it... the only problem is that now it is not booting from the SD, I think that is the problem with tat uboot. I think I need to attach it to a UART console and reprogram it
-
1 minute ago, TheLinuxBug said:
That's because when you write the image (Armbian) back over mmcblk1 you overwrote u-boot and fex again
I did it on the internal eMMC, bro
The SDCARD is not booting now, I'll check what I did wrong, but at leaste internal eMMC boot to uboot, boots Linux and then panicks (I think it is the UUID on the bootargs)
-
1 hour ago, TheLinuxBug said:
stuck.
With the fex file, ti worked. I used the next command:
wget --no-check-certificate "https://web.archive.org/web/ 20171210180447/http://kaiser-edv.de/tmp/NumpU8/Armbian_5.34_Sunvell-r69_Ubuntu_x enial_default_3.4.113_desktop.img.xz" -O - | pv | unxz | dd of=/dev/mmcblk1
And at least it booted, until it panicked hahaha.
I am on the right direction, thank you!
-
38 minutes ago, TheLinuxBug said:
Armbian for OPi Plus 2E image
Tried, didnt work (freezes at BOOTING KERNEL). I am installing H3Droid in this moment
-
39 minutes ago, TheLinuxBug said:
eMMc
eMMC still not recognized
I am booting from the SD card btw.
-
1 hour ago, TheLinuxBug said:
Hey Guys,
I ended up using a FEX file pro
Hey, bro! It's me, netomx from LET It is a pleasure to know you're working on this. Does this FEX file enables eMMC access?
-
8 minutes ago, raschid said:
There is community support (sunvell_r69.csc) for a mainline kernel now, which provides access to the eMMC. No HDMI support yet though ...
Nice! So we need to recompile the kernel with the patch?
-
2 minutes ago, guidol said:
because it need some partition-scheme...
That should be easy to fix, with sunxi-nand-part, the hard problem is to make it recognizable
-
Mine has 470 ohms open and closed is short-circuit, but still has the same message. Do you think I need to patch uboot?
-
H2: Sunvell R69 Android TV Box (AliExpress)
in Allwinner CPU Boxes
Posted
Yup, you're right, pal. Apologies if I used NAND...
But no, your image doesn't recognize the internal eMMC, I had to use h3droid's kernel to recognize it