• Content Count

  • Joined

  • Last visited

About gufmar

  • Rank

Recent Profile Visitors

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

  1. I tested this on multiple v1.3 and 1.4 Boards In the boot sequence the message appears. `A start job is running for Bluetooth Rockpi (3min 1s / no limit)` The boot process continue for other tasks but never completes, even after waiting for hours. All boards boot fine with 20.08
  2. loving this Armbian forum and community. It works great! TYVM
  3. I try to build a customized image as described in and by using the template with the OpenMediaVault example The goal is to build an image who auto-execute an initial setup script after being flashed and frist boot. The device has connected RGB-Leds and an OLED I2c Display on the GPIO pins. It should give color signals durring this initial setup, and then show system parameters (especially the
  4. Yes most of all my boards run on eMMC (just started experimenting with the NVME extension) I never noticed a difference between A and B regarding eMMC behaviour. I'm not sure if it is related (or my mistake) but 3 from my 8 eMMC cards are not recognised anymore at full size. As they appear with onle 1/8 of size, I guess it is some mistake between 4096 and 512 sector size, happened either on disc resizing after boot, or re-flashing with etcher (on a notebook with weird SDCard driver) I wasn't able to bring them back to original capacity with whatever operating system, device and par
  5. Is this something related to the overlay file, or where do I have the chance to play with this value? By using the python spidev library I can set something like spi.max_speed_hz=10000000 But I can't see any effect. Also spi.xfer has some factor and it looks like it depends a bit on the HW, wiring and CPU components spi.xfer(tx.tolist(), int(4/1.25e-6)) #works, on Zero (initially didn't?) #spi.xfer(tx.tolist(), int(4/1.20e-6)) #works, no flashes on Zero, Works on Raspberry 3 #spi.xfer(tx.tolist(), int(4/1.15e-6)) #works, no flashes on Zero #spi.xfer(
  6. still some fine-tuning required but .... it works !
  7. yes. First kernel compilation in my life, worked fine, with expert mode (at least afaik for now ;- ) no, will do this evening. I wasn't sure if I need to do this as for I2C in the dts/dtb file (okay) or somewhere else. Thanks.
  8. ok, whatever I did, the flashed eMMC booted up and run fine. But there is still no /dev/spi* device. Do I need to enable it in the .dts file and recompile to to dtb (similar as with i2c devices) ?
  9. TIL: there are many branches. thanks. will try my best.
  10. This sounds great! So I while waiting the setup of my new armbuilder vm, I read through the and and wonder if I need some special options set or if I can just go with defaults? (I checked out the build repo after your two commits, but as far as I can see it's master, not DEV branch)
  11. Instead of breaking the (bright) onboard LED's it might be a good idea to use some small piece of black tape. This topic is interesting because I'm also currently working on LEDs on the RockPi. The very bright green LED is very well suited to make the logo appear in a 3d-printed case. But it can only light up in one colour. A first problem arises when the M.2 NVME adapter board is screwed on top and hides the green light. I could connect an RGB LED (cathode) to the GPIOs. But it would need 3 digital (PWM) pins. So I looked at the small WS2812 LED modules. The
  12. The buster image boots up, and has both Ethernet and Wifi devices enabled. But no IP packets leave or reach the board, trying both dhcp or static setup, on ipv4 and ipv6. Ping shows destination unreachable msgs. Eth0 interface shows up in desktop GUI as well as armbian-config tool and with ip interface command Switching to an eMMC with bionic image works fine.
  13. I have a and b versions in my lab (all 4GB equipped) Do you still need some confirmation/verification?