ehelfer

Members
  • Content Count

    11
  • Joined

  • Last visited

About ehelfer

  • Rank
    Member

Recent Profile Visitors

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

  1. Hi Igor, Thanks a lot, I think it works now, the connector was a bit loose, that's why it was unstable. I'll bought a new one.
  2. Updated to the nightly build kernel, and saw some improvements: On windows nothing is detected. when the cable is plugged. On raspberry pi most of the time nothing is detected (similar to windows) I had once this crash/reboot on the raspberry pi when plugging the otg cable : Jul 5 13:46:06 WBox kernel: [ 383.753841] Indeed it is in host mode hprt0 = 00001501 Jul 5 13:46:06 WBox kernel: [ 383.963629] usb 1-1: new high-speed USB device number 6 using dwc_otg Jul 5 13:46:06 WBox kernel: [ 383.963740] Indeed it is in host mode hprt0 = 00001101 Jul 5 13:46:06 WBox kernel: [ 384.203831] usb 1-1: New USB device found, idVendor=0424, idProduct=9514 Jul 5 13:46:06 WBox kernel: [ 384.203840] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jul 5 13:46:06 WBox kernel: [ 384.204276] hub 1-1:1.0: USB hub found Jul 5 13:46:06 WBox kernel: [ 384.204327] hub 1-1:1.0: 5 ports detected Jul 5 13:46:07 WBox kernel: [ 384.523621] usb 1-1.1: new high-speed USB device number 7 using dwc_otg Jul 5 13:46:07 WBox kernel: [ 384.653894] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00 Jul 5 13:46:07 WBox kernel: [ 384.653905] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jul 5 13:46:07 WBox kernel: [ 384.656652] smsc95xx v1.0.6 Jul 5 13:46:07 WBox mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1" Jul 5 13:46:07 WBox mtp-probe: bus: 1, device: 7 was not an MTP device Jul 5 13:46:07 WBox kernel: [ 384.746550] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:23:73:87 Jul 5 13:46:07 WBox kernel: [ 385.025275] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup Jul 5 13:46:07 WBox kernel: [ 385.025466] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 5 13:46:09 WBox kernel: [ 386.499921] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 5 13:46:09 WBox kernel: [ 386.500566] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1 Jul 5 13:48:01 WBox kernel: [ 0.000000] Booting Linux on physical CPU 0x0 rarely it works and I can connect from the raspberry host in serial on /dev/ttyACM0. [ 287.293970] usb 1-1.4: new high-speed USB device number 4 using dwc_otg [ 287.424702] usb 1-1.4: New USB device found, idVendor=0525, idProduct=a4a7 [ 287.424717] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 287.424726] usb 1-1.4: Product: Gadget Serial v2.4 [ 287.424735] usb 1-1.4: Manufacturer: Linux 4.19.57-sunxi with musb-hdrc [ 287.476847] cdc_acm 1-1.4:2.0: ttyACM0: USB ACM device [ 287.477482] usbcore: registered new interface driver cdc_acm [ 287.477488] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Btw if you can upload a SD image with the modifications, I'll test it. thanks
  3. Hi Igor, thanks a lot for instructions that's great. I'm glad you made it work on your device, unfortunately I still have the issue on mine (nothing detect on the host either on my windows or other linux machines). I followed your instructions starting with a virgin orangepipc image armbian stretch, did a firmware update, installed the new dtb : dpkg -i linux-dtb-next-sunxi_5.90_armhf.deb root@orangepipc:/boot# ls -l total 20816 -rw-r--r-- 1 root root 3295977 May 8 12:20 System.map-4.19.38-sunxi -rw-r--r-- 1 root root 201 Jul 5 10:04 armbianEnv.txt -rw-r--r-- 1 root root 1536 May 4 00:08 armbian_first_run.txt.template -rw-r--r-- 1 root root 4882 May 4 00:08 boot-desktop.png -rw-r--r-- 1 root root 230454 May 4 00:08 boot.bmp -rw-r--r-- 1 root root 3726 May 4 00:06 boot.cmd -rw-rw-r-- 1 root root 3798 May 4 00:10 boot.scr -rw-r--r-- 1 root root 162592 May 8 12:20 config-4.19.38-sunxi lrwxrwxrwx 1 root root 17 Jul 5 09:53 dtb -> dtb-4.19.57-sunxi drwxr-xr-x 3 root root 12288 Jul 5 10:19 dtb-4.19.57-sunxi lrwxrwxrwx 1 root root 17 May 4 00:07 dtb.old -> dtb-4.19.38-sunxi -rw-r--r-- 1 root root 4954411 Jul 5 09:56 initrd.img-4.19.38-sunxi -rw-r--r-- 1 root root 176056 Jul 5 09:53 linux-dtb-next-sunxi_5.90_armhf.deb drwxrwxr-x 2 root root 4096 May 4 00:08 overlay-user -rw-r--r-- 1 root root 0 Jul 5 10:19 sun8i-h3-orangepi-pc-plus.dts lrwxrwxrwx 1 root root 21 Jul 5 09:56 uInitrd -> uInitrd-4.19.38-sunxi -rw-r--r-- 1 root root 4954475 Jul 5 09:56 uInitrd-4.19.38-sunxi -rwxr-xr-x 1 root root 7489584 May 8 12:20 vmlinuz-4.19.38-sunxi lrwxrwxrwx 1 root root 21 Jul 5 09:56 zImage -> vmlinuz-4.19.38-sunxi Then I installed g_serial, seems to work: root@orangepipc:/boot/dtb# uname -a Linux orangepipc 4.19.38-sunxi #5.85 SMP Wed May 8 14:20:48 CEST 2019 armv7l GNU/Linux root@orangepipc:/boot/dtb# dmesg | grep g_serial [ 4.429565] g_serial gadget: Gadget Serial v2.4 [ 4.429576] g_serial gadget: g_serial ready root@orangepipc:/boot/dtb# ps aux | grep getty root 1267 0.0 0.1 3692 1156 tty1 Ss+ 10:05 0:00 /sbin/agetty --noclear tty1 linux root 1268 0.0 0.1 3472 1460 ttyS0 Ss+ 10:05 0:00 /sbin/agetty --keep-baud 115200,38400,9600 ttyS0 linux root 1269 0.0 0.1 3472 1552 ttyGS0 Ss+ 10:05 0:00 /sbin/agetty --keep-baud 115200,38400,9600 ttyGS0 linux I decompiled the /boot/dtb-4.19.57-sunxi/sun8i-h3-orangepi-pc-plus.dtb , opened sun8i-h3-orangepi-pc-plus.dts with notepad++, and I couldn't find the sections mentioned in your patch (used dtc version 1.5.0 to decompile). Don't know if it is normal ? seems strange to me (see attached dts files). Do I need to update the kernel to version 4.19.57 ? I tried with different boards orangepipc, orangepipc+, and micro usb cables / otg cables, so I doubt it is a hardware issue. I can give you remote SSH access to my device if you would like to check things. I'll make armbian a donation once it is working. thanks sun8i-h3-orangepi-pc.dts sun8i-h3-orangepi-pc-plus.dts
  4. I used dtc to modify the dr_mode: (to compile) dtc -I dts /boot/dtb/sun8i-h3-orangepi-pc.dts -O dtb -o /boot/dtb/sun8i-h3-orangepi-pc.dtb segment of the dts I modified file : usb@1c19000 { compatible = "allwinner,sun8i-h3-musb"; reg = <0x1c19000 0x400>; clocks = <0x3 0x20>; resets = <0x3 0x11>; interrupts = <0x0 0x47 0x4>; interrupt-names = "mc"; phys = <0xc 0x0>; phy-names = "usb"; extcon = <0xc 0x0>; status = "okay"; dr_mode = "otg"; phandle = <0x3f>; }; I tried the "host" mode (connecting my keyboard through the usb-otg cable) , I got the following errors : [ 1259.409939] usb 2-1: new low-speed USB device number 26 using ohci-platform [ 1259.601958] usb 2-1: device descriptor read/64, error -62 [ 1259.901964] usb 2-1: device descriptor read/64, error -62 [ 1260.197984] usb 2-1: new low-speed USB device number 27 using ohci-platform [ 1260.389988] usb 2-1: device descriptor read/64, error -62 [ 1260.689998] usb 2-1: device descriptor read/64, error -62 [ 1260.798056] usb usb2-port1: attempt power cycle [ 1261.302030] usb 2-1: new low-speed USB device number 28 using ohci-platform [ 1261.718039] usb 2-1: device not accepting address 28, error -62 [ 1261.906058] usb 2-1: new low-speed USB device number 29 using ohci-platform [ 1262.322070] usb 2-1: device not accepting address 29, error -62 [ 1262.322134] usb usb2-port1: unable to enumerate USB device In "otg" and "peripheral" modes (peripheral is the mode I would like to use), nothing is detected on the host side (raspberry pi) , altough g_serial is running seemingly correctly on the peripheral (orange pi pc) Any ideas ? I tried both otg-cables and plain micro usb cables. thanks
  5. I found this tutorial : https://vjordan.info/log/fpga/nanopi-neo-usb-otg-with-armbian-mainline-4x-kernel.html and tried to modify the .dtb file without success. The file seems correct to me, but I am not a specialist. The article mention this patch for orange pi one : https://github.com/megous/linux/commit/b97b8104c1f61071c6b7c4d6fe7a2eb06517e956 I tried to follow this and activate vbus0 with the PL2 gpio (don't know if it makes sense), but i could not make it work.
  6. The g_ether / g_serial module are working, the usb0 interface is working (for g_ether) and the /dev/ttyGS0 (g_serial) are present. But nothing is detected on the host side when I plug the usbcable. I tried to connect it to a raspberry pi and my windows 10, nothing detected. Any ideas why ? I am using the standard armbian image without modifications.
  7. Hi, I just would like to make the micro usb port work with g_serial or g_ether as a peripheral (not host). Tried to put the dr_mode to "peripheral", but I have seen no difference. When I plug the micro usb cable, it is like dead. Already tried other forums solutions. The host device doesn't detect anything, does not mount /dev/ttyACM0 (and on windows host I have no periphals detected). I also already tried to power it through GPIO PL2 (by writing directly in the shared memory), but no difference thanks
  8. Hi, I can't make usb otg works on orange pi pc armbian stretch. Linux orangepipc 4.19.38-sunxi #5.83 SMP Fri May 3 23:33:25 CEST 2019 armv7l GNU/Linux At boot there is the following message in dmesg: [ 2.252841] usb0-vbus: disabling I tried to enable usbhost0 with armbianconfig overlays, but it doesn't make a difference. Any suggestions ? thanks
  9. Dear Armbian team, I am using debian stretch with orange pi PC ( Linux orangepipc 4.19.38-sunxi #5.83 SMP Fri May 3 23:33:25 CEST 2019 armv7l GNU/Linux ). At the moment by default when I press the power button, it shutdowns the orangepi pc, and I have to plug off/on the power supply to reboot the device. I would like to modify this behavior, to program custom actions when the button is pressed. If possible it would be nice to be able to distinguish between short press and long press. I tried without success to follow the manual instructions, and add the custom overlay gpio-button.dts. Also tried the acpi package approach without access. Could you please help me on this issue? Best regards, Etienne
  10. Hi Martinayotte, I would be interested in the em485 patch for orange pi pc board. The goal would be to use it with uart to rs485 MAX3485 for modbus communication. Do you know when it would be available ? Are there any limitations in terms of reliability / baud rate / parity / stop bit / etc.. ? I am ready to help, test, and make donation. Best regards, Etienne