Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Today
  2. 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
  3. 1234 https://github.com/armbian/config/blob/master/debian-software#L426
  4. 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.
  5. @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.
  6. 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.
  7. 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
  8. Wifi device not ready fix by copying from previous version fw_bcm4356a2_ag.bin & nvram_ap6356.txt into /lib/firmware/brcm
  9. 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?
  10. 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
  11. 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
  12. 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
  13. 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
  14. Yesterday
  15. I have two boards of nanopi-a64. after following the instructions here to enable usb and hdmi audio, i've tried also making the audio jack working (at least for audio output). I did the inclusion of a custom board config as stated in post #1 of this thread. Here is my patch file I add to <armbian-build-path>/patch/kernel/sunxi-dev/ I named it xxx-xxx-nanopi-a64-fix-usb-and-audio.patch so that it would be executed last on the patching stage of the build. diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-nanopi-a64.dts b/arch/arm64/boot/dts/allwinner/sun50i-a64-nanopi-a64.dts index 9b9d915..0b671c7 100644 --- a/arch/arm64/boot/dts/allwinner/sun50i-a64-nanopi-a64.dts +++ b/arch/arm64/boot/dts/allwinner/sun50i-a64-nanopi-a64.dts @@ -283,3 +283,48 @@ &usbphy { status = "okay"; }; + +&codec { + status = "okay"; +}; + +&codec_analog { + cpvdd-supply = <&reg_eldo1>; + status = "okay"; +}; + +&dai { + status = "okay"; +}; + +&i2s1 { + status = "okay"; +}; + +&i2s2 { + status = "okay"; +}; + +&sound { + simple-audio-card,aux-devs = <&codec_analog>; + simple-audio-card,widgets = "Microphone", "Microphone Jack", + "Headphone", "Headphone Jack"; + simple-audio-card,routing = + "Left DAC", "AIF1 Slot 0 Left", + "Right DAC", "AIF1 Slot 0 Right", + "Headphone Jack", "HP", + "AIF1 Slot 0 Left ADC", "Left ADC", + "AIF1 Slot 0 Right ADC", "Right ADC", + "MIC2", "Microphone Jack"; + status = "okay"; +}; + +&sound_hdmi { + status = "okay"; +}; + +&usb_otg { + dr_mode = "host"; + status = "okay"; +}; + Adding it at the patching stage avoids having to decompile and recompile into dtb and replacing the one at the boot. So far so good, audio on hdmi and the audio jack works, you just have to set the default sink device on pulse audio's settings if you want to use either audio outputs. Be aware though that is needed to hold the linux-dtb-dev-sunxi and linux-dtb-dev-sunxi64 packages so that the patches above wont be lost when running apt-get upgrade.
  16. I done some test with a bananapi M1 with Armbian_5.91_Bananapipro_Debian_stretch_next_4.19.59 In this case, the display working
  17. In case, both IP address are static, write your your DNS sever in /etc/resolv.conf : nameserver 'dns_IP_address' If one IP address from DHCP, network-manager will re-write resolv.conf with data from DHCP If the DNS from DHCP is not good, you must fix a static address one each interface and write manually resolv.conf What is this ?????? internet access blocking port 80 and 443 Are you sur port 8000 or 8001 are open ; for user, prefer port 8080, some internet browser block no standard port ( i have had this problem with port 8000 and must move to 8080 ) For the firewall, normally all Armbian have installed IPTABLES ( il the native linux firewall ) but it's only on command line I never used webmin but i think it said "not installed" because there are not filtering rules https://doxfer.webmin.com/Webmin/Linux_Firewall
  18. @lex

    Updated htop

    According to this: https://github.com/armbian/build/blob/master/packages/bsp/helios4/90-helios4-hwmon.rules , it is not related to CPU temp. My guess is just a missing kernel config.
  19. thanks anyhow. I feel I'm so close with the description stating that the file need to be there and that is it. And I have the file there and it is not working but showing up in a different color.
  20. @Igormaybe we need ony a "old" fix-commit again for his device? https://github.com/armbian/build/commit/76ac54aae381714cee7bf1b03d4bce097b1630de
  21. Do you use Armbian? We do have an "universe" repository where this package come from: https://github.com/armbian/build/blob/master/lib/general.sh#L153-L163 https://packages.ubuntu.com/bionic/usbmount
  22. I did. Once again: You are referring to a wrong documentation and asking why it doesn't work. It is expected to fail and I told you that. (now the 3rd time and last time) Read this to understand background: https://linux-sunxi.org/GPIO Step by step documentation? I don't know if it exists. I will not search it nor make it for you - you have to invest your own time with the essential information which you got here.
  23. Last week
  24. IIRC AXP driver in modern kernel has limited functionality. Not on the level as legacy ... but nevertheless you can communicate with AXP via I2C ... there are some manuals for this (Google) I would say this is simply a bug. But where? There are no logs, we don't have this hardware, we don't use this kernel ... This is how you check if you run official Armbian which we can try to support: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity
  25. tomsolo

    NanoPI M4

    thanks everyone! Another question: netflix in browser is working too?
  26. I assume that you want to start Linux from SD card instead of SATA, right? This is different from loading the board firmware form SD card instead of SPI flash. The firmware should be able to boot Linux from any device, no matter where the firmware is actually stored. You may post the u-boot environment (the output of `printenv`) here.
  1. Load more activity