Vladimir Petrovic

Thanks man. I did not saw that. All work no play makes jack a dull boy. Tnx again. Послато са Redmi Note 6 Pro уз помоћ Тапатока

Nothing in dmesg. Had to see.u-boot. When I get that log I will post. Thou I got segmentation fault on dpkg and when I replaced bin fom a pckage it started working again. Could be sdcard? Послато са Redmi Note 6 Pro уз помоћ Тапатока

verbosity=1 logo=enabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=f2be4c3e-fb7c-4a81-b3db-f29ff41e7bdf rootfstype=ext4 overlays=analog-codec cir i2c0 i2c1 i2c2 pps-gpio pwm spdif-out spi-spidev uart1 uart2 uart3 usbhost0 usbhost1 usbhost2 usbhost3 w1-gpio param_spi_dev_bus=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Послато са Redmi Note 6 Pro уз помоћ Тапатока

Orange pi one refuse to add spi to /dev/. It's 5.73 armbian kernel 4.19.20-sunxi. I've activated spi dev from armbian-config but no device after reboot. Gpio and i2c work great . Anyone had problem like this? Послато са Redmi Note 6 Pro уз помоћ Тапатока

can you suggest any android image for testing if camera module is not fried? Also i figured out that twi addres does not want to change in bin file made from edited fex. When I write 0x78 in fex it compile to 120 (done bin2fex again on bin file I've created from modified fex)

Hi, Sorry for bringing this topic from dead but I have some problems with ov5640. I bought this camera module : https://www.aliexpress.com/item/OPI-5MP-Camera-OV5640-Auto-zoom-with-wide-angle-lens-for-Orange-Pi-PC-Pi-One/32869355445.html?spm=a2g0s.9042311.0.0.2ac84c4d4jeaqv and I connected it to Orange Pi One. I've isntalled lts 16 image with kernel 3.4.113 and I've loaded ov5640 kernel and vfe_v4l2 modules. I dont get /dev/video0 device and have this otput from kernel.log: [OV5640@lex]init_sensor - frame_rate: 0, max_win_size: 11 [ISP] isp platform_id = 5! [OV5640@lex]CSI_SUBDEV_PWR_ON! [OV5640@lex]sensor_init 0x0 [OV5640@lex]sensor read retry=2 [OV5640@lex]error at sensor_detect [OV5640@lex]chip found is not an target chip. [OV5640@lex]CSI_SUBDEV_PWR_OFF! what could be wrong? Do I have to swap R6 and r5 on this board?

look's like u-boot does not recognise usb2sata controler on NAS expansion board for opi0. Any idea how to correct this? Is it even possible?

So legacy is a choice? Can I get ov5640 work in legacy ubuntu on opi one?

Can somebody confirm that this driver work on mainline opi0 kernel? https://github.com/avafinger/ov5640

So it's usb sata... I think I know what I missed in instalation. I've dd if=soruce of=/dev/sdxx but I've did not set boot flag on partiton so that's why it does not boot from the hdd. I'll check today if I can boot it bringing boot flag to hdd. I have UART deug console attached to RPI0 . Tnx.

I've found this: https://github.com/lentinj/u-boot/blob/master/doc/README.sata . Look's like it's possible. Anyone correct me if I'm wrong.

Is it possible to boot Orange pi Zero directly from hdd. I have sata hdd attached to OPI Zero via PI NAS. I can boot from usb flash and use HDD as root device but faild to boot from HDD directly. Is it possible to do this or not.

Ok. Tnx. Job Done.

so I can push bin like this to spi flash: flashcp /usr/lib/linux-u-boot-next-orangepizero_5.38_armhf/u-boot-sunxi-with-spl.bin /dev/mtd0 ?

I've added spidev overlay: Found mainline kernel configuration 31935 bytes read in 1273 ms (24.4 KiB/s) 504 bytes read in 795 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 504 bytes read in 891 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo 780 bytes read in 878 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-spi-spidev.dtbo 804 bytes read in 834 ms (0 Bytes/s) Applying kernel provided DT overlay sun8i-h3-spi-jedec-nor.dtbo 382 bytes read in 373 ms (1000 Bytes/s) Applying kernel provided DT overlay sun8i-h3-cir.dtbo U-Boot SPL 2017.11-armbian (Jan 25 2018 - 08:04:30) DRAM: 512 MiB Trying to boot from MMC1 But no /dev/spidev0.0 . What I'm doing wrong? kernel is : Linux orangepizero 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l GNU/Linux

Still no luck to update u-boot on SPI flash. If I'm not in wrong spi device is in mainline kernel /dev/mtd0. cat /proc/mtd dev: size erasesize name mtd0: 00200000 00001000 "spi0.0" When I try to write : dd if=/dev/zero count=4096 bs=1K | tr '\000' '\377' > spi.img dd if=/usr/lib/ linux-u-boot-dev-orangepizero_5.38_armhf /u-boot-sunxi-with-spl.bin of=spi.img bs=1k conv=notrunc everything goes fine but when I execute write to chip flashrom -p linux_spi:dev=/dev/mtd0 -w spi.img I get this error: Calibrating delay loop... OK. linux_spi_init: failed to set SPI mode to 0x00: Inappropriate ioctl for device Error: Programmer initialization failed. What I'm doing wrong?

Do I need to boot with Debian 9 image with mainline kernel from sdcard to see spi flash and then udgrade u-boot on it because it's old u-boot on SPI flash right now. That look's like only solution to se SPI flash to update with new u-boot for mainline kernel.

Ok, I've activated spi-add-cs1 spi-jedec-nor spi-spidev and still no luck to find spi flash. sunxi-fel spiflash-info return : ERROR: Allwinner USB FEL device not found! also can not find /dev/spidev0.0 as on legacy kernel. Any clue? Do I need some params for spi-spidev and spi-jedec-nor?

Can not find spi flash in /dev/ where can I find it on Debian 9?

Hi, Have a problem with Orange Pi Zero on Armbian Mainline kernel . It's based on Debian 9. It's Linux orangepizero 4.14.14-sunxi .

Ok tnx. I'll check that today.

Hi, I have a problem to comunicate with sim800l via UART3 or any other UART. Is there way to activate UART3 on Linux PiOne 4.14.18-sunxi kernel if it is not already activated. I could find DTB files but I do not know how to view them or transfer to DTS and read/modify them to se if there could be a problem. I'm using pins 8 and 10 for UART3 on 40Pin header and try to comunicate with putty and screen over /dev/ttyS3 but no luck. Any idea what is going on? Sim800L works fine over pl2303.

I've managed to build kivy on OrangePi Zero. Dependency need cython 0.25.2 for successful build.

cythoning /tmp/pip-build-EOjUJ7/kivy/kivy/graphics/svg.pyx to /tmp/pip-build-EOjUJ7/kivy/kivy/graphics/svg.c Error compiling Cython file: ------------------------------------------------------------ ... end = time() Logger.debug("Svg: Loaded {} in {:.2f}s".format(filename, end - start)) finally: fd.close() cdef void reload(self) except *: ^ ------------------------------------------------------------ kivy/graphics/svg.pyx:469:9: Signature not compatible with previous declaration Error compiling Cython file: ------------------------------------------------------------ ... cpdef flag_update(self, int do_parent=?, list _instrs=?) ELSE: cpdef flag_update(self, int do_parent=?) cdef void flag_update_done(self) cdef void set_parent(self, Instruction parent) cdef void reload(self) ^ ------------------------------------------------------------ kivy/graphics/instructions.pxd:36:20: Previous declaration is here Any idea?