All Activity

This stream auto-updates     

  1. Past hour
  2. Thank you, for the link. This "framework" is very cool. I,ve installed and try a first build, but i don't find where I can choose drivers. I 'll try again tomorrow ..
  3. Fair enough. It depends on how I configure the routing, to be sure. This is going to be much more capable than a raspberry PI in a like configuration which was the other likely candidate. While I could configure a PI4 as a single-armed router, the EB design provides for more direct routing configuration.
  4. After running: $ sudo dd if=SPL.sdhc of=/dev/sde bs=1K seek=1 status=noxfer $ sudo dd if=u-boot.img.sdhc of=/dev/sde bs=1K seek=69 status=noxfer U-boot seems having well been updated! But it does not boot, it is looping like this: U-Boot 2018.01-armbian (Jul 07 2019 - 11:26:59 +0200) CPU: Freescale i.MX6Q rev1.2 1200 MHz (running at 792 MHz) CPU: Extended Commercial temperature grade (-20C to 105C) at 33C Reset cause: POR Board: MX6 Cubox-i Watchdog enabled DRAM: 2 GiB U-Boot SPL 2018.01-armbian (Jul 07 2019 - 11:26:59) Trying to boot from MMC1 Why MMC1?? armbianEnv.txt: verbosity=7 rootdev=UUID=4a9f4e28-6a2f-4a58-b21a-8b0582b90cd5 console=serial usbstoragequirks= boot.txt: setenv bootargs root=UUID=4a9f4e28-6a2f-4a58-b21a-8b0582b90cd5 rootfstype=ext4 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi ahci_imx.hotplug=1 consoleblank=0 vt.global_cursor_default=0 quiet ext2load mmc 0 0x18000000 /boot/dtb/${fdt_file} ext2load mmc 0 0x12000000 /boot/zImage bootz 0x12000000 - 0x18000000 boot.cmd is the default one. Shouldn't I do something with the other files which are in the deb? SPL.emmc SPL.sata SPL.spi-flash u-boot.img.emmc u-boot.img.sata u-boot.img.spi-flash I wanna boot on /dev/sda...
  5. Hai @lex In my orange pi pc2, i'm load sun6i_csi and ov5640 module on boot. Now to connect ov5640, need adjust DT Script. Can i see DT Script for ov5640 ? I already tried to adjust DT but on dmesg, i see error : ov5640_read_reg: error: reg=300a. how to fix this ?
  6. Today
  7. The Emulator compiled even on a Pinebook A64, but is slower than on the NanoPi K1 Plus
  8. Yes of course. I completely forgot about Here is the recipe: https://github.com/armbian/build/blob/master/config/sources/cubox.conf#L48-L52 Sometimes order is also important ...
  9. Ok, did it. Now, on the console (via USB-TTL serial console) I have only: U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42) Boot Device: SD1 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42) Boot Device: SD1 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42) Boot Device: SD1 spl: error reading image u-boot.img, err - -1 Load image from RAW... Should I try updating also the "SPL.sdhc" using: sudo dd if=SPL.sdhc of=/dev/sde bs=1K seek=1 status=noxfer
  10. 1234 https://github.com/armbian/config/blob/master/debian-software#L426
  11. https://docs.armbian.com/Developer-Guide_Build-Preparation/ kernel + dtb and u-boot come out deb packaged. You install them on the target and that's it. Only u-boot needs a special treatment - it used to update this way in the past but due to the problems we move it under manual update -> armbian-config -> system -> install/update boot loader ... for this case you don't need to update boot loader. Just remember to install image and dtb package. This is essential.
  12. @dasbee - "saturate the ethernet links" but there's only a single gigabit SERDES to the ethernet switch, so any traffic that has to go to the CPU is limited below the 1 Gbps of the ethernet links.
  13. Hi there, I'm currently struggling to get the Cedrus VPU up and running. I have downloaded the specific version from bootlin and got the kernel up and running, however the V3s isn't supported by the Sunxi SRAM driver. This driver is important to get the VPU going. I tried altering the devicetree of the V3s to match a SoC that is somehow similiar, but it clearly failed for obvious reasons. I get this error message: [ 1.035259] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 1.040990] cedrus 1c0e000.video-codec: Failed to probe hardware [ 2.478247] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 2.484047] cedrus 1c0e000.video-codec: Failed to probe hardware [ 2.505765] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 2.511591] cedrus 1c0e000.video-codec: Failed to probe hardware [ 8.595278] cedrus 1c0e000.video-codec: Failed to claim SRAM [ 8.601112] cedrus 1c0e000.video-codec: Failed to probe hardware I tried to understand whats going on in the linux/drivers/soc/sunxi/sunxi_sram.c file to adapt this driver to the V3s, but in the end I don't know how to do that. I hope somebody can help me with that or can give me a hint.
  14. RPI does not have any internal storage, it boots mainly on the SD card, I did not change any partitions, I just described the partitions in the dtb file to match the original dtb, I think that the kernel does not see the /dev/system partition, I don't know why, here the modified dtb file that I have updated, not the original one. gxl_p281_1g.dts
  15. Wifi device not ready fix by copying from previous version fw_bcm4356a2_ag.bin & nvram_ap6356.txt into /lib/firmware/brcm
  16. Oh i think you use the SD cards indeed al little bit (mean a lot!!) more intensive then i should do. Otherwise is in the dashcam's my idea also that the Samsung's has a longer lifetime than the Sandisk. But i agree with you: the only correct way to check it is to buy a lot and do all the same things and see how long the SD cards live. Offcourse with originals. But even then could there be a bad batch of a brand... 'SD cards are consumable items' do i read somewhere on the internet. And i think we should agree. Btw: is the lifetime of a onboard eMMC better than a SD card?
  17. Usb works because i see my devices with lsub. The rfxcom serial devices et bluetooth dongle are not created under /dev... I didn't try testing the zwave dongle. So does a tutorial exists to compile an armhf kernel and install it with u-boot (i will do it under x86 station)... Regards,
  18. Hi all, When i trie to install ISPconfig with softy all goes very well. And when the installation is finished i should be login on https://orangepi-PC:8080/login/index.php . But every what i trie (i read it should be admin/admin at the first start) nothing worked to login. Does anyone know what is the default password or what is the problem van not loging in? Kind regards!
  19. I got such a problem (waiting for root device) with a RPi 3B after recreating partitions on a SDCard for getting a bigger partition 1 (FAT32) and restoring the old contents. While creatng the new partitions they do get a new PARTUUID, which is configured in /etc/fstab (and on the RPi 3B also in /boot/cmdline.txt). With the command blkid I searched for the IDs and did put the new value in /etc/fstab. After that my RPi 3B did boot properly from the new created SDCard. Here my sample: root@rpi3-aiy(192.168.6.206):~# more /etc/fstab proc /proc proc defaults 0 0 PARTUUID=21fbfeb1-01 /boot vfat defaults 0 2 PARTUUID=21fbfeb1-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for that
  20. Hello, I have bought an x96mini with a uboot version from 03/2019, everythings works perfectly when booting from SD, but when I try to boot from internal the kernel boots and it stops at "waiting for root device", after an investigation I have noticed that the partitions layout is different from the standard one, I have updated the dtb to be inline with that layout but the problem remains the same, unable to boot from internal. Here is the original dts file from that box, Any help would be appreciated, knowing that I am using the kernel version 3.14. Thanks, 01_dtbdump_Amlogic.dts
  21. That's all. You need a superuser rights ofc.
  22. Maybe someone here knows the 8-Bit Guy and the project of his Dream-Computer - the Commander X16 You could see the actual state of the real hardware at YT-Video from the 8-Bit Guy: (Building my Dream Computer - Part 2) https://www.youtube.com/watch?v=sg-6Cjzzg8s Since the hardware isnt ready/completed yet there is a Emulator which uses SDL2 and can be compiled now (since r30) also on Linux ARM Github-page of the emulator: https://github.com/commanderx16/x16-emulator https://github.com/commanderx16/x16-emulator/releases Source: https://github.com/commanderx16/x16-emulator/archive/r30.zip or https://github.com/commanderx16/x16-emulator/archive/r30.tar.gz Linux-Binary for PC including the 2 ROMs: https://github.com/commanderx16/x16-emulator/releases/download/r30/x16emu_linux-r30.zip libsdl2-dev hasnt to be compiled from source for armbian, because we have already a installable package and the runtime libsdl2-2.0-0 is already installed in the desktop image. For compiling the Emulator I used on my NanoPi K1 Plus a fresh compiled (with armbian-build-system) dev-image: Armbian_5.97_Nanopik1plus_Debian_buster_dev_5.3.0-rc8_desktop For to have all programs for compiling the application I did use sudo apt install gcc git make libsdl2-dev zip unzip -y Then we do create a directory and download the source and extract it: mkdir x16 cd x16 wget https://github.com/commanderx16/x16-emulator/archive/r30.tar.gz tar -xvf r30.tar.gz Now we change in the newly created directory and do compile with make: cd x16-emulator-r30/ make For running the emulator we do need the 2 ROMs chargen.bin and rom.bin out of the archive https://github.com/commanderx16/x16-emulator/releases/download/r30/x16emu_linux-r30.zip in the same directory as the compile x16emu binary. Now we can run the emulator (here with german keymap): ./x16emu -keymap de Unfortunately the emulator doesnt run very fast, do use only one CPU-core and hasnt idle-support - so the CPU will get really fast very hot (70 Degree). A AMD Phenom II X4 with 4x3GHz max. is about 2 times more faster (100%+200%=300%) than the X16 on the NanoPi K1 Plus X16_r30_ROMs.zip
  23. original dtb - system start, but no ethernet meson-gxl-s905x-p212.dtb - system not start meson-g12a-x96-max.dtb - system start, but no ethernet
  24. Which DTB have you tried? meson-gxl-s905x-p212.dtb?
  25. a short update on my rk3318 tv box (h96 max rk3318 2/16G) excursion in short: simply avoid those boxes in detail: i tried to boot armbian rk3288 tv box & rock64 images, the original rock64 image and the libre ROC-RK3328-CC image - none of them worked ... then i tried to get into maskrom mode of the box, tried all the test points on the board but none worked, the heavy way of zeroing the emmc worked of course and i'm in mask rom mode now and can boot from sd card without any interference from the installed loader on emmc - i tried to boot the above mentioned images again: no way (with different error scenarios, but non of them really looking promising), i built atf and u-boot from sources too, but this failed as well - some other experiments failed too - all in all i do not see any way right now to get linux booted in an easy way on it ... besides that the rk3318 hardware seems to be way lower speced than rk3328: on android the cpu frequency scaling only went up to 1.1ghz and there seemed to be only two mali pp cores enabled (just like on the rk3328) - so no gain at all of the rk3318 over the rk3328 - in the end better stick to rk3328 boxes instead trying your luck with rk3318 ones ... best wishes - hexdump
  26. Finally solved this issue. The first thermal zone tripping point is at 70C with a hysteresis of 10. One would expect to kick a throttle in at 70C and lift the throttle at 60C. However throttling occurs at 60C. So I adapted a script found elsewhere and raised the first two tripping points. echo 'setting cpu temperature limits ...' i=0 while [ $i -lt 4 ]; do sudo bash -c "echo \"85000\">/sys/devices/virtual/thermal/thermal_zone""$i""/trip_point_0_temp" sudo bash -c "echo \"95000\">/sys/devices/virtual/thermal/thermal_zone""$i""/trip_point_1_temp" i=$[$i+1] done
  27. I have a Magicsee N5 Max box, which version work with ethernet? Which DTB? I'm trying but ethernet doesn't work ...
  1. Load more activity