Jump to content

dfwBrawler

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Here's an update to our testing. The problem now is that the fel-mass-storage setup seems to have a 512MB device size limitation. We switched to trying to use the sunxi-fel tool from Zador: https://github.com/zador-blood-stained/fel-mass-storage After connecting the board to a Ubuntu machine, fdisk sees the eMMC as /dev/sdb Disk /dev/sdb: 511 MB, 511221760 bytes 255 heads, 63 sectors/track, 62 cylinders, total 998480 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xe64560c2 Device Boot Start End Blocks Id System The trouble is that the eMMC device is 8GB and not 512MB. When trying to dd the image file via FEL it works fine until it gets close to the 512MB limit and then fails with a "no space left on device" error. /home/x/Desktop# dd if=emmc.img | pv -s 8G | dd of=/dev/sdb bs=16M dd: error writing ‘/dev/sdb’ 488MB 0:00:28 [ 14MB/s] [> : No space left on device:22 488MB 0:00:28 [17.4MB/s] [> ] 5% 0+132653 records in 0+132652 records out 511221760 bytes (511 MB) copied, 28.053 s, 18.2 MB/s I notice that the heads/cylinders/sectors numbers are all set to maximum. Does this mean there isn't a way to support devices larger than 512MB? Would it be possible to switch to a much higher number of bytes/sector instead of 512KB/sector? Is there another way around the limitation?
  2. That works great now. I pulled down the updates and built a dev 4.11 release. eMMC works and so does Ethernet. I want to thank everyone for your help getting this problem solved. Without this dedicated group of people there wouldn't be a working Linux release for Allwinner boards.
  3. We have done some more testing. The device tree stuff seems confusing. We did two builds. 1) h3-orangepi-zeroplus, 4.11.0 Xenial, mainline 2) h3-orangepi-zeroplus, 3.4.113, xenial legacy 1) h3-orangepi-zeroplus, 4.11.0 Xenial, mainline. This build gives Ethernet: yes and eMMC: no. Doing a diff of sources/linux-sun8i-mainline/orange-pi-4.11/arc/arm/boot/dts/sun8i-h3-orangepi-zeroplus.dts vs sources/linux-sun8i-mainline/orange-pi-4.11/arc/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts shows only title string differences < model = "Xunlong Orange Pi Zero"; < compatible = "xunlong,orangepi-zero", "allwinner,sun8i-h2-plus"; --- > model = "Xunlong Orange Pi Zero Plus"; > compatible = "xunlong,orangepi-zeroplus", "allwinner,sun8i-h3"; This looks like the Zero plus dts file was accidentally just copied from the Zero dts file without making the necessary changes. 2) zero plus 2 h3 3.4.113, xenial legacy This give eMMC: yes and Ethernet: no Doing a diff of source/u-boot/v2017.05/arch/arm/dts/sun8i-h3-orangepi-zeroplus.dts vs source/u-boot/v2017.05/arch/arm/dts/sun8i-h2-plus-orangepi-zero.dts shows both include the same dtsi file #include "sun8i-h3.dtsi" and they both have the same emac section &emac { phy = <&phy1>; phy-mode = "mii"; allwinner,use-internal-phy; allwinner,leds-active-low; status = "okay"; phy1: ethernet-phy@1 { reg = <1>; }; }; Also neither lib/config/fex/orangepizeroplus2-h3.fex nor lib/config/fex/orangepizero.fex shows any mention of emac or phy or ethernet Lastly we did notice is that we tried to comment out the "disabled" line in the emac section of the sun8i-h3.dtsi file, but after doing the build, the line was no longer commented. Could that be part of why we aren't getting Ethernet?
  4. Thanks to help in another thread to solve our eMMC problems, we are making progress getting Armbian working well on the H2+ boards we have. Now we would like to be able to make a snapshot of the eMMC device and then be able to write the whole image to another board. I have been able to create a single file backup using both these methods (done after booting from SD). The created files appear to be the same size. dd if=/dev/mmcblk1 bs=16M | gzip -c > /mnt/usbflash/emmc.img.gz or ./backup_block_device.sh (from https://code.online-mp.pl/svn/public/backup_block_device/trunk/) To write the image, we'd like to use FEL. When we run sunxi-fel on a windows machine we do detect the board: C:\win32>sunxi-fel.exe -l USB device 001:012 Allwinner H3 02c00042:44004620:79910124:3c23010e When I look at the command line for the start.bat tool for writing to eMMC, I see this line, but it isn't clear where a single image file would start in memory. win32\sunxi-fel.exe -p uboot %BOARD%\u-boot-sunxi-with-spl.bin write 0x42000000 %BOARD%\zImage write 0x43000000 %BOARD%\script.bin write 0x43300000 %BOARD%\uInitrd write 0x43100000 %BOARD%\boot.scr My question is, what command line would we use to write the eMMC image in one block?
  5. The board we are using is not commercially available. As best I can tell it was primarily based on a Zero and has an added eMMC. Can you elaborate on what you mean by "merge DT and resulting dts compiled into dtb"?
  6. Let me try to clarify. The board we have is electrically very similar to the Pi Zero, except that it also has eMMC. We used Igor's suggestion of using the image for the Zero Plus 2-H3 and that worked to get eMMC working on the board we have. I understand that the Zero Plus2-H3 doesn't have an Ethernet port. When we use the Zero image on the board we have, the Ethernet works well. What I'm trying to figure out is how to enable the Ethernet drivers within the Zero Plus2-H3 image such that it will behave exactly like the Ethernet drivers in the Zero image.
  7. We have our own WiFi device and it works fine with the drivers we build and install. The Ethernet works fine with the original Zero board image. The Ethernet on the board we are using is wired exactly the same way to the H2 as the original Zero.
  8. Ran a few more tests. 1) tried Armbian_5.27.170508_Orangepizeroplus2-h3_Ubuntu_xenial_dev_4.11.0.img - there's an Ethernet device, but no eMMC device 2) tried building an SD image by selecting Jessie instead of Xenial - it built ok, there's an eMMC device, but no Ethernet 3) tried building an SD image but patched using these instructions: https://forum.armbian.com/index.php?/topic/4186-orange-pi-zero-ethernet-disabled-in-mainline-411/ there's an eMMC device but still no Ethernet device.
  9. Ran a quick test with Armbian_5.27_Orangepizeroplus2-h3_Ubuntu_xenial_default_3.4.113.img It boots from SD with a minimum of errors. The eMMC device is available and nand-sata-install runs without errors. The board then boots from eMMC (whoo hoo we are making progress). We don't see an Ethernet device. So two new questions. 1) Is there a simple fix to turn on Ethernet? 2) What are the chances of getting Jessie to work? Thanks.
  10. We have an H2+ based board that is very similar to the Orange Pi Zero. Basically it is equivalent to a Zero board with a different Wi-Fi chip and adding an eMMC chip. The SD card is on the SDC0 bus and the eMMC chip is on the SDC2 bus. The SDC1 bus isn't connected. We have been using the stock Orange Pi Zero Jessie images on SD card and they work pretty well (thanks to you guys for your hard work) We want to put a Jessie image on the eMMC but we are having trouble. First we tried the nand-sata-install script but it wouldn't run without the eMMC device. We edited the lib/config/fex/orangepizero.fex file and changed sdc_used for mmc2 to 1 from 0 and rebuit the SD image. This gave me the eMMC device and nand-sata-install ran withtout errors. Now SD and eMMC both appear in /dev/mmc* root@orangepizero:~# ls /dev/mmc* /dev/mmcblk0 /dev/mmcblk1 /dev/mmcblk1boot1 /dev/mmcblk0p1 /dev/mmcblk1boot0 /dev/mmcblk1p1 Unfortunately when the board reboots it only displays the following: U-Boot SPL 2017.03-armbian (May 03 2017 - 15:25:24) DRAM: 512 MiB Trying to boot from MMC2 MMC Device 1 not found spl: could not find mmc device. error: -19 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### We also tried putting an Orange Pi Plus image on the eMMC, but it had a number of errors when it booted from eMMC plus it seemed to be missing the Ethernet device. So the question is, what are we missing to get the eMMC working correctly?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines