aaditya

  • Posts

    13
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Posts posted by aaditya

  1. I have a suggestion for the moderators:

     

    Please move the Rockchip 3399 subforum from development to Bug Tracker if its ok!

     

    Most of the boards listed there: Nanopi Neo4, M4, NanoPC T4, Rock64PRO, Rock Pi4 are now marked as supported on the Armbian download page.

    I read a comment from @Igor sometime ago (not able to locate right now) that the only thing holding back the sub forum transfer was a lack of moderator action.

    Thanks.

     

  2. Hi Igor,

     

    On 12/16/2019 at 5:55 PM, Igor said:

    And It most likely also works with Armbian with Linux 4.4.y ... This is the correct way to compare.

    Agree. Will check.

     

    On 12/16/2019 at 5:55 PM, Igor said:

    Yes. Modern kernel needs lots of development and porting to match the level of the kernel where this hardware support was initially developed. This can take years.

    I understand. I reported so that we know this problem is present with current kernels. And experienced community members can help to diagnose and fix it.

     

    Thanks.

     

    Edit-

    I confirm that it works with the Armbian legacy kernel (4.4.198-rockchip64).

  3. Hi,

     

    I am using Armbian_19.11.3_Rockpi-4b_buster_current_5.3.11_desktop.

     

    Facing issue when trying to use USB devices in the upper USB 3 port on a Rock Pi 4 v1.3. This port also supports USB OTG. The switch is set to Host mode.

    The storage is detected occasionally, while most of the time it does not work.

     

    dmesg contains no reference to the connected storage:

    $ dmesg | grep usb
    [    0.000000] Kernel command line: root=UUID=590fca6f-9771-4245-86a7-34712bfe535b rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=7ef2aff3-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
    [    5.284733] usbcore: registered new interface driver usbfs
    [    5.287156] usbcore: registered new interface driver hub
    [    5.292587] usbcore: registered new device driver usb
    [   50.127245] usbcore: registered new interface driver pegasus
    [   50.129170] usbcore: registered new interface driver rtl8150
    [   50.132096] usbcore: registered new interface driver r8152
    [   50.134404] usbcore: registered new interface driver dm9601
    [   50.136578] usbcore: registered new interface driver CoreChips
    [   50.139442] usbcore: registered new interface driver smsc75xx
    [   50.141440] usbcore: registered new interface driver smsc95xx
    [   50.143765] usbcore: registered new interface driver plusb
    [   50.145608] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
    [   50.374451] ehci-platform fe380000.usb: EHCI Host Controller
    [   50.375497] ehci-platform fe380000.usb: new USB bus registered, assigned bus number 1
    [   50.381185] ehci-platform fe380000.usb: irq 31, io mem 0xfe380000
    [   50.395266] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00
    [   50.408238] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03
    [   50.408790] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [   50.409190] usb usb1: Product: EHCI Host Controller
    [   50.409557] usb usb1: Manufacturer: Linux 5.3.11-rockchip64 ehci_hcd
    [   50.410635] usb usb1: SerialNumber: fe380000.usb
    [   50.468500] ehci-platform fe3c0000.usb: EHCI Host Controller
    [   50.469493] ehci-platform fe3c0000.usb: new USB bus registered, assigned bus number 2
    [   50.475359] ehci-platform fe3c0000.usb: irq 33, io mem 0xfe3c0000
    [   50.491432] ehci-platform fe3c0000.usb: USB 2.0 started, EHCI 1.00
    [   50.501308] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03
    [   50.502470] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [   50.502888] usb usb2: Product: EHCI Host Controller
    [   50.503283] usb usb2: Manufacturer: Linux 5.3.11-rockchip64 ehci_hcd
    [   50.503650] usb usb2: SerialNumber: fe3c0000.usb
    [   50.585291] ohci-platform fe3a0000.usb: Generic Platform OHCI controller
    [   50.587119] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus number 3
    [   50.592909] ohci-platform fe3a0000.usb: irq 32, io mem 0xfe3a0000
    [   50.664813] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.03
    [   50.665289] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [   50.666380] usb usb3: Product: Generic Platform OHCI controller
    [   50.666764] usb usb3: Manufacturer: Linux 5.3.11-rockchip64 ohci_hcd
    [   50.667113] usb usb3: SerialNumber: fe3a0000.usb
    [   50.720807] ohci-platform fe3e0000.usb: Generic Platform OHCI controller
    [   50.722470] ohci-platform fe3e0000.usb: new USB bus registered, assigned bus number 4
    [   50.728607] ohci-platform fe3e0000.usb: irq 34, io mem 0xfe3e0000
    [   50.799943] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.03
    [   50.800404] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [   50.800802] usb usb4: Product: Generic Platform OHCI controller
    [   50.801176] usb usb4: Manufacturer: Linux 5.3.11-rockchip64 ohci_hcd
    [   50.801528] usb usb4: SerialNumber: fe3e0000.usb
    [   50.897341] usbcore: registered new interface driver usb-storage
    [   52.303330] usbcore: registered new interface driver usbhid
    [   52.303335] usbhid: USB HID core driver
    [   53.090803] OF: graph: no port node found in /syscon@ff770000/usb2-phy@e450/otg-port
    [   53.093318] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03
    [   53.093324] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [   53.093329] usb usb5: Product: xHCI Host Controller
    [   53.093334] usb usb5: Manufacturer: Linux 5.3.11-rockchip64 xhci-hcd
    [   53.093338] usb usb5: SerialNumber: xhci-hcd.0.auto
    [   53.095135] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
    [   53.095238] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03
    [   53.095244] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [   53.095249] usb usb6: Product: xHCI Host Controller
    [   53.095253] usb usb6: Manufacturer: Linux 5.3.11-rockchip64 xhci-hcd
    [   53.095257] usb usb6: SerialNumber: xhci-hcd.0.auto
    [   53.100145] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03
    [   53.100150] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [   53.100155] usb usb7: Product: xHCI Host Controller
    [   53.100160] usb usb7: Manufacturer: Linux 5.3.11-rockchip64 xhci-hcd
    [   53.100164] usb usb7: SerialNumber: xhci-hcd.1.auto
    [   53.101778] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
    [   53.101822] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03
    [   53.101825] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [   53.101828] usb usb8: Product: xHCI Host Controller
    [   53.101830] usb usb8: Manufacturer: Linux 5.3.11-rockchip64 xhci-hcd
    [   53.101833] usb usb8: SerialNumber: xhci-hcd.1.auto
    [   54.194069] usb 8-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
    [   54.219860] usb 8-1: New USB device found, idVendor=8564, idProduct=1000, bcdDevice=11.00
    [   54.219871] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [   54.219878] usb 8-1: Product: Mass Storage Device
    [   54.219885] usb 8-1: Manufacturer: JetFlash
    [   54.219892] usb 8-1: SerialNumber: 72Z6UO7B9R2GAU45
    [   54.221852] usb-storage 8-1:1.0: USB Mass Storage device detected
    [   54.223204] scsi host0: usb-storage 8-1:1.0
    [   54.228901] usbcore: registered new interface driver uas
    [   59.801887] phy phy-ff770000.syscon:usb2-phy@e450.2: charger = USB_DCP_CHARGER

     

    It works with the Radxa Debian Stretch image with Linux 4.4.154-99-rockchip-g5b699a48544d:

    [    3.117507] rockchip-dwc3 usb0: USB HOST connected
    [    3.426644] usb 8-1: new SuperSpeed USB device number 2 using xhci-hcd
    [    3.444057] usb 8-1: New USB device found, idVendor=0080, idProduct=a001
    [    3.444673] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [    3.445322] usb 8-1: Product: External USB 3.0
    [    3.445735] usb 8-1: Manufacturer: TOSHIBA
    [    3.446113] usb 8-1: SerialNumber: 201503310007F
    [    4.138675] usb 7-1: new SuperSpeed USB device number 2 using xhci-hcd
    [    4.160143] usb 7-1: New USB device found, idVendor=8564, idProduct=1000
    [    4.160746] usb 7-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [    4.161370] usb 7-1: Product: Mass Storage Device
    [    4.161788] usb 7-1: Manufacturer: JetFlash
    [    4.162159] usb 7-1: SerialNumber: 72Z6UO7B9R2GAU45
    [    4.420405] usb-storage 7-1:1.0: USB Mass Storage device detected
    [    4.430414] scsi host0: usb-storage 7-1:1.0
    [    4.431253] usbcore: registered new interface driver usb-storage
    [    4.438119] usbcore: registered new interface driver uas

    So I am guessing its a kernel issue.

     

    Thanks for your work.

  4. 1 hour ago, mo123 said:

    Check if this patch is missing from the mainline kernel perhaps, it's responsible for the headphone jack.

    https://github.com/radxa/kernel/commit/cc4fef39f29bda97ba1d9129d897e77d08ccf096

    Hi mo123,

     

    Thanks for the comment. Indeed, in the mainline kernel the above code is not present.

    There are some other changes too, related to i2s0 in the Radxa kernel which are not present in mainline.

     

    Radxa (4.4): https://github.com/radxa/kernel/blob/cc4fef39f29bda97ba1d9129d897e77d08ccf096/arch/arm64/boot/dts/rockchip/rockpi-4b-linux.dts

    Mainline(5.3): https://github.com/torvalds/linux/blob/549dcdafe793000fbe38914a1f231d3c6034a6ec/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dts

     

     

  5. 3 hours ago, pkfox said:

    Thanks for replying but I'm a user not a kernel hacker :-) that stuff doesn't mean much to me - are you saying anything using kernel 5 or above has no sound ?

     

    Hi,

     

    Yes, sound with kernel 5 and above is being worked on as written in this thread.

     

  6. Hi,

     

    Tested the current build (Armbian_19.11.3_Rockpi-4b_buster_current_5.3.11_desktop.7z) on a Rock Pi 4 v1.3.

    Working well so far the past couple of hours. Its an amazing feeling to be able to run the mainline kernel with so little issues.

     

    Some minor things:

    1. The Red Led keeps on blinking with this build. Earlier it only blinked if there was error while booting. New to this board, so this maybe incorrect. I booted up Radxa image and there also red light was blinking.
    2. Sound via 3.5 mm jack not working. Inserted earphone, no output. Sound via HDMI works.

     

    Thanks for your work. :)

     

    Edit-

    System info:

    aaditya@rockpi:~$ inxi -Fxz
    System:    Host: rockpi Kernel: 5.3.11-rockchip64 aarch64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Xfce 4.12.4 
               Distro: Armbian GNU/Linux 10 (buster) 
    Machine:   Type: ARM Device System: Radxa ROCK Pi 4 details: N/A serial: <filter> 
    CPU:       Topology: 6-Core (2-Die) model: N/A variant-1: cortex-a53 variant-2: cortex-a72 bits: 64 type: MCP MCM arch: ARMv8 
               rev: 4 
               features: Use -f option to see features bogomips: 0 
               Speed: 1800 MHz min/max: 408/1512:2016 MHz Core speeds (MHz): 1: 408 2: 408 3: 408 4: 408 5: 1800 6: 1800 
    Graphics:  Device-1: display-subsystem driver: rockchip_drm v: N/A bus ID: N/A 
               Device-2: rk3399-dw-hdmi driver: dwhdmi_rockchip v: N/A bus ID: N/A 
               Device-3: rk3399-mali driver: panfrost v: kernel bus ID: N/A 
               Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev resolution: 1920x1080~60Hz 
               OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 direct render: Yes 
    Audio:     Device-1: rk3399-dw-hdmi driver: dwhdmi_rockchip bus ID: N/A 
               Device-2: simple-audio-card driver: asoc_simple_card bus ID: N/A 
               Sound Server: ALSA v: k5.3.11-rockchip64 
    Network:   Device-1: rk3399-gmac driver: rk_gmac_dwmac v: N/A port: N/A bus ID: N/A 
               IF: eth0 state: down mac: <filter> 
               IF-ID-1: dummy0 state: down mac: <filter> 
               IF-ID-2: wlan0 state: up mac: <filter> 
    Drives:    Local Storage: total: 44.52 GiB used: 15.60 GiB (35.1%) 
               ID-1: /dev/mmcblk1 model: EB1QT size: 29.81 GiB 
               ID-2: /dev/sda type: USB vendor: Transcend model: JetFlash Transcend 16GB size: 14.70 GiB 
    Partition: ID-1: / size: 28.98 GiB used: 3.16 GiB (10.9%) fs: ext4 dev: /dev/mmcblk1p1 
               ID-2: /var/log size: 48.4 MiB used: 4.2 MiB (8.6%) fs: ext4 dev: /dev/zram0 
    Sensors:   Missing: Required tool sensors not installed. Check --recommends 
    Info:      Processes: 183 Uptime: 6m Memory: 3.78 GiB used: 534.1 MiB (13.8%) Init: systemd Compilers: gcc: 8.3.0 Shell: bash 
               v: 5.0.3 inxi: 3.0.32 
    

    dmesg attached.

    dmesg-armbian-buster-current-rockpi4.txt

  7. 12 hours ago, NicoD said:

    Armbian uses only 1 partition. So that's not a problem. When the led blinks it should mean it's is booting. 
     

     

    I think for all RK3399 devices the baud rate is 1500000
    Could be only for the M4 tho. Be sure to connect the correct wires. you've got to revers the data wires.  RX -> TX and TX -> RX. 
    Not all serial programs seems to be able to use 1500000 baud rate. I've used putty in the past and that worked I think? There's other posts on the forum about what program is bes for serial use. 
     

    Hi NicoD,

     

    You are right there! I was connecting the RX of the USB Serial to the RX GPIO pin, while the correct way was to connect RX of the USB serial to TX on the GPIO. With correct connections it worked today.

     

    The chip was not a problem. Thanks to martinayotte, I knew which USB serial device to try and buy

     

    I will retry the old build which was failing to see if I can provide more information.

     

     

    Quote

    The 5.3 is a mainline. Not an updated version. There is less support for this as it's not the default rk3399 kernel.

    I'll try some images an mine and see what happens.


     

    The 5.3 kernel is interesting for me as its mainline and more open source I believe! Will try it and report any issues if possible.

     

    Thanks for the help and videos. :-)

  8. On 7/13/2019 at 3:07 AM, rogerl said:

    I installed both earlier and the latest Armbian stretch service versions. Couldn't boot from the micro SD cards. Tried several different micro SD cards too.  Nothing showed through HDMI. The red LED on board was double blinking. The board can boot from all three official images.

    Hi,

     

    I had the same issue.

     

    The latest Armbian image worked for me. More details here:

     

  9. Hi,

     

    I face the same issue, on a recently bought a Rock Pi 4B v1.3.

     

    Steps followed:

     

    1. Downloaded official (Radxa) Ubuntu Server Bionic  as well as Armbian Buster Desktop (Armbian_5.98_Rockpi-4b_Debian_buster_default_4.4.192_desktop.7z) via torrent.

     

    2. Wrote both images to different SD cards (Samsung Evo Plus Class 10) using dd. The one with Radxa Ubuntu boots, but Armbian buster does not. The red Led keeps blinking, no output via HDMI. Rewrote and tested the Armbian image twice, but no change.

     

    One difference I noticed is that on writing the Radxa image 5 partitions are created, one of which is type vfat name boot and one is type ext4 name ubt-bionic. The disk partition format is gpt. With Armbian only 1 partition of type ext4 is created and disk partition format is mbr.

     

    3. Bought a CH340G USB TTL converter thinking I could use it if needed. Connected to Rock Pi 4 using breadboard wires, but could not get any output.

     

    I am new to Armbian, Rock Pi 4 and SBCs in general; familiar with Linux.

     

    Let me know if I can try something or provide more information.

    Kind regards.

     

    Edit-

    With the latest Armbian image (Armbian_19.11.3_Rockpi-4b_buster_current_5.3.11_desktop.7z) was able to boot!

    The red led keeps blinking, but the system booted up and is working. Thanks for the updated version.