• Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by sgjava

  1. @Keeratiglad to hear that. What properties file did you use with MMIO?
  2. @KeeratiI replied to your post on github. The input file is for MMIO GPIO mappings and not used by LedBlink. Use --help argument on any demo or tool for list of arguments such as gpio chip, pin, etc.
  3. @DorisSmithI'm using since they are about the cheapest 4K camera you can get. I have 6 of them in use. Make sure you check the coupon and save $40. Works out to about $70 US. That's the easy part. Setting up a homemade NVR is more difficult, so you may want to look at some of the existing NVR packages out there.
  4. This is a follow up based on running my cameras for a few months. While setting up a new XU4 and copying a file I noticed the same lockup issue. The heartbeat still going but internal and USB NIC dead. I set usbstoragequirks for the SSD drive to u and now I'm able to copy multi-gig files without this issue. Of course SSD performance is less, but I still have plenty of bandwidth. I will monitor long term.
  5. armbianEnv.txt is missing from latest XU4 focal image Armbian_21.08.5_Odroidxu4_focal_current_5.4.159_minimal.img. Should I just create on or use boot.ini?
  6. @lanefuI love the device tree (the one with the boards welded on). I ended up using a storage box with little drawers I got off Amazon and made the cut outs with a rotary tool. This was right after I had it complete. Those Android sticks were quad cores running Linux. That's how I started before most SBCs were sold. Note the active cooling
  7. Java UIO provides high performance Java interfaces for Linux Userspace IO. Java UIO was built from the ground up to use modern kernel APIs, libraries and code generation techniques to provide a best of breed cross platform approach. It does not make sense to recreate the wheel like so many other IO libraries. JDK 17 LTS is supported out of the box. I've been committing code to U8g2 that utilizes the same userspace code at the C level and dramatically improved the performance of HW/SW SPI and I2C in the arm-linux port. I also made the arm-linux port thread safe and multi display capable (you can use this in C as well obviously). It made sense to add modularization to the Java Periphery IO library since I can take advantage of the same code generation techniques. I will continue to wrap optimized C libraries moving forward in the same modular fashion. So now you can develop against IO and small displays with one code base in Java.
  8. OK, so I tried console=none, the getty disable ttyS0 trick, etc. Most of the posts indicate you need to make a change and recompile the kernel. I don't have time for that, but for multi function pins this should work like it did in the previous releases.
  9. @WernerOK, I finally figured this out and it's not my wiring job What's happening is the Duo uses DRX pin (debug receive) for PWM, so if I wire up a LED it will not boot. If I remove that wire it will boot up. After it boots I can connect wire and it will work as expected, so something changed in Armbian_21.08.1_Nanopiduo_focal_current_5.10.60.img. I suspect that no one noticed this unless they were doing hardware PWM, I guess I need to disable serial console?
  10. OK, found root cause. I had a board wired up with all kinds of test devices, loopbacks, etc. My bad, sorry about that. I can fire up debug console now as a result. Still not sure why other version would boot though.
  11. Damn thing booted Armbian_21.08.1_Nanopiduo_focal_current_5.10.60.img. Let me try this on the board I had an issue with and the same SD card. At least I know how to grab boot log now
  12. OK, have FriendlyElec Matrix USB to TTL logging with working image. Let me try broken one and capture.
  13. OK, let me try the easy way with USB UART, but I also found I have a kicking around. Give's me a use for it if easy method doesn't work. And good thing I have 4 Duos because 3 are already on breadboards in use.
  14. So on a normal boot I can putty into Duo using USB serial. Are you saying I need adapter that uses debug pins? i.e.
  15. Armbian_21.05.1_Nanopiduo_focal_current_5.10.34.img boots (updating via apt upgrade also causes it not to boot any more) Armbian_21.08.1_Nanopiduo_focal_current_5.10.60.img does not When I examine the SD card it hasn't expended from image (makes sense since the heartbeat never starts).
  16. PA18\0PA19 and E12\0PE13 do not seem to map to pins.
  17. Found it in DTB i2c0-pins { pins = "PA11\0PA12"; function = "i2c0"; phandle = <0x1c>; }; i2c1-pins { pins = "PA18\0PA19"; function = "i2c1"; phandle = <0x1d>; }; i2c2-pins { pins = "PE12\0PE13"; function = "i2c2"; phandle = <0x1e>; };
  18. So in armbian-config I can enable /dev/i2c-0 /dev/i2c-1 /dev/i2c-2 but there is only one hardware I2C onboard. Are the other two software driven? If so what pins do you use for SCL and SDA?
  19. How is i2c1 and i2c2 mapped on Nanopi Duo? I can configure in armbian-config, but all the Duo pin diagrams only show i2c0.
  20. How is i2c1 and i2c2 mapped on Nanopi Duo? I can configure in armbian-config, but all the Duo pin diagrams only show i2c0.
  21. Java U8g2 is a high performance library based on U8g2: Library for monochrome displays, version 2. Rather than try to code the JNI by hand I used HawtJNI to generate the JNI wrappers. I also used some custom code to generate the setup methods and font constants. final var u8g2 = U8g2.initU8g2(); // Change this to your actual display U8g2.setupSsd1306I2c128x64NonameF(u8g2, U8G2_R0, u8x8_byte_arm_linux_hw_i2c, u8x8_arm_linux_gpio_and_delay); U8g2.initDisplay(u8g2); logger.debug(String.format("Size %d x %d, draw color %d", U8g2.getDisplayWidth(u8g2), U8g2.getDisplayHeight(u8g2), U8g2. getDrawColor(u8g2))); U8g2.setPowerSave(u8g2, 0); U8g2.clearBuffer(u8g2); U8g2.setFont(u8g2, u8g2_font_t0_15b_mf); U8g2.drawStr(u8g2, 1, 18, "Java U8g2"); U8g2.sendBuffer(u8g2); try { TimeUnit.SECONDS.sleep(5); } catch (InterruptedException ie) { Thread.currentThread().interrupt(); } U8g2.setPowerSave(u8g2, 1); U8g2.done(u8g2);
  22. Tried to flash a couple of times, but it never makes it to the heartbeat led. Will try other releases. This one boots
  23. Java Periphery is a high performance library for GPIO, LED, PWM, SPI, I2C, MMIO and Serial peripheral I/O interface access in userspace Linux. Rather than try to build this from scratch I used c-periphery and HawtJNI to generate the JNI wrappers. This saves a lot of hand coding and allows for easier synchronization with c-periphery changes moving forward. I believe this is the only userspace IO library that supports the new JDK 17 LTS (and still supports JDK 11). I had to fork HawtJNI to make it work with JDK 17. The only caveat is that ARM32 supports JDK 11. For some reason I cannot find a JDK 17 for ARM32 or information on why is was not supported. The install script handles this automatically. ARM64/x86/x86_64 uses JDK 17.
  24. I agree, but I went with Annke 4K cameras at around $80 US. So far, so good.
  25. I'm running the latest XU4 focal and ffmpeg doesn't support the latest H265+ codec even though I'm only doing a copy (no transcoding). Is there a way to build latest ffmpeg without losing hardware accelration? [rtsp @ 0x556f60] [warning] Multi-layer HEVC coding is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. BOARD=odroidxu4 BOARD_NAME="Odroid XU4" BOARDFAMILY=odroidxu4 BUILD_REPOSITORY_URL= BUILD_REPOSITORY_COMMIT=428a20876-dirty DISTRIBUTION_CODENAME=focal DISTRIBUTION_STATUS=supported VERSION=21.05.6 LINUXFAMILY=odroidxu4 ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=Image BRANCH=current