The Zynthian on Zero saga . .


#1

Note to self.

The connector on a raspberry Pi zero is an HDMI mini.

This is not the same as the micro HDMI ordered from amazon. . .

I will be leaving the room with a bottle of whiskey and a revolver.
No flowers. . .


#2

And that’s why I bought a Pi Zero starter kit with a bundled whateverHDMI to standart HDMI adapter :slight_smile:

(had a previous similar experience with a stupid Samsung camera with a stupid custom HDMI connector)


#3

OK.
I’ve now got a Mini HDMI connector & can now start up a Pi Zero with Audio Injector board and a micro usb hub.

So starting up on the zero:

Well I can see the zynth start up, but the splash screen displays but obviously at the wrong resolution and it clears to be replaced with the zyhian error splash screen.
Sadly I still don’t get wifi access so it’s rather difficult to actual see what is going wrong.

So transferring back to the normal zynthlite (Audio injector, HDMI, no encoders)

I have considerable trouble starting the wifi.
The gui component doesn’t start it: The webconf sees the network, but upon starting with just WiFi and using my new favourite trick to bring up a terminal (CNTRL/ALT/Function key)

I can use ifconfig to see eth0 / lo and wlan0 but no
IPaddress in wlan.

So now with the zythian-nord ssd back in the zynthian zero and the new power grip (Cntr/Alt/Function key) I can get a prompt on the zero…

… but I can’t get in before the zynthian system ctl process restarts …

Yes you can… :slight_smile: if you type regardlessly …

so
systemctl stop zynthian gets you a slightly better behaving zynthian zero…


#4

Downloaded recent .img updasted wifi not turning on . . .

zyncoder: master (c13d120)
zynthian-ui: master (50f785e)
zynthian-sys: master (dde2f79)
zynthian-data: master (40dd1f1)
zynthian-webconf: master (5afcfd5)


#5

I’m super interested to watch this thread: a zynthian over raspberry zero with only setBFree engine and a full drawbar controller, like the Ferrofish B4000+ =) just dreaming


#6

And We have wifi network on a raspberry Pi 3 zynthlite. . .

Open up the Wifi Section under System and press Advanced Config.

This allows you access to the /etc/wpa_supplicant/wpa_supplicant.conf file

and add the network details at the end. . . .
remembering also to change the country code (GB in my case . . .)

Remember to include your own psk . . .
It is replaced by **** in the webconf ( Nice …)

IF you wish to be more secure read on here . . .

Raspberry Pi WiFi

Now to try this in a zero…

and partial success (finally) logging onto an audio injector equipped raspberry pi zero via Putty as zynthian.local from an updated version of the current image.

Hasn’t got webconf as yet . . .

So using my newly configured Putty access

cd /zynthian/zynthian-webconf
python3 zynthian_webconf.py ( I will NEVER remember when its underscore and when its htphen …)

we get…

cd /zynthian/zynthian-webconf
root@zynthian:/zynthian/zynthian-webconf# python3 zynthian_webconf.py
Illegal instruction
root@zynthian

Hmmmmmm . . . .

Tried setting the kernel image explicitly …
Not helped more to read…

Presumably the ARMv6 versus the quad-core Cortex-A53 ARMv8-A 32bit versus 64 bit . . .

So I’ll try to tackle the misdisplayed Zynthian splash screen. . . .

> root@zynthian:~# tvservice -status
> state 0x12000a [HDMI DMT (39) RGB full 16:9], 1360x768 @ 60.00Hz, progressive
> 
> 
> #uncomment to force a console size. By default it will be display's size minus
> #overscan.
> framebuffer_width=1360
> framebuffer_height=768
> 
> #uncomment if hdmi display is not detected and composite is being output
> #hdmi_force_hotplug=1
> 

Ok not right . .

Try a different resolution . . .

>  #uncomment to force a specific HDMI mode (this will force VGA)
> hdmi_group=2
> hdmi_mode=35

And that works a proper splash screen at last . . .

> root@zynthian:~# tvservice -status
> state 0x12000a [HDMI DMT (35) RGB full 5:4], 1280x1024 @ 60.00Hz, progressive
> root@zynthian:~#

#7

Isn’t it .sh? Just run it.


#8

Yes. I just prefer getting a little close to the core functionality for error messages.

The result is the same illegal operation . . . .