No display or audio

[Jdubaya]

I have installed sdrberry, and it seems to run.
I can see data streaming in the terminal, but there is no display or audio.

I used the WC12 option for display.
I am not using USB audio, though I see it is indicated in the config.

Do I need to rebuild with different options?

[paulh002]

I don't have any experience with the waveshare display, this option was added by some contributor. The software is optimised for 800 x 480 displays, but it can work for other sizes as well. You can edit sdrberry.cpp line 92 and 93 to set the correct display size. In file lv_conf.h you can set the colordepth if necessary. The audio adapter can be set in the GUI in the setup page or you can replace the device name in sdrberry_settings.cfg (use aplay -l to list the audio device name)

[Jdubaya]

I have the display up, but the mouse, keyboard, and touch are not working.
I was trying to run it in the GUI.
Did a little reading, and adjusted the config and cmdline to get the correct resolution.
Now the display works.

I think I need to rebuild with the DSI display.
Will that work with a 7" touch display?

Awesome project by the way!

[paulh002]

7" should work, that is the 800 x 480 raspberry pi display I have tested. Generic USB mouse should work. If not please share the log. The touch screen is selected based on the driver name. It can be that I need to add a specific driver name. But if you share the log I would be able to see the driver name. Just start sdrberry > log.txt and share the log file

[Jdubaya]

I have reinstalled everything.
I think the sound is not working because Alsa doesn't support HDMI.

For the rest. I start sdrberry, and the display comes up.
Nothing happens after that except that the clock works.
No signal, no touch, no keyboard. Nothing.

The display I am using is an iPistBit 7" touchscreen.
I have attached the latest log.

sdr3.txt

[paulh002]

Looks like sdrberry cannot access the radioberry device. Also i see pulse audio is active. Normally the installation script removes puls audio. Try starting sdrberry with sudo. Radioberry device can only be accessed with sudo rights. Or some other software is using it. Like the firmware service of radioberry. In that case you have to stop that one. Op za 26 okt. 2024 20:50 schreef Jdubaya ***@***.***>:

…

I have reinstalled everything. I think the sound is not working because Alsa doesn't support HDMI. For the rest. I start sdrberry, and the display comes up. Nothing happens after that except that the clock works. No signal, no touch, no keyboard. Nothing. The display I am using is an iPistBit 7" touchscreen. I have attached the latest log. sdr3.txt <https://github.com/user-attachments/files/17531670/sdr3.txt> — Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIOBYUBJQCI34YUKHHNMTXTZ5PP5TAVCNFSM6AAAAABQUUAAWOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBWGIYTMOI> . You are receiving this because you commented.Message ID: ***@***.***>

[Jdubaya]

Thank you!
Stopping the firmware service did it. I now have action on the screen.
Still no touch, mouse, or keyboard.
Is this something that is in a cfg file?

[paulh002]

I think you're using a logitech combined keyboard / mouse. Those keyboards do not identify them self as a separate mouse and keyboard. So it will not be recognised as such. I have such a keyboard my self but always use a microsoft mouse. Any usb mouse will do. But not (for now) those combined units do not work, i have to check if it can be added. Regarding touch what kind of touch driver does the display have? Touch driver names are also depended on the version of raspberry pi OS are you using Bullseye 64 bit? Or an older version?

[paulh002]

Maybe you can share the output of: cat /proc/bus/input/devices To see what devices are available.

[Jdubaya]

I am not sure which driver it is using. The screen plugs in to one of the usb ports.
I did not have to install anything.
I thing the overlay, dtoverlay = vc4-fkms-V3D, is disrupting something in the touch driver.
The instructions that come with the screen say to comment that out of config.txt, and I am using it to force 800x600 in CLI.
I am running bookworm on a pi4B.

[Jdubaya]

The keyboard / mouse are on separate usb receivers. They are Logitech.
Mayhap I need to pick up a new wireless mouse.

[paulh002]

The touch is working when you run the xwindows desktop? If so than the naming of the touch driver is different than most drivers. Please share the output of cat /proc/bus/input/devices that will list all devices. For the mouse I think Logitech just does not have "mouse" in the name. I can add this, that should not be a problem. The same for the touch driver.

[paulh002]

I updated the mouse detection, it is not using names any more so it should now also work for logitech. I also added your display name to the touch drivers. (this is a bit a guess) may be you can try that. To get the new version you can use the build version from git.
By executing the following steps:

cd sdrberry
git pull
git checkout build
cd build
cmake ..
make -j4
sudo make install

[Jdubaya]

Thanks!
I will pull it and see.
Attached my devices. It seems my screen is a knock off of waveshare.
Mouse and keyboard both work in gui and CLI until I start sdrberry.

devices.txt

[Jdubaya]

It seems to be working better kind of.
I have one mouse that works. Touch works. Keyboard works.
The GUI is having issues now though.

https://quickshare.samsungcloud.com/ta4DqK114GX6

[paulh002]

The console output is also writing to the framebuffer.
Start sdrberry like this

sdrberry >/dev/null 2>&1

An other option is to copy sdrstart.sh from the install directory to /home/pi and use crontab for auto start

cp ./sdrberry/install/sdrstart.sh .
chmod +x sdrstart.sh
cp ./sdrberry/install/crontab .
crontab crontab

sudo reboot

Now sdrberry will start when you switch the pi on

[Jdubaya]

That fixed it. everything seems to be working that is installed now.
The touch needs to be calibrated, but is working.
The PulseAudio and bcm headphones options kind of give me audio. I have a couple of USB adapters coming today.
The keyboard works, but the top row numbers are giving symbols instead of numbers, and the num lock won't turn on.

WSJTX is receiving, and decoding, but I can't seem to transmit.
Tuning frequency must mainly be done with the encoder and keypad you built?

This is an amazing project!

[paulh002]

You need usb audio adapter for transmit, I use the timing from the audio input also for ft8. So without audio input it will not work. The key board I guess you are not using a US keyboard. There is no api in Linux kernel for translating keyboards. I did not implement different keyboards like French or German. But you could change the keys can table. I have to check the library from where i got it. It probably has some options. For tuning there are several options, you can use some hid devices there are cheap one on AliExpress sold as external volume knobs. I also use a video jog. The encoder I build is a esp32 with optical encoder which works very well. The sdrberry supports cat interface and the esp32 just sends cat codes for tuning. I use a esp32 with small display as a 2nd display it also is used as swr meter. The code is in my GitHub. You could just take a esp32 dev board and connect a optical encoder with some pull up resistors. That should work.