hallo1

  • Content Count

    12
  • Joined

  • Last visited

About hallo1

  • Rank
    Member

Recent Profile Visitors

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

  1. sd and emmc are not present. The radxa's image have been flashed to the optane memory. But actrually the content inside the optane memory don't have much to do with this error. EVEN A BLANK OPTANE MEMORY CAUSES THIS ERROR.
  2. Intel Optane memory M10 16GB is NOT working. Here is some log. U-Boot TPL 2020.07-armbian (Dec 23 2020 - 15:30:05) Channel 0: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB Channel 1: LPDDR4, 50MHz
  3. /dts-v1/; /plugin/; / { compatible = "radxa,rockpi4b", "radxa,rockpi4", "rockchip,rk3399"; fragment@0 { target = <&spi2>; __overlay__ { status = "okay"; }; }; fragment@3 { target = <&pinctrl>; __overlay__ { st7735rdisplay { st7735r_display_pins: st7735r_display_pins { rockchip,pins = <4 26 1 &pcfg_pull_none>, //GPIO4_D2 (A->
  4. My testing result: (U-Boot 2020.07-armbian (Dec 12 2020 - 01:58:01 +0100)) SD card boot: Working (absolutely) NVMe boot: Working (on my ssd w/ sm2263xt controller) USB boot: Working (bad compability, the upper usb3.0 port seems won't work) PXE boot: Untested (but networking seems okay) EMMC boot: Untested SPI Flash read/write: Working HDMI: Working (tested 1920x1080) USB keyboard: Not working(can be detected but not working)
  5. Here is the output of the logic analyzer (kernel ~5.4). You can open it using the pulseview software. under linux mainline 5.4.sr
  6. That is not a I2C speed issue. I examined the i2c data of the OLED using a logic analyzer and found the i2c clock is both 100KHz (maybe a little slow but reasonable)
  7. I2cdetect works properly, showing a device at address 0x3c I'm using superuser permission to execute the script. If there is a permission issue, it will show a error message "permission denied" Sometimes the display will light up and show proper content, but the script will still run into this error after ~3s.
  8. I am using a orangepi win plus. I have attached a ssd1306 OLED display to the board, using i2c1 interface, using the luma.oled library as driver. import sys from PIL import Image from PIL import ImageDraw from PIL import ImageFont import subprocess from luma.core.interface.serial import i2c from luma.core.render import canvas from luma.oled.device import ssd1306, ssd1325, ssd1331, sh1106 from time import sleep serial = i2c(port=1, address=0x3C) device = ssd1306(serial, rotate=0) width=device.width height=device.height image = Image.new('1', (device.width, device.height)) # Get draw
  9. Output is here: http://ix.io/28uM Sadly, my board's HDMI output have been damanged by static electricity when I get the output. Probably it will cause wrong information.
  10. I connect the rockpi 4 to a Samsung display whose normal resolution is 1680x1050 via a hdmi to dvi line, but the maxium resolution I can choose is 1280x1024. And when I connect it to a 4K tv via hdmi, the maxium resolution is 1920x1080, not 3840x2160. The legacy kernel (4.4.210) works perfectly in both cases.
  11. Thank you! bootloader now works normally without any storage device connected.
  12. I am using an Orange pi win plus (Allwinner A64, 2GB ram), running Armbian Bionic with Linux 5.3.9-sunxi64 The board has an 2MB on-board spi flash and I want to flash bootloader in it. The spi flash can be correctly detected in the system (showing /dev/mtdblock0). But the "install" tool in armbian-config can't install the bootloader into the flash. When I selected "Install/Update the bootloader on SPI Flash" and confirmed the warning notice, the tool printed "OK" immidiately and there is actually nothing written to the flash. After using "sudo bash -x arm