Topics

Using the DRAWS hat with a Raspberry Pi 4 #draws #yaac #install #js8call #replacecompass

la4rha@...
 

Hi all,

Not sure if this is the correct group, mods: please feel free to move this to another group if it belongs there !

LA9KOA Karl and I have started using our DRAWS on a Raspberry Pi 4. As of now we have WSJT-X, JS8Call, YAAC and Xastir working on the Raspbian Buster image. This has been through some basic tests with a Yaesu FT-891. There is still a lot to test, but so far it seems to be working quite well. YMMV

FLDigi is installed, but not yet tested

If you want to set this up yourselves, our notes/worklog is here: https://docs.google.com/document/d/1Wq-jNLXYuREIOcr0OVu1FxPNhDFGuCOu6dX5OQ2BVxA/edit?usp=sharing
Please be aware that this is a work in progress, so changes and alterations should be expected !

We appreciate any comments, both here, and in the google document

73, de
LA4RHA Lars

 

Lars,

Great work.  To your question, yes you should build fldigi and flrig from source.  

John

Frank Ivan
 

Hi Lars

You can fix the loading of js8call and wsjtx by using sudo apt-get install ./$findname instead to sudo dpkg -I $filename.  Apt will resolve the missing dependencies.  It just needs to know it is working with a local file - thus the ./ prefix.

I have followed this but can't get the drivers enabled.  When I have dtoverlay=vc4-fkms-v3d or dtoverlay=draws,alsaname=udrc enabled in /boot/config.txt my Task Bar on the screen goes away and aplay -l says aplay: device_list:272: no soundcards found... 

Maybe the drivers aren't compatible with the new SOC.

73 - Frank - K0FEI

LA9KOA - Karl
 

FYI: While you are waiting for your RPi4 to arrive, you still prepare a SDcard with Raspbian Buster (the new version needed for RPi4) on an older RPi.
I followed LA4RHA, Lars' guide (and hopefully helped a tiny bit) on a RPi3b+
Today my shiny new RPi4 arrived. I moved the DRAWS hat and SDcard over to the new RPi4 and was up and running before I could even find the right input on my TV to watch the first boot !

- I got an new IP by DHCP since the hardware MAC address change on the new unit. Other than that, everything seem to be working. Now I have to do some testing on the air. Think I'll start with my FT-817 and JS8call on 40m. :)

In other news Debian Buster was released this weekend. This is now the new "stable" release. 
How will this affect the DRAWS ecosystem? 

Best,
Karl

 

You never know until it is tested, but with Anna's driver for sound and serial in the kernel it should just move forward.

On Mon, Jul 8, 2019 at 7:50 AM LA9KOA - Karl <oyoygard@...> wrote:


In other news Debian Buster was released this weekend. This is now the new "stable" release. 
How will this affect the DRAWS ecosystem? 

Best,
Karl


--
John D. Hays
Kingston, WA
K7VE

 

Mike Watkins
 

To add to the collective knowledge, I had to run rpi-update to get the latest firmware (working on 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l).

I'm running otherwise stock Buster and installing only those apps that I need at present which for the time being is Direwolf for an APRS Digipeater/Igate.

Currently using RPI4, and yes, it does need a fan! I'm going to move the DRAWS hat to an idle Pi3. 

Frank Ivan
 

Hi John and all,

I have tried everything listed above on both a Pi3 and Pi4.  I can not see the sound card or the gps or even the sensor data.

Can someone do a new step by step or better still a video.  Maybe just a description of the kernel modules, dkms system, what is the udrc module used for and where to get it.  I am interested making a portable SOTA station running FT8 and JS8CALL maybe using flrig for rig control.

Not to put too sharp of a point on it, but Buster and Pi4 have been out just short of two months.  Downloading the stretch Compass gives you something that can not be updated.  Is there any projection when drivers for Buster and Pi 4 will be available or even a downloadable image.

As for the Pi 4 heat problem, just use the PoE HAT between the pi and DRAWS and put a small heat sink on the cpu.  It will not go above 58 C on a fully loaded system.

73 - Frank - K0FEI

 

I did this just yesterday
(from memory - not at system right now)
Download and burn Buster onto SD Card
Let it boot up and update/upgrade

sudo reboot
sudo apt install git build-essential
cd
cd n7nix/config
sudo ./image_install.sh
sudo apt install --fix-broken
sudo reboot

After boot try
aplay -l

Use n7nix scripts to install/config applications.
DRAWS™ Manager is at https://github.com/nwdigitalradio/draws-manager

On Mon, Aug 26, 2019 at 1:07 PM Frank Ivan via Groups.Io <k0fei=me.com@groups.io> wrote:
Hi John and all,

I have tried everything listed above on both a Pi3 and Pi4.  I can not see the sound card or the gps or even the sensor data.

Can someone do a new step by step or better still a video.  Maybe just a description of the kernel modules, dkms system, what is the udrc module used for and where to get it.  I am interested making a portable SOTA station running FT8 and JS8CALL maybe using flrig for rig control.

Not to put too sharp of a point on it, but Buster and Pi4 have been out just short of two months.  Downloading the stretch Compass gives you something that can not be updated.  Is there any projection when drivers for Buster and Pi 4 will be available or even a downloadable image.

As for the Pi 4 heat problem, just use the PoE HAT between the pi and DRAWS and put a small heat sink on the cpu.  It will not go above 58 C on a fully loaded system.

73 - Frank - K0FEI



--
John D. Hays
Kingston, WA
K7VE

 

Mike Watkins
 

On your Pi3/4 running Buster, please report the result from:

uname -a



On Mon., Aug. 26, 2019, 13:07 Frank Ivan via Groups.Io, <k0fei=me.com@groups.io> wrote:
Hi John and all,

I have tried everything listed above on both a Pi3 and Pi4.  I can not see the sound card or the gps or even the sensor data.

Can someone do a new step by step or better still a video.  Maybe just a description of the kernel modules, dkms system, what is the udrc module used for and where to get it.  I am interested making a portable SOTA station running FT8 and JS8CALL maybe using flrig for rig control.

Not to put too sharp of a point on it, but Buster and Pi4 have been out just short of two months.  Downloading the stretch Compass gives you something that can not be updated.  Is there any projection when drivers for Buster and Pi 4 will be available or even a downloadable image.

As for the Pi 4 heat problem, just use the PoE HAT between the pi and DRAWS and put a small heat sink on the cpu.  It will not go above 58 C on a fully loaded system.

73 - Frank - K0FEI

Frank Ivan
 

Hi John,

My results were not successful.

I am using a Pi 4 - 2gb memory with the Buster downloaded today.  I did not turn on anything except to connect to wifi.  After the install I did enable ssh.

uname -a

Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux

Changing to n7nix/bin

./sndcard.sh

No udrc sound card found.

aplay -l

**** List of PLAYBACK Hardware Devices ****

card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]

  Subdevices: 7/7

  Subdevice #0: subdevice #0

  Subdevice #1: subdevice #1

  Subdevice #2: subdevice #2

  Subdevice #3: subdevice #3

  Subdevice #4: subdevice #4

  Subdevice #5: subdevice #5

  Subdevice #6: subdevice #6

card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]

  Subdevices: 1/1

  Subdevice #0: subdevice #0

card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]

  Subdevices: 1/1

 

  Subdevice #0: subdevice #0

sudo lsmod

Module                  Size  Used by

rfcomm                 49152  4

bnep                   20480  2

hci_uart               40960  1

btbcm                  16384  1 hci_uart

serdev                 20480  1 hci_uart

bluetooth             389120  29 hci_uart,bnep,btbcm,rfcomm

ecdh_generic           28672  1 bluetooth

fuse                  110592  3

8021q                  32768  0

garp                   16384  1 8021q

stp                    16384  1 garp

llc                    16384  2 garp,stp

joydev                 20480  0

evdev                  24576  11

brcmfmac              311296  0

brcmutil               16384  1 brcmfmac

sha256_generic         20480  0

cfg80211              614400  1 brcmfmac

bcm2835_v4l2           45056  0

rfkill                 28672  6 bluetooth,cfg80211

bcm2835_codec          36864  0

snd_bcm2835            24576  2

v4l2_mem2mem           24576  1 bcm2835_codec

videobuf2_dma_contig    20480  1 bcm2835_codec

snd_pcm               102400  1 snd_bcm2835

bcm2835_mmal_vchiq     32768  2 bcm2835_codec,bcm2835_v4l2

v4l2_common            16384  1 bcm2835_v4l2

videobuf2_vmalloc      16384  1 bcm2835_v4l2

videobuf2_memops       16384  2 videobuf2_dma_contig,videobuf2_vmalloc

videobuf2_v4l2         24576  3 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem

videobuf2_common       45056  4 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2

snd_timer              32768  1 snd_pcm

raspberrypi_hwmon      16384  0

videodev              200704  6 bcm2835_codec,v4l2_common,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2

hwmon                  16384  1 raspberrypi_hwmon

snd                    73728  7 snd_timer,snd_bcm2835,snd_pcm

media                  36864  2 videodev,v4l2_mem2mem

vc_sm_cma              36864  1 bcm2835_mmal_vchiq

rpivid_mem             16384  0

uio_pdrv_genirq        16384  0

uio                    20480  1 uio_pdrv_genirq

fixed                  16384  0

ax25                   69632  0

i2c_dev                20480  0

ip_tables              24576  0

x_tables               32768  1 ip_tables

ipv6                  450560  30

Doesn't look like any of the modules are loading.

cat /boot/config.txt

# For more options and information see

# http://rpf.io/configtxt

# Some settings may impact device functionality. See link above for details

 

# uncomment if you get no picture on HDMI for a default "safe" mode

#hdmi_safe=1

 

# uncomment this if your display has a black border of unused pixels visible

# and your display can output without overscan

#disable_overscan=1

 

# uncomment the following to adjust overscan. Use positive numbers if console

# goes off screen, and negative if there is too much border

#overscan_left=16

#overscan_right=16

#overscan_top=16

#overscan_bottom=16

 

# uncomment to force a console size. By default it will be display's size minus

# overscan.

#framebuffer_width=1280

#framebuffer_height=720

 

# uncomment if hdmi display is not detected and composite is being output

#hdmi_force_hotplug=1

 

# uncomment to force a specific HDMI mode (this will force VGA)

#hdmi_group=1

#hdmi_mode=1

 

# uncomment to force a HDMI mode rather than DVI. This can make audio work in

# DMT (computer monitor) modes

#hdmi_drive=2

 

# uncomment to increase signal to HDMI, if you have interference, blanking, or

# no display

#config_hdmi_boost=4

 

# uncomment for composite PAL

#sdtv_mode=2

 

#uncomment to overclock the arm. 700 MHz is the default.

#arm_freq=800

 

# Uncomment some or all of these to enable the optional hardware interfaces

#dtparam=i2c_arm=on

#dtparam=i2s=on

#dtparam=spi=on

 

# Uncomment this to enable the lirc-rpi module

#dtoverlay=lirc-rpi

 

# Additional overlays and parameters are documented /boot/overlays/README

 

# Enable audio (loads snd_bcm2835)

dtparam=audio=on

 

[pi4]

# Enable DRM VC4 V3D driver on top of the dispmanx display stack

dtoverlay=vc4-fkms-v3d

max_framebuffers=2

 

[all]

#dtoverlay=vc4-fkms-v3d

 

# enable udrc/draws if no eeprom

dtoverlay=draws,alsaname=udrc

force_turbo=1

Doesn't look like /boot/config.txt got the dtparam=audio=on made it to the last line.

I am not sure why my results are so different.

Thanks
Frank - K0FEI

 




Frank Ivan
 

Hi John,

One thing more - I do see the hat

./udrcver.sh

Found a DRAWS

 

     HAT ID EEPROM

Name:        hat

Product:     Digital Radio Amateur Work Station

Product ID:  0x0004

Product ver: 0x0204

UUID:        2420cda1-931d-478c-80e5-d770f3346adb

Vendor:      NW Digital Radio

 

 

Frank,

Between your two emails, I am not sure of your current state.  Did you follow the steps I outlined earlier?

You should be seeing the card.

On Tue, Aug 27, 2019 at 1:40 PM Frank Ivan via Groups.Io <k0fei=me.com@groups.io> wrote:
Hi John,

One thing more - I do see the hat

./udrcver.sh

Found a DRAWS

 

     HAT ID EEPROM

Name:        hat

Product:     Digital Radio Amateur Work Station

Product ID:  0x0004

Product ver: 0x0204

UUID:        2420cda1-931d-478c-80e5-d770f3346adb

Vendor:      NW Digital Radio

 



--
John D. Hays
Kingston, WA
K7VE

 

Frank Ivan
 

Hi John,

I followed your steps exactly,.  The second post was some additional info to show that I could read the EEPROM and thus the hardware was working.

I think there is a  problem that the drivers are not being loaded.

Is there a log file for the image_install script?  Is there anything else I can send to you?

Thanks
Frank - K0FEI

Frank Ivan
 

Hi John,

If you would like to take this offline - my email address (at least the one in QRZ) is k0fei@....

Frank

 

Did you reboot after the steps? Then do the aplay -l?

The script is by Basil, N7NIX -- it worked for me.

On Tue, Aug 27, 2019 at 2:52 PM Frank Ivan via Groups.Io <k0fei=me.com@groups.io> wrote:
Hi John,

I followed your steps exactly,.  The second post was some additional info to show that I could read the EEPROM and thus the hardware was working.

I think there is a  problem that the drivers are not being loaded.

Is there a log file for the image_install script?  Is there anything else I can send to you?

Thanks
Frank - K0FEI



--
John D. Hays
Kingston, WA
K7VE

 

Frank Ivan
 

Hi John,

Yes - I rebooted as instructed.

I rebooted after doing the updates.

I rebooted after running the install_image.

As listed in the earlier post the aplay -l just talks about the bcm2835 ALSA device.

wsjtx cannot find an input device.

I have subsequently power down and booted.  Still no sound card.

Where you using a Pi3 or a Pi4?

Frank

Frank

 

Frank,

I did the install on 3B+, so I needed unpack and setup a Pi 4 (4GB) to verify it ran there as well.  I just moved over the SD Card to test.

Installation (using the 3B+)

    git clone https://github.com/nwdigitalradio/n7nix.git
   cd n7nix/config
   sudo ./image_install.sh
   sudo apt install --fix-broken
   sudo apt update
   sudo apt upgrade

After moving the SD Card to the Pi 4

pi@draws-buster:~ $ uname -m
armv7l
pi@draws-buster:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 7/7
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0


Telemetry from DRAWS™ Manager (Footer)
image.png
No Case. 


On Tue, Aug 27, 2019 at 7:00 PM Frank Ivan via Groups.Io <k0fei=me.com@groups.io> wrote:
Hi John,

Yes - I rebooted as instructed.

I rebooted after doing the updates.

I rebooted after running the install_image.

As listed in the earlier post the aplay -l just talks about the bcm2835 ALSA device.

wsjtx cannot find an input device.

I have subsequently power down and booted.  Still no sound card.

Where you using a Pi3 or a Pi4?

Frank

Frank



--
John D. Hays
Kingston, WA
K7VE

 

Edouard Lafargue
 

Would the same instructions also work with a UDRC-II card ? I tried them on Vanilla Buster with a RPi 3B+ with no success so far...

Ed

Jonathan Magee
 

Hi John and Frank
If you do take this off line and you get it working, please could you post to the list what steps were taken. I am having the same issue with my PI4 as Frank.

Regards
Jonathan GI7KMC
 


On Tue, 27 Aug 2019 at 23:10, Frank Ivan via Groups.Io <k0fei=me.com@groups.io> wrote:
Hi John,

If you would like to take this offline - my email address (at least the one in QRZ) is k0fei@....

Frank

Frank Ivan
 

Hi John,

I tried using a raspberry pi 3B and the same thing.
The aplay -l command did not return the card1 info.

This is beginning to look like a case of I can't get there from here.  Maybe someone else will chime in and say they did it or it didn't work for them.

I guess a couple of things to try.

1. Make an image of your SD card and upload it.
2. Did you do exactly what you listed including downloading the "latest" Buster and making a fresh SD card and downloading n7nix from the GitHub repository?  Maybe try it on a Pi4 although I have tried it on both.  It only takes about an hour depending on your internet speed and I have done it about 10 times.
\
Thanks
Frank - K0FEI