markbirss

Members
  • Content Count

    47
  • Joined

  • Last visited

About markbirss

  • Rank
    Advanced Member

Recent Profile Visitors

629 profile views
  1. markbirss

    Lichee Pi zero

    You can try use a used 4.3inch TomTom display for cheap on Ebay
  2. markbirss

    Lichee Pi zero

    Im waiting for 7inch 1024x600 screen also
  3. markbirss

    Lichee Pi zero

    @ftp-bin2fex Yes, here is a 4.3 inch 800x480 screen, the default image has it enabled for uboot. (im still waiting for my screens) https://www.banggood.com/Lichee-Pi-5-inch-LCD-Display-RTP-800480-Resolution-With-4-wire-Resistive-Touch-Screen-p-1340806.html?rmmds=search&cur_warehouse=CN https://licheepizero.us/ Also the Zero Dock board with Ethernet https://www.banggood.com/LicheePi-Zero-1GHz-Cortex-A7-512Mbit-DDR-Development-Board-Mini-PC-p-1337966.html
  4. @tpc010 oh thank you! for building, i will send link to where to store image (personal message)
  5. I don't have other u-boot configs to try and the previous version do the same
  6. I did blacklist the pwm_bl on the card, but it just stuck at Starting Kernel... Did you need to set via u-boot console the disp parameter at all? it seems my bootup want to change video mode ?
  7. @tpc010 is it possible for you to share your last known working image ? I found a YunTab 7, but my build stuck at starting kernel....
  8. markbirss

    I2S Codec on Euler bus of Pine A64+

    try changing "status = "disabled"; -------> "okay"" to
  9. @gprovost refer to these links for detail around how cjdns uses it's own CryptoAuth protocol with ed25519, poly1305, and salsa20. https://github.com/cjdelisle/cjdns/blob/master/doc/Whitepaper.md https://github.com/hyperboria/bugs/issues/112 To see if the encryption task the CJDNS uses benefits or not from cryptodev hw acceleration
  10. @gprovost thank you for effort with the guide. Could you possibly include some CJDNS benchmarks ?
  11. markbirss

    H3 I2S0 DT overlay

    @nikkov also not armbian related, any chance you tried this or want to try ? NanoPi-NEO2 の I2SでMCLK出力 & 384kHz, 768kHz, 1536kHz, 8kHz https://qiita.com/blue-7/items/d643cc9e441ca594a01e http://www.single-ended.com/Nanopi-neo.htm
  12. As already contributed by @Elektrický and @martinayotte Here what I did with a recent ARMBIAN 5.64 user-built Ubuntu 18.04.1 to flash the mx25l1606e (2048 Kbytes) spi flash with u-boot-sunxi-with-spl.bin Modify /boot/armbianEnv.txt Add spi-jedec-nor to overlays and param_spinor_spi_bus=0 as example below verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost2 usbhost3 spi-jedec-nor rootdev=UUID=ee53d069-0ba8-4123-943b-ac96fb25148c rootfstype=ext4 param_spinor_spi_bus=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Install mtd-utils apt install mtd-utils Verify existence of the mtd device (will only work if your board actually has a supported spi chip) mtd_debug info /dev/mtd0 Should show something like this mtd.type = MTD_NORFLASH mtd.flags = MTD_CAP_NORFLASH mtd.size = 2097152 (2M) mtd.erasesize = 4096 (4K) mtd.writesize = 1 mtd.oobsize = 0 regions = 0 Erase the mtd device flash_erase /dev/mtd0 0 256 Find the local "u-boot-sunxi-with-spl.bin" and it's size in bytes (548864) find / -name u-boot-sunxi-with-spl.bin ls -l /usr/lib/linux-u-boot-next-orangepizero_5.64_armhf/u-boot-sunxi-with-spl.bin -rw-rw-r-- 1 root root 548864 Oct 21 18:07 /usr/lib/linux-u-boot-next-orangepizero_5.64_armhf/u-boot-sunxi-with-spl.bin Write the local u-boot-sunxi-with-spl.bin to the mtd device nandwrite -p /dev/mtd0 /usr/lib/linux-u-boot-next-orangepizero_5.64_armhf/u-boot-sunxi-with-spl.bin Write the mtd device to a local file to compare with local u-boot-sunxi-with-spl.bin (using the size of bytes the u-boot file used 548864) mtd_debug read /dev/mtd0 0 548864 current.bin Compare the current.bin with the local /usr/lib/linux-u-boot-next-orangepizero_5.64_armhf/u-boot-sunxi-with-spl.bin cmp /usr/lib/linux-u-boot-next-orangepizero_5.64_armhf/u-boot-sunxi-with-spl.bin current.bin If they are identical no output will be shown from the cmp command Now you can write the recent Armbian image to USB drive, remove the sdcard from the Orange Pi and power up the board. It should now read u-boot from the spi and attempt to boot from USB device If all went well as this example below U-Boot SPL 2018.05-armbian (Oct 21 2018 - 20:06:47 +0200) DRAM: 512 MiB Trying to boot from sunxi SPI U-Boot 2018.05-armbian (Oct 21 2018 - 20:06:47 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 Loading Environment from EXT4... MMC: no card present ** Bad device mmc 0 ** Failed (-5) In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 MMC: no card present ** Bad device mmc 0 ** MMC: no card present ** Bad device mmc 0 ** 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... 2 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop MMC: no card present Device 0: Vendor: Lexar Rev: 1100 Prod: USB Flash Drive Type: Removable Hard Disk Capacity: 7494.0 MB = 7.3 GB (15347712 x 512) ... is now current device Scanning usb 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 244 ms (14.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SPI Boot script loaded from usb 266 bytes read in 198 ms (1000 Bytes/s) 8302942 bytes read in 680 ms (11.6 MiB/s) 7037480 bytes read in 648 ms (10.4 MiB/s) Found mainline kernel configuration 32098 bytes read in 742 ms (42 KiB/s) 504 bytes read in 990 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 504 bytes read in 1000 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo 804 bytes read in 918 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-spi-jedec-nor.dtbo 4179 bytes read in 837 ms (3.9 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8302878 Bytes = 7.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49814000, end 49fff11e ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 497a3000, end 49813fff ... OK Starting kernel ... Loading, please wait... starting version 237 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.31.1 [/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1 /dev/sda1: clean, 35997/445440 files, 230089/1879068 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Ubuntu 18.04.1 LTS! Ubuntu 18.04.1 LTS orangepizero ttyS0 orangepizero login:
  13. @tpc010 unfortunately my A33 tablet, does not start at all from sdcard no matter what A33 image or u-boot i try. fel-storage does not work for me either, so im stuck NeonNiQ NQT-7W tablet from South Africa, running Android 5.1 7inch 1024x600, 512mb ram, 8Gb storage
  14. You will also find some USB flash drives work (respond quicker) better than others for USB booting from u-boot .