TonyMac32

  • Posts

    2342
  • Joined

  • Last visited

Reputation Activity

  1. Like
    TonyMac32 got a reaction from lanefu in Armbian 20.02 (Chiru) Release Thread   
    O RLY? Very nice.

    Sent from my Pixel using Tapatalk

  2. Like
    TonyMac32 reacted to sgjava in User Space IO is Python 3 and Java 8 bindings for user space GPIO, SPI, I2C, PWM and Serial interfaces   
    @TonyMac32 @Tido @fourtyseven I've updated userspaceio to build libgpiod master branch. It requires >= 5.5.0 kernel which I install using armbian-config. Now you will be on the bleeding edge of libgpiod.
  3. Like
    TonyMac32 got a reaction from balbes150 in Armbian 20.02 (Chiru) Release Thread   
    This looks very much like what I did, I'll have to dig a bit deeper since it didn't work for me.  I applied the dtsi and dts patches as proposed for the sound pipeline on mainline, I'll just have to dig around and see what else is different. 
     
    @balbes150 I forgot to enable i2s0 and 1...    Works now, but PulseAudio isn't piping audio until I change outputs back and forth a few times... (Bionic)
  4. Like
    TonyMac32 reacted to balbes150 in Armbian 20.02 (Chiru) Release Thread   
    With the correct DTB, the sound works in the official images for rk3328 (I tried the official images for Renegade and Rock64). All it took was adding the correct DTB (with audio support). If use a DTB from roc-cc, there is no sound.
     
    You can see how the sound was added to DTS here.
     
    https://github.com/150balbes/Amlogic_s905-kernel/blob/5.4/arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts
     
    https://github.com/150balbes/Amlogic_s905-kernel/blob/5.5/arch/arm64/boot/dts/rockchip/rk3328-roc-cc.dts
  5. Like
    TonyMac32 reacted to stut in Armbian 20.02 (Chiru) Release Thread   
    I do have one of those gun like ones, thanks for reminding me. I checked some temps and the reported temps are pretty much spot on. It might run cooler without the 1.3ghz overlay cuz I think that increases the voltage, not sure though. Of course I can't measure the chip itself due to the heatsink but I did my best to get a close as possible and find the hottest parts. I do have a temp sensor for a multimeter somewhere that is probably small enough to sit between the heatsink and the dye of the chip but it will reduce the surface so might influence results a bit.
     
    Edit: ran sbc-bench without errors: http://ix.io/28pz
  6. Like
    TonyMac32 got a reaction from TRS-80 in KiCad templates   
    I pushed a template for the NanoPi NEO (2/Air/Core/Plus2) onto my github:
     
    https://github.com/Tonymac32/kicad-templates
     
    If you want to make add-ons, that's fully labelled and the header positions are as correct as I could get them without official reference.  I have made a few boards with it, so can vouch that it will assemble.  I'll add more as I have time and money to do so, since I don't want to push any that aren't verified in some manner.
  7. Like
    TonyMac32 reacted to sgjava in User Space IO is Python 3 and Java 8 bindings for user space GPIO, SPI, I2C, PWM and Serial interfaces   
    @TonyMac32 @Tido I've gone through all the demo code and everything is working with the updated libraries. non-root access works with everything except PWM which has been a bear to figure out. Also added system LED library which includes triggers. I still need to work on some demos for LED triggers. 
  8. Like
    TonyMac32 got a reaction from JMCC in RK3328 Kernel   
    The media script is only functional with the rockchip 4.4 kernel.  The upstream decoder support is incomplete, and incompatible with the Rockchip driver.
  9. Like
    TonyMac32 got a reaction from Redferne in Armbian 20.02 (Chiru) Release Thread   
    I knew I would get the right people into this conversation.
  10. Like
    TonyMac32 got a reaction from aaditya in RK3399 Stable? Move subforum from Development to Bug Tracker?   
    I think with the next LTS mainline kernel this will be possible. Right now there are still a few odds and ends, RK3399 is not as well supported as RK3288, for example. It's far better off than RK3328 though. We have some fragmentation of the RK3399 boards due to bootloader difficulties with RAM, Rockchip has been extraordinarily slow to improve LPDDR4 support

    Sent from my Pixel using Tapatalk


  11. Like
    TonyMac32 reacted to chwe in Armbian 20.02 (Chiru) Release Thread   
    well you've no chance I already set up the pinebook in rk3399 with u-boot 2020:
     
    U-Boot 2020.01-armbian (Jan 21 2020 - 23:08:47 +0100) Model: Pine64 Pinebook Pro DRAM: 3.9 GiB PMIC: RK808 MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0 In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Pine64 Pinebook Pro ## Error: Can't overwrite "serial#" ## Error inserting "serial#" variable, errno=1 rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2940 bytes read in 6 ms (478.5 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 143 bytes read in 6 ms (22.5 KiB/s) 7118384 bytes read in 752 ms (9 MiB/s) 20722176 bytes read in 2178 ms (9.1 MiB/s) 72693 bytes read in 17 ms (4.1 MiB/s) 2698 bytes read in 9 ms (292 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7118320 Bytes = 6.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f5853000, end f5f1cdf0 ... OK Loading Device Tree to 00000000f57d8000, end 00000000f5852fff ... OK Starting kernel ... [ 2.647157] Internal error: Oops: 96000004 [#1] PREEMPT SMP  
    it seems it doesn't like my new DT.. but u-boot works fine and blobfree..
  12. Like
    TonyMac32 got a reaction from Werner in [Moderation] Resources, Tips, Guidance   
  13. Like
    TonyMac32 got a reaction from lanefu in [Moderation] Resources, Tips, Guidance   
  14. Like
    TonyMac32 got a reaction from lanefu in Armbian 20.02 (Chiru) Release Thread   
    I just pushed a fix for the desktop in legacy.  It boots to desktop now.
  15. Like
    TonyMac32 reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    Bugfix only after freeze date
  16. Like
    TonyMac32 got a reaction from manuti in Emby Server with hardware transcoding in XU4/HC1/HC2 Armbian Stretch   
    I run a Plex server at the moment, on an XU4.  I'll have to try this out on my test board and might have to migrate if it as good as advertised.
  17. Like
    TonyMac32 reacted to piter75 in Rock PI 4 A not starting   
    Totally agree. This is the only way to get help in this case.
     
    This crossed my mind before and I think it is a good idea.
    We already have it in place for Rock Pi 4b (it was implemented before we had Rock Pi 4a as a separate board) and it works well when used with the same u-boot version on eMMC and SD.
     
    @raidboy you can try to use Rock Pi 4b image which has priority set to SD and see if it works better in this scenario. Nothing is guaranteed as you are mixing stages of u-boots compiled with different configurations and even different code bases so... YMMV.
  18. Like
    TonyMac32 reacted to guidol in [Info] FriendlyARM PCM5102A-Hat with NanoPi Neo under mainline 4.x.x and dev 5.x.x   
    I did that on a NanoPi Neo with the FriendlyARM PCM5102A Hat
    ( https://www.friendlyarm.com/index.php?route=product/product&product_id=169 )
    using kernel 4.14.87-sunxi and armbian 5.67 (or later would be only 5.65?)
    (before that I did use legacy kernel 3.4.x with the PCM510A)

    and the armbian-BuildSystem
    plus (THANKS to) informations in threads from  @dony71 , @Christos, @Valery Rezvyakov
    and the the Reference-Threads you could find above
     
    ----------------------------------------------------------------------------------------------------------------------------------
    BACKUP DTB (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    cp /boot/dtb/sun8i-h3-nanopi-neo.dtb /boot/dtb/sun8i-h3-nanopi-neo.dtb_org
     
    ----------------------------------------------------------------------------------------------------------------------------------
    CONVERT dtb to dts (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    dtc -I dtb -O dts /boot/dtb/sun8i-h3-nanopi-neo.dtb -o /boot/dtb/sun8i-h3-nanopi-neo.dts
     
    ----------------------------------------------------------------------------------------------------------------------------------
    EDIT /boot/dtb/sun8i-h3-nanopi-neo.dts
    ----------------------------------------------------------------------------------------------------------------------------------
    nano /boot/dtb/sun8i-h3-nanopi-neo.dts
     
    - change: status from "disabled" to "okay"
    ----------------------------------------------------------------------------------------------------------------------------------
    FROM
     
                    i2s@1c22000 {                         #sound-dai-cells = <0x0>;                         compatible = "allwinner,sun8i-h3-i2s";                         reg = <0x1c22000 0x400>;                         interrupts = <0x0 0xd 0x4>;                         clocks = <0x3 0x38 0x3 0x54>;                         clock-names = "apb", "mod";                         dmas = <0x13 0x3 0x13 0x3>;                         resets = <0x3 0x2b>;                         dma-names = "rx", "tx";                         status = "disabled";                         phandle = <0x4e>;                 };  

    TO
     
                    i2s@1c22000 {                         #sound-dai-cells = <0x0>;                         compatible = "allwinner,sun8i-h3-i2s";                         reg = <0x1c22000 0x400>;                         interrupts = <0x0 0xd 0x4>;                         clocks = <0x3 0x38 0x3 0x54>;                         clock-names = "apb", "mod";                         dmas = <0x13 0x3 0x13 0x3>;                         resets = <0x3 0x2b>;                         dma-names = "rx", "tx";                         status = "okay";                         phandle = <0x4e>;                 };
    ----------------------------------------------------------------------------------------------------------------------------------
    CONVERT (BACK) dts to dtb (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    dtc -I dts -O dtb /boot/dtb/sun8i-h3-nanopi-neo.dts -o /boot/dtb/sun8i-h3-nanopi-neo.dtb_I2S_okay
     
    ----------------------------------------------------------------------------------------------------------------------------------
    COPY new dtb over dtb (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    cp /boot/dtb/sun8i-h3-nanopi-neo.dtb_I2S_okay /boot/dtb/sun8i-h3-nanopi-neo.dtb
                    
    ----------------------------------------------------------------------------------------------------------------------------------
    COPY sun8i-h3-I2S-out.dts to home (working directory on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    copy sun8i-h3-I2S-out.dts -->  /home/guido/
     
    ----------------------------------------------------------------------------------------------------------------------------------
    armbian-add-overlay (on NanoPi Neo)
    does only work if you got the kernel-headers installed for your actual kernel-version
    (at this time the lastest kernel-header are (via armbian-config -> Software -> Install Headers)
    Linux kernel headers for 4.14.84-sunxi on armhf - so NOT for kernel 4.19.y)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):/home/guido# armbian-add-overlay ./sun8i-h3-I2S-out.dts
    Compiling the overlay
    Copying the compiled overlay file to /boot/overlay-user/
    Reboot is required to apply the changes

    ----------------------------------------------------------------------------------------------------------------------------------
    dtbo is created (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):/home/guido# ls -l /boot/overlay-user/
    insgesamt 4
    -rw-r--r-- 1 root root 1323 Dez  7 19:34 sun8i-h3-I2S-out.dtbo
     
    ----------------------------------------------------------------------------------------------------------------------------------
    user-overlay is created in /boot/armbianEnv.txt (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost1 usbhost2 rootdev=UUID=33ca90d6-130b-4d5f-a8f4-95b3b97ef5c0 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u user_overlays=sun8i-h3-I2S-out  
    ----------------------------------------------------------------------------------------------------------------------------------
    now REBOOT (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):~# lsmod|grep i2s
    sun4i_i2s              16384  0
    snd_soc_core          118784  2 sun4i_i2s,sun8i_codec_analog
    snd_pcm                69632  3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core
     
    ----------------------------------------------------------------------------------------------------------------------------------
    EDIT config-default.conf (on armbian-BuildSystem)
    ----------------------------------------------------------------------------------------------------------------------------------
    cd /home/guido/build
    nano ./config-default.conf
    replace content /home/guido/build/config-default.conf with attached
    config-default.conf_nanopineo
    ./compile
    -> With this conf, script compilation will stop to overwrite kernel source to build patch
    -> At that time, overwrite original Kconfig with the one you modified above
    (at "Make changes to U-Boot" press ENTER to proceed)
    wait for
    "Make your changes to /home/guido/build/cache/sources/linux-mainline/linux-4.14.y then press ENTER"
    BUT DONT PRESS ENTER YET
     
    ----------------------------------------------------------------------------------------------------------------------------------
    EDIT/SAVE Kconfig in a 2nd shell-Window (on armbian-BuildSystem)
    ----------------------------------------------------------------------------------------------------------------------------------
    nano /home/guido/build/cache/sources/linux-mainline/linux-4.14.y/sound/soc/codecs/Kconfig
     
    the part FROM
     
    config SND_SOC_PCM5102A     tristate TO
     
    config SND_SOC_PCM5102A     tristate "Texas Instruments PCM5102A CODEC - I2S"  
    ----------------------------------------------------------------------------------------------------------------------------------
    NOW PRESS ENTER in the 1st shell-Windows (.compile.sh) (on armbian-BuildSystem)
    ----------------------------------------------------------------------------------------------------------------------------------
    -> Then script compilation will stop again to ask whether you want to add pcm5102a to compile
    -> Default is N, so you need to enter m for module compilation
    Texas Instruments PCM5102A CODEC - I2S (SND_SOC_PCM5102A) [N/m/?] (NEW) m = m for module compilation
     
    After compile is complete
     
    ----------------------------------------------------------------------------------------------------------------------------------
    copy (via SCP/FTP?) the .deb's from /home/guido/build/output/debs (on armbian-BuildSystem) 
    to /home/guido/ (on the NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
     
    ----------------------------------------------------------------------------------------------------------------------------------
    INSTALL the .deb's (here only header and image - because it was already 5.67 (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    cd /home/guido 
    dpkg -i ./linux-headers-next-sunxi_5.67_armhf.deb
    dpkg -i ./linux-image-next-sunxi_5.67_armhf.deb
    (image did include the .ko module for the pcm5102a)
     
    ----------------------------------------------------------------------------------------------------------------------------------
    now REBOOT (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
     
    =====================================================================================
    =====================================================================================
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!! ATTENTION: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    After reboot my NanoPi Neo show the following armbian-version:
    ARMBIAN 5.65 stable Debian GNU/Linux 9 (stretch) 4.14.84-sunxi
    and 2 upgrades for headers&image (without the PCM5102A support)
    please keep in mind to freeze the kernel-updates in armbian-config
    for not to loose the support (module) for the PCM5120A!
    armbian-config -> system -> Freeze Disable kernel upgrades
    =====================================================================================
    =====================================================================================

    ----------------------------------------------------------------------------------------------------------------------------------
    BE HAPPY about a successful i2s mapping in dmesg (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):~# dmesg|grep -i i2s
    [    6.911751] asoc-simple-card sound_i2s: pcm5102a-hifi <-> 1c22000.i2s mapping ok
     
    ----------------------------------------------------------------------------------------------------------------------------------
    I enabled also ananlog-Codec (on NanoPi Neo)
    ----------------------------------------------------------------------------------------------------------------------------------
    root@npi-neo(192.168.6.24):/home/guido# aplay -l
    **** Liste der Hardware-Geräte (PLAYBACK) ****
    Karte 0: Codec [H3 Audio Codec], Gerät 0: CDC PCM Codec-0 []
      Sub-Geräte: 1/1
      Sub-Gerät #0: subdevice #0
    Karte 1: I2Smaster [I2S-master], Gerät 0: 1c22000.i2s-pcm5102a-hifi pcm5102a-hifi-0 []
      Sub-Geräte: 1/1
      Sub-Gerät #0: subdevice #0

    ----------------------------------------------------------------------------------------------------------------------------------
    /etc/asound.conf (on NanoPi Neo) - later I2S did switch automatically to card 0
    ----------------------------------------------------------------------------------------------------------------------------------
     
    pcm.!default {     type hw     card 1     device 0 } ctl.!default {     type hw     card 1 }  
    ----------------------------------------------------------------------------------------------------------------------------------
    Reference-Threads
    ----------------------------------------------------------------------------------------------------------------------------------
     
    config-default.conf.mod_nanopineo
    sun8i-h3-I2S-out.dts
  19. Like
    TonyMac32 reacted to sgjava in User Space IO is Python 3 and Java 8 bindings for user space GPIO, SPI, I2C, PWM and Serial interfaces   
    @TonyMac32 @Tido I'm building a frankenboard to test all the code (I'll need to take a picture soon). Since there were a lot of things brought up to date a regression type test is required (at least in my mind). So far GPIO, PWM and SPI are working fine. I even added logic to turn on/off LED based on HC-SR501 input in Java. The only issue so far was on libgpiod chip close https://github.com/sgjava/userspaceio/issues/5, but this may go away once I can test libgpiod master branch on 5.5 kernel.
  20. Like
    TonyMac32 reacted to sgjava in User Space IO is Python 3 and Java 8 bindings for user space GPIO, SPI, I2C, PWM and Serial interfaces   
    @TonyMac32 OK the cffi stuff is failing, but that's all packaging (no compiles), so I hope that's easy to fix. The Java/JNA and libgpiod work so far (what's committed). libgpiod master branch requires >= 5.5.0 kernel to build.  The nanopi duo distro uses 5.3.9, so I used v1.4.x branch! Let me see if I can finish up the rest.
    sudo gpiodetect gpiochip0 [1c20800.pinctrl] (224 lines) gpiochip1 [1f02c00.pinctrl] (32 lines)  
  21. Like
    TonyMac32 reacted to sgjava in User Space IO is Python 3 and Java 8 bindings for user space GPIO, SPI, I2C, PWM and Serial interfaces   
    @TonyMac32 I just flash a nanopi duo v1.1 and will go through the install. I know for a fact the Java JDK will need to be updated. I'll keep you updated.
  22. Like
    TonyMac32 reacted to sgjava in ArmbianIO API proposal   
    I've focused only on UserSpaceIO because it covers more of what I needed. Multi-language/multi-interfaces. I'll go in and do any updates since I'll have to switch over to Zulu JVM since Oracle isn't releasing ARM based JDKs.
  23. Like
    TonyMac32 got a reaction from Igor in Pine H64 Model B Questions   
    Indeed I do, let me set up the white box. ;-)

    Sent from my Pixel using Tapatalk

  24. Like
    TonyMac32 got a reaction from gounthar in ROC-RK3399-PC (Renegade Elite)   
    So far what I'm seeing is dt slop (on all boards using this chip)
    1) lack of a connector node, which, when added, brings along
    lack of port nodes for the connector IRQ errors (related how?  no idea) 2) lack of "op-sink-milliwatt" property
     
    Once op-sink-milliwatt is added it will boot, which leads me to believe the chip is receiving commands from the driver, however probe fails with "failed to register tcpm error -22"  I haven't gotten past that, so 5V only, no mode switching.  And I am not immediately inclined to write a driver for the dc-dc converter.  ;-)
     
    My current device tree entry:
    &i2c7 { i2c-scl-rising-time-ns = <600>; i2c-scl-falling-time-ns = <20>; status = "okay"; fusb0: usb-typec@22 { compatible = "fcs,fusb302"; reg = <0x22>; interrupt-parent = <&gpio1>; interrupts = <2 IRQ_TYPE_LEVEL_LOW>; pinctrl-names = "default"; pinctrl-0 = <&fusb0_int>; vbus-supply = <&vcc_vbus_typec0>; usbc_con2: connector { compatible = "usb-c-connector"; label = "USB-C-0"; power-role = "dual"; sink-pdos = <PDO_FIXED(5000, 3000, PDO_FIXED_USB_COMM) PDO_VAR(5000, 15000, 3000) PDO_PPS_APDO(5000, 15000, 3000)>; op-sink-microwatt = <25000000>; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; usb_con_hs0: endpoint { remote-endpoint = <&u2phy0_otg>; }; }; port@1 { reg = <1>; usb_con_ss0: endpoint { remote-endpoint = <&tcphy0_usb3>; }; }; port@2 { reg = <2>; usb_con_sbu0: endpoint { remote-endpoint = <&tcphy0_dp>; }; }; }; }; }; };  
    [edit]  I want to be clear all the port definitions could be nonsense, the documentation is a bit thin on all sides of this.  One thing I'd like to consider is the interrupt type, even though the fusb302 specified it's interrupt pin is active low...
     
    @Neil Armstrong, in case you have some insight into this.
  25. Like
    TonyMac32 got a reaction from Redferne in ROC-RK3399-PC (Renegade Elite)   
    There is special driver work done in their kernel to cover an unsupported I2C buck/boost converter that provides the 12V rail on this board, and for reasons I'm digging into, the fusb302 driver is a complete mess after they moved it out of staging, it has a lot of odd behaviors and a completely new set of requirements for the device tree.  I temporarily ran it back to the staging driver for our mainline expert builds (limited improvement), but am working on the proper driver.