Audio/MIDI error screen

Building Zynthian
1

Hello,
I just finished building my v5.1 and I’m getting an error screen with the message “Audio/MIDI”.
I’ve accessed the webconf and this is the UI Log:

Restarting UI in debug mode
Sep 25 22:03:44 zynthian systemd[1]: Started zynthian_debug.service - Zynthian User Interface (DEBUG).
Sep 25 22:03:44 zynthian startx[2223]: X.Org X Server 1.21.1.7
Sep 25 22:03:44 zynthian startx[2223]: X Protocol Version 11, Revision 0
Sep 25 22:03:44 zynthian startx[2223]: Current Operating System: Linux zynthian 6.6.47-v8-16k+ #1794 SMP PREEMPT Thu Aug 29 16:30:28 BST 2024 aarch64
Sep 25 22:03:44 zynthian startx[2223]: Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=2C:CF:67:76:2C:13 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 root=PARTUUID=e249d476-02 rootfstype=ext4 fsck.repair=yes rootwait console=tty1 logo.nologo modules-load=dwc2,libcomposite
Sep 25 22:03:44 zynthian startx[2223]: xorg-server 2:21.1.7-3+rpt3+deb12u7 (https://www.debian.org/support)
Sep 25 22:03:44 zynthian startx[2223]: Current version of pixman: 0.42.2
Sep 25 22:03:44 zynthian startx[2223]: Before reporting problems, check http://wiki.x.org
Sep 25 22:03:44 zynthian startx[2223]: to make sure that you have the latest version.
Sep 25 22:03:44 zynthian startx[2223]: Markers: (--) probed, (**) from config file, (==) default setting,
Sep 25 22:03:44 zynthian startx[2223]: (++) from command line, (!!) notice, (II) informational,
Sep 25 22:03:44 zynthian startx[2223]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Sep 25 22:03:44 zynthian startx[2223]: (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 25 22:03:44 2024
Sep 25 22:03:44 zynthian startx[2223]: (==) Using config directory: "/etc/X11/xorg.conf.d"
Sep 25 22:03:44 zynthian startx[2223]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Sep 25 22:03:46 zynthian startx[2239]: ----------------------------------------------
Sep 25 22:03:46 zynthian startx[2239]: Linux Version: bookworm
Sep 25 22:03:46 zynthian startx[2239]: Kernel Version: 6.6.47-v8-16k+
Sep 25 22:03:46 zynthian startx[2239]: ZynthianOS Version: 2409
Sep 25 22:03:46 zynthian startx[2239]: Virtualization: none
Sep 25 22:03:46 zynthian startx[2239]: Hardware Architecture: aarch64
Sep 25 22:03:46 zynthian startx[2239]: Hardware Model: Raspberry Pi 5 Model B Rev 1.0
Sep 25 22:03:46 zynthian startx[2239]: ----------------------------------------------
Sep 25 22:03:46 zynthian startx[2268]: /zynthian/config/img/fb_zynthian_boot.jpg is a 800x480 JPEG image, color space Grayscale, 1 comp, Huffman coding.
Sep 25 22:03:46 zynthian startx[2268]: Zooming image by 100%...done
Sep 25 22:03:46 zynthian startx[2268]: Merging...didn't find evidence of prior run.
Sep 25 22:03:46 zynthian startx[2268]: done
Sep 25 22:03:46 zynthian startx[2268]: Building XImage...done
Sep 25 22:03:46 zynthian startx[2269]: INFO:zynthian_gui_config.<module>: ZYNTHIAN-UI CONFIG ...
Sep 25 22:03:46 zynthian startx[2269]: INFO:zynthian_gui_config.<module>: No Wiring Layout configured. Only touch interface is available.
Sep 25 22:03:46 zynthian startx[2269]: ZynCore: Configured 8 x Logical Zynswitches...
Sep 25 22:03:46 zynthian startx[2269]: ZynCore: Setting-up 0 x Physical Zynswitches...
Sep 25 22:03:46 zynthian startx[2269]: ZynCore: Setting-up 0 x Zynpots (zyncoders)...
Sep 25 22:03:46 zynthian startx[2269]: Cannot connect to server socket err = No such file or directory
Sep 25 22:03:46 zynthian startx[2269]: Cannot connect to server request channel
Sep 25 22:03:46 zynthian startx[2269]: jack server is not running or cannot be started
Sep 25 22:03:46 zynthian startx[2269]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 25 22:03:46 zynthian startx[2269]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 25 22:03:46 zynthian startx[2269]: ZynMidiRouter: Error connecting with jack server.
Sep 25 22:03:46 zynthian startx[2269]: ERROR:zynthian_gui_config.<module>: lib_zyncore: Failed to initialise zynmidirouter (2)
Sep 25 22:03:46 zynthian startx[2239]: *******************
Sep 25 22:03:46 zynthian startx[2239]: EXIT STATUS => 202
Sep 25 22:03:46 zynthian startx[2239]: *******************
Sep 25 22:03:46 zynthian startx[2284]: /zynthian/config/img/fb_zynthian_message.jpg is a 800x480 JPEG image, color space YCbCr, 3 comps, Huffman coding.
Sep 25 22:03:46 zynthian startx[2284]: Zooming image by 100%...done
Sep 25 22:03:46 zynthian startx[2284]: Merging...done
Sep 25 22:03:46 zynthian startx[2284]: Building XImage...done
Sep 25 22:03:57 zynthian startx[2295]: INFO:zynthian_gui_config.<module>: ZYNTHIAN-UI CONFIG ...
Sep 25 22:03:57 zynthian startx[2295]: INFO:zynthian_gui_config.<module>: No Wiring Layout configured. Only touch interface is available.
Sep 25 22:03:57 zynthian startx[2295]: ZynCore: Configured 8 x Logical Zynswitches...
Sep 25 22:03:57 zynthian startx[2295]: ZynCore: Setting-up 0 x Physical Zynswitches...
Sep 25 22:03:57 zynthian startx[2295]: ZynCore: Setting-up 0 x Zynpots (zyncoders)...
Sep 25 22:03:57 zynthian startx[2295]: Cannot connect to server socket err = No such file or directory
Sep 25 22:03:57 zynthian startx[2295]: Cannot connect to server request channel
Sep 25 22:03:57 zynthian startx[2295]: jack server is not running or cannot be started
Sep 25 22:03:57 zynthian startx[2295]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 25 22:03:57 zynthian startx[2295]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 25 22:03:57 zynthian startx[2295]: ZynMidiRouter: Error connecting with jack server.
Sep 25 22:03:57 zynthian startx[2295]: ERROR:zynthian_gui_config.<module>: lib_zyncore: Failed to initialise zynmidirouter (2)
Sep 25 22:03:57 zynthian startx[2239]: *******************
Sep 25 22:03:57 zynthian startx[2239]: EXIT STATUS => 202
Sep 25 22:03:57 zynthian startx[2239]: *******************
Sep 25 22:03:57 zynthian startx[2310]: /zynthian/config/img/fb_zynthian_message.jpg is a 800x480 JPEG image, color space YCbCr, 3 comps, Huffman coding.
Sep 25 22:03:57 zynthian startx[2310]: Zooming image by 100%...done
Sep 25 22:03:57 zynthian startx[2310]: Merging...done
Sep 25 22:03:57 zynthian startx[2310]: Building XImage...done
Sep 25 22:04:07 zynthian startx[2321]: INFO:zynthian_gui_config.<module>: ZYNTHIAN-UI CONFIG ...
Sep 25 22:04:07 zynthian startx[2321]: INFO:zynthian_gui_config.<module>: No Wiring Layout configured. Only touch interface is available.
Sep 25 22:04:08 zynthian startx[2321]: ZynCore: Configured 8 x Logical Zynswitches...
Sep 25 22:04:08 zynthian startx[2321]: ZynCore: Setting-up 0 x Physical Zynswitches...
Sep 25 22:04:08 zynthian startx[2321]: ZynCore: Setting-up 0 x Zynpots (zyncoders)...
Sep 25 22:04:08 zynthian startx[2321]: Cannot connect to server socket err = No such file or directory
Sep 25 22:04:08 zynthian startx[2321]: Cannot connect to server request channel
Sep 25 22:04:08 zynthian startx[2321]: jack server is not running or cannot be started
Sep 25 22:04:08 zynthian startx[2321]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 25 22:04:08 zynthian startx[2321]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 25 22:04:08 zynthian startx[2321]: ZynMidiRouter: Error connecting with jack server.
Sep 25 22:04:08 zynthian startx[2321]: ERROR:zynthian_gui_config.<module>: lib_zyncore: Failed to initialise zynmidirouter (2)
Sep 25 22:04:08 zynthian startx[2239]: *******************
Sep 25 22:04:08 zynthian startx[2239]: EXIT STATUS => 202
Sep 25 22:04:08 zynthian startx[2239]: *******************
Sep 25 22:04:08 zynthian startx[2336]: /zynthian/config/img/fb_zynthian_message.jpg is a 800x480 JPEG image, color space YCbCr, 3 comps, Huffman coding.
Sep 25 22:04:08 zynthian startx[2336]: Zooming image by 100%...done
Sep 25 22:04:08 zynthian startx[2336]: Merging...done
Sep 25 22:04:08 zynthian startx[2336]: Building XImage...done
Sep 25 22:04:18 zynthian startx[2347]: INFO:zynthian_gui_config.<module>: ZYNTHIAN-UI CONFIG ...
Sep 25 22:04:18 zynthian startx[2347]: INFO:zynthian_gui_config.<module>: No Wiring Layout configured. Only touch interface is available.
Sep 25 22:04:18 zynthian startx[2347]: ZynCore: Configured 8 x Logical Zynswitches...
Sep 25 22:04:18 zynthian startx[2347]: ZynCore: Setting-up 0 x Physical Zynswitches...
Sep 25 22:04:18 zynthian startx[2347]: ZynCore: Setting-up 0 x Zynpots (zyncoders)...
Sep 25 22:04:18 zynthian startx[2347]: Cannot connect to server socket err = No such file or directory
Sep 25 22:04:18 zynthian startx[2347]: Cannot connect to server request channel
Sep 25 22:04:18 zynthian startx[2347]: jack server is not running or cannot be started
Sep 25 22:04:18 zynthian startx[2347]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 25 22:04:18 zynthian startx[2347]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Sep 25 22:04:18 zynthian startx[2347]: ZynMidiRouter: Error connecting with jack server.
Sep 25 22:04:18 zynthian startx[2347]: ERROR:zynthian_gui_config.<module>: lib_zyncore: Failed to initialise zynmidirouter (2)
Sep 25 22:04:18 zynthian startx[2239]: *******************
Sep 25 22:04:18 zynthian startx[2239]: EXIT STATUS => 202
Sep 25 22:04:18 zynthian startx[2239]: *******************
Sep 25 22:04:18 zynthian startx[2362]: /zynthian/config/img/fb_zynthian_message.jpg is a 800x480 JPEG image, color space YCbCr, 3 comps, Huffman coding.
Sep 25 22:04:18 zynthian startx[2362]: Zooming image by 100%...done
Sep 25 22:04:18 zynthian startx[2362]: Merging...done
Sep 25 22:04:18 zynthian startx[2362]: Building XImage...done

I’m using the latest stable image, so I don’t know what can be the problem.
What can I check?

Oh, and another interesting thing that happened to me: the screen is upside down, even though I followed the instructions carefully. Can this be modified by any config?
Thanks!

UPDATE: I’ve accessed the terminal and I think the sound card is not detected. In the terminal I did:

root@zynthian://zynthian# aplay -l                                              
**** List of PLAYBACK Hardware Devices ****                                     
root@zynthian://zynthian# aplay -L                                              
null                                                                            
    Discard all samples (playback) or generate zero samples (capture)

I’ve checked the 2 rows of 20-pin connection between the RPi5 and the main board and it looks good. Can I do any other check?

UPDATE 2: I’ve gone through the bizarre issues thread and I noticed that @allordacia seems to have a similar problem than mine.
Here’s my /root/first_boot.log:

                                                                                
Running autoconfig...                                                           
Detected I2C Chips: ['PCM1863@0x4A', 'PCM5242@0x4D', 'RV3028@0x52', 'TPA6130@0x6
0']                                                                             
Checking Boards: ['V5_MAIN', 'V5_CONTROL']                                      
ERROR: Undetected Hardware ['MCP23017@0x20', 'MCP23017@0x21']                   
Checking Boards: ['Z2_MAIN', 'V5_CONTROL']                                      
ERROR: Undetected Hardware ['MCP23017@0x20', 'MCP23017@0x21']                   
Checking Boards: ['Z2_MAIN', 'Z2_CONTROL']                                      
ERROR: Undetected Hardware ['MCP23017@0x20', 'MCP23017@0x21', 'ADS1115@0x48', 'A
DS1115@0x49']                                                                   
Checking Boards: ['Z2_MAIN_BETA', 'Z2_CONTROL']                                 
ERROR: Undetected Hardware ['MCP23017@0x20', 'MCP23017@0x21', 'ADS1115@0x48', 'A
DS1115@0x49']                                                                   
Checking Boards: ['ZynADAC', 'ZynScreen']                                       
ERROR: Undetected Hardware ['MCP23017@0x20']                                    
Checking Boards: ['HifiBerryDAC+', 'ZynScreen']                                 
ERROR: Undetected Hardware ['MCP23017@0x20']                                    
Detected Custom kit!                                                            
Configuring Zynthian for Custom ...
                                                                                
Reboot...                                                                       
                                                                                
Running autoconfig...                                                           
Detected I2C Chips: ['PCM1863@0x4A', 'PCM5242@0x4D', 'RV3028@0x52', 'TPA6130@0x6
0']                                                                             
Checking Boards: ['V5_MAIN', 'V5_CONTROL']                                      
ERROR: Undetected Hardware ['MCP23017@0x20', 'MCP23017@0x21']                   
Checking Boards: ['Z2_MAIN', 'V5_CONTROL']                                      
ERROR: Undetected Hardware ['MCP23017@0x20', 'MCP23017@0x21']                   
Checking Boards: ['Z2_MAIN', 'Z2_CONTROL']                                      
ERROR: Undetected Hardware ['MCP23017@0x20', 'MCP23017@0x21', 'ADS1115@0x48', 'A
DS1115@0x49']                                                                   
Checking Boards: ['Z2_MAIN_BETA', 'Z2_CONTROL']                                 
ERROR: Undetected Hardware ['MCP23017@0x20', 'MCP23017@0x21', 'ADS1115@0x48', 'A
DS1115@0x49']                                                                   
Checking Boards: ['ZynADAC', 'ZynScreen']                                       
ERROR: Undetected Hardware ['MCP23017@0x20']                                    
Checking Boards: ['HifiBerryDAC+', 'ZynScreen']                                 
ERROR: Undetected Hardware ['MCP23017@0x20']                                    
Detected Custom kit!                                                            
Zynthian already configured for Custom.                                         
                                                                                
Fixing ALSA mixer settings...                                                   
                                                                                
Regenerating keys...    
Removing current webconf cookie secret...                                       
A new webconf cookie secret will be generated on next request.                  
Removing current system SSH keys...                                             
Generating new system SSH keys...                                               
Generating public/private rsa key pair.                                         
Your identification has been saved in /etc/ssh/ssh_host_rsa_key                 
Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub                 
The key fingerprint is:                                                         
SHA256:VtJwwwfVWF0fJ7c59dWYnx4OaqHN0TW5sTwhrZ/jrdc root@zynthian                
The key's randomart image is:                                                   
+---[RSA 3072]----+                                                             
|        ..+o.++=X|                                                             
|         +..o.+X%|                                                             
|        . o.. ==X|                                                             
|         o o + Bo|                                                             
|        S + + = +|                                                             
|       . . =   * |                                                             
|          .   . +|                                                             
|               .E|                                                             
|              .o |                                                             
+----[SHA256]-----+                                                             
Generating public/private dsa key pair.                                         
Your identification has been saved in /etc/ssh/ssh_host_dsa_key 
Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub                 
The key fingerprint is:                                                         
SHA256:zt4TWpHg47hYcNFvwWNWJ26+Uo0hcvY474euvs8licA root@zynthian                
The key's randomart image is:                                                   
+---[DSA 1024]----+                                                             
|       . . .o .  |                                                             
|      . o *. o   |                                                             
|       o.=+++    |                                                             
|    . ..o+=* +   |                                                             
|     o oEoo.= .  |                                                             
|      oo..o= o   |                                                             
|     o .ooo.=..  |                                                             
|    . .....+.o.  |                                                             
|        ..=*=.   |                                                             
+----[SHA256]-----+                                                             
Generating public/private ecdsa key pair.                                       
Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key               
Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub               
The key fingerprint is:                                                         
SHA256:+WpDKR+Bq9piClV4/BT0Uz2wuJDc04fs/UE/qB1u0is root@zynthian                
The key's randomart image is:                                                   
+---[ECDSA 256]---+                                                             
|     .o   oo     |                
|   o . = = oo    |                                                             
|  . + =.* = ...  |                                                             
|   o o...* o ... |                                                             
|  .   ..So. .o...|                                                             
| .    o +.  =....|                                                             
|.    . + ..o =.  |                                                             
|. o..   +. Eo .  |                                                             
|.o.o.  ...  ..   |                                                             
+----[SHA256]-----+                                                             
Restarting SSH server ...                                                       
Removing current SSL certificate...                                             
Generating new SSL certificate for 100 years...                                 
Resizing partition...

And I also had to do the EEPROM recovery thing.

Xavier

2

It seems your control boards is not well connected, what prevents the correct detection of your kit.
Re-check the connection, putting attention to cable orientation and reset your SD card by running:

set_first_boot.sh

Wait until the system is shutdown. Then power off / power on. If it’s well connected it should configure your V5.1.

Regards

3

That made it! Now it booted correctly and even the screen orientation is correct!
Thank you so much!

1 Like
4

There is an easy way of expressing your gratitude…

2 Likes
5

@gregdulli did you have to change your cable orientation or other physical changes? It is useful for us to know whether this issue is due to construction issue or software so that we can improve the guides or fix the software.

Cheers

6

I’ve checked in the building guide and it’s quite clear about it:

2. Using two fingers, one on each hand, softly pull the main board’s control-1 connector tongue until it’s open. Insert the flat ribbon cable coming from the control board (top part). Do it straight, without bending or twisting it in any way, so the blue side is face down.

Anyway, I’ve edited the guide to “bold” the “the blue side is face down” fragment.

Regards,

2 Likes
7

I didn’t have to change anything, the box was correctly built. I just had to run the set_first_boot.sh script and restart, and everything was fixed, including the orientation of the screen.

The thing was that after doing the EEPROM recovery thing I once ran the raspberry without the connectors plugged, so the initial setup could not be made.

@jofemodo I think the guide is very clear in all steps. I would only suggest 2 changes:

  1. In step 3.3 Plug the display ribbon cable into the RPi5, in point 3 it says (in bold) “All flat cables in the V5 kit are reversible, so you can take any of the 2 caps”, but I believe this doesn’t apply in this case because RPi5’s DSI connector is narrower than RPi4’s, so the cable only can be connected in one direction.

  2. In step 3.4 Install the thermal block, in point 8 it says “stick the remaining piece of thermal pad (27 x 20 mm) on the contact surface in the external side of the thermal block” but it wasn’t clear to me what side did I have to stick to the thermal block (or if it even matters). In the previous steps it was stated that I had to first remove the blue protective sheet and stick that side, but in this case it was not specified and the image shows the blue protective sheet on top.

4 Likes
8

I wonder if there may be benefit in having a script that checks the firmware version at boot and updates it to a known good version if a bad one is detected. The following command provides information about the bootloader version:

vcgencmd bootloader_version

in the format:

My RPi4:

2024/07/30 14:02:35
version 5f18ffb61682740ed1751ba59952843d7521314f (release)
timestamp 1722344555
update-time 1724391075
capabilities 0x0000007f

My RPi5:

2024/09/10 14:40:30
version 5be4f304b152e06cbcb9c08c26aafc9da755ae47 (release)
timestamp 1725975630
update-time 1726168243
capabilities 0x0000007f
9

I doubt it’s strongly related to revision/version numbers. I imagine they test all chips at some standarized “test” frequency, probably slighty higher than the nominal freq. Some chips pass and some not. Chips rejected SHOULD be destroyed or labeled for a different application so they don’t end “by error” in a Pi5 board. Each chip from the good ones will have an unknown MWF value (maximum working frequency) that it can support while keeping stability. This MWF value would be distributed in a Gauss bell (or kind of), with an average and a variance. This average and variance could depend of batch number, manufacturing location, weekday, moon phase, sun activity, etc. but individual value for MWF is a lottery.

My 2 cents :wink:

1 Like
10

I am talking about bootloader firmware version, not oversampling.

11

Sorry mate, i read too fast this morning! :smiling_face:

Regarding firmware, the mechanism for recovering firmware on first boot is prepared to deploy, but i wanted to see how things work without it.

For testing this auto-recovering feature you simply run:

rpi_eeprom_reset.sh

and the firmware from /zynthian/zynthian-sys/boot folder will be recovered on next boot.

This reset command is commented in the “set_first_boot.sh” script, but it can be enabled as soon as we decide this is really needed.

Regards,

1 Like
12

Does this add to boot time? WE may be able to test whether it is needed with vcgencmd bootloader_version before calling rpi_eeprom_reset.sh.

13

Yes. It’s an extra reboot to add to the first boot process, but a short one because it don’t load the SO.

If system doesn’t boot because of the bootloader, you can’t run vcgencmd nor anything else. You have no SO.

Regards,

1 Like