piCoPlayerV2 (26MB with WiFi, SSH, squeezelite and set-up)

[sbp]

Hi I have update the piCoPlayer.

piCoPlayer is a dedicated player (like a Duet receiver) build on a small read-only linux (Microcore) and Triodes excellent Squeezelite player.
It is now even smaller than the first version (26 MB in total). There is no writing to the SD-card and therefore no risk of corruption of your card - just pull the power if you need to. After booting everything is sitting in RAM.

Out of the box, the analog audio via the 3.5" jack is working.

If you want to use a USB DAC, you will need to supply the correct squeezelite commands - for this you can use the setup menu.

The setup-script can be used in two different ways:
1. Connect via SSH (use putty from another computer on the same LAN (user=tc, password=nosoup4you)). At the command promt write; picoplayer which will start the setup-script.
2. If you have a keyboard and screen connected to your raspberry. At the command promt write: picoplayer which will start the setup-script.


The WiFi is supposed to work - I have not tested it, but I have seen a few reports that it is working on the piCore linux which is used for building this player. Please test it and report your findings.

Also suggestions in improving the set-up script is welcome.

The piCoPlayer image can be downloaded here:
http://rapidshare.com/files/2536786570/ ... yer_v2.img

Regards
STeen



Changes from version 1:

1. WiFi included (needs further testing)
2. Even smaller now (26 MB)
3. Is optimized for both 256 and 512 MB Raspberry boards
4. SSH access via Dropbear. User = tc Password = nosoup4you
5. Analog and USB sound is tested and is working
6. Included is a set-up menu that makes it easy to:
a. Download and update Squeezelite
b. Auto setup for analog audio from 3.5 jack
c. Detect and show the available USB devices
d. Option to easily change the squeezelite options (output, name MAC address etc)
e. Save these changes so they survive a reboot on the "read-only" microcore structure
f. Reboot to start using the changes.

[drgeoff]

I was expecting the setup script to include Wi-Fi.

Since it does not, what about some pointers in this thread on how to do that?

It wasn't obvious to me that menu option 5 does the save. Initially I thought that was just a comment line and option 6 would do the save and the reboot.

[drgeoff]

I was expecting the setup script to include Wi-Fi.

Since it does not, what about some pointers in this thread on how to do that?

wifi.sh seems to be the way but the whole setup seems very flakey compared to the previous version of piCoplayer which was rock solid. I need to spend more time on this.

[sbp]

I was expecting the setup script to include Wi-Fi.

Since it does not, what about some pointers in this thread on how to do that?

wifi.sh seems to be the way but the whole setup seems very flakey compared to the previous version of piCoplayer which was rock solid. I need to spend more time on this.

Thanks for your feedback. I'm sorry for your disappointment with the wifi part. As already described I have not tested it myself as my wifi card has not arrived yet. As soon as I get it I will update the info on this part.
However, here is a description on two who succeeded in using a wifi card in microcore: http://forum.tinycorelinux.net/index.ph ... 491.0.html

way but the whole setup seems very flakey compared to the previous version of piCoplayer which was rock solid. I need to spend more time on this.

Could you please elaborate on this.
Do you have problems with the piCoPlayer - is it more unstable now that the first version?
Or it is the menu-script that needs attention?
Do you have suggestions for improvements?
Should I remove the "save changes menu point", and let it save before a reboot.

All suggestions are welcome.

[drgeoff]

I have occasionally got the Wi-Fi to connect with a Realtek based 150Mbit/s nano-dongle but issues include the following:

1. The dongle isn't always recognised. wifi.sh often reports no wi-fi devices.
2. wifi.sh never finds any networks the first time it scans. A second run usually does.
3, The driver for Ralink 5370 dongle seems broken. dmesg says something like "error; undefined symbol" and wifi.sh always reports "no wifi devices".
4. Although the WPA key is memorised and does not need to be re-entered after a reboot, the Wi-Fi connection is not automatically establiished. Running wifi.sh from an attached keyboard of over ssh (need the LAN port cabled up!) is necessary after every reboot.
5. I've encountered keyboard problems of seemingly dead keyboard or lots and lots of command prompts with various combinations of keyboard , USB dongle ans PCM2704 USB DAC. But these may be the well known RPi USB problem and not down to piCorePlayer.

I'd like to get to the situation of the RPi plus Wi-Fi dongle in one USB socket plus USB DAC in the other and automatically connecting to Wi-Fi router on power-up.

I don't think you need to delete menu item 5 and combine with 6. Just make it clearer that it is 5 which does the save.

[sbp]

I have occasionally got the Wi-Fi to connect with a Realtek based 150Mbit/s nano-dongle but issues include the following:

1. The dongle isn't always recognised. wifi.sh often reports no wi-fi devices.
2. wifi.sh never finds any networks the first time it scans. A second run usually does.

Hi thanks for the clarification.
I found this info from Gerrelt in the microcore forum:

"I also added this line to bootlocal.sh to make it connect at startup:

/usr/local/bin/wifi.sh -a 2>&1 > /tmp/wifi.log

But that didn't work at first. I had to add the line again (so two of the same lines) to get it working.

I allready noticed when executing wifi.sh by hand it only worked the second time."

It look like the same problem you are describing.

3, The driver for Ralink 5370 dongle seems broken. dmesg says something like "error; undefined symbol" and wifi.sh always reports "no wifi devices".
4. Although the WPA key is memorised and does not need to be re-entered after a reboot, the Wi-Fi connection is not automatically establiished. Running wifi.sh from an attached keyboard of over ssh (need the LAN port cabled up!) is necessary after every reboot.

I think that is connected with the issue above, that somehow you need the same line twice in the bootlocal.sh file. If that is coorect I will add a menu item in the set-up script that allows for these lines to be easyly inserted. So could you please test this?

5. I've encountered keyboard problems of seemingly dead keyboard or lots and lots of command prompts with various combinations of keyboard , USB dongle ans PCM2704 USB DAC. But these may be the well known RPi USB problem and not down to piCorePlayer.

I'd like to get to the situation of the RPi plus Wi-Fi dongle in one USB socket plus USB DAC in the other and automatically connecting to Wi-Fi router on power-up.

OK, is this problem with dead keyboard worse in the new version compared with the first version?
Also how is the stability with the player after you have it playing?

My goal is the same as yours, to get piCoPlayer automatically to connect - so hopefully we will get there.

I don't think you need to delete menu item 5 and combine with 6. Just make it clearer that it is 5 which does the save.

[/quote]

Fine I will change the menu item text.

[magiczambo]

Hello,

is it possible to start the piCorePlayer more than one time, in order to have different outputs on one Raspi?

Thanks in Advance

[drgeoff]

Hello,

is it possible to start the piCorePlayer more than one time, in order to have different outputs on one Raspi?

Thanks in Advance

Why don't you try it yourself and let us know the answer?

Or is your question really. "How can I start picoreplayer more than once?"

[magiczambo]

Hello,

is it possible to start the piCorePlayer more than one time, in order to have different outputs on one Raspi?

Thanks in Advance

Why don't you try it yourself and let us know the answer?

Or is your question really. "How can I start picoreplayer more than once?"

Yes, that could be another way to ask the question for me the same question

[Paul Webster]

Under the covers, is it using Squeezelite?
If yes - then iI would expect it to be possible to do it by hand by simply running Squeezelite with different outputs (controlled by command line).
If you can get that working first then next step would be to see if the scripts used by picoplayer support it ... and if not then adapting them or persuading the maintainer to make some updates.

[drgeoff]

Under the covers, is it using Squeezelite?

Yes.

[magiczambo]

Under the covers, is it using Squeezelite?
If yes - then iI would expect it to be possible to do it by hand by simply running Squeezelite with different outputs (controlled by command line).
If you can get that working first then next step would be to see if the scripts used by picoplayer support it ... and if not then adapting them or persuading the maintainer to make some updates.

Yes i can start two squeezelites with different outputs, but within the squeezbox player I always see only one player from the two.
One time picore 1 one time picore 2.
Klicking on refresh the player changes....any ideas?

[Paul Webster]

Try specifying different "MAC" address and name for each Squeezelite.
The MAC address parameter does not have to be related to the real Network MAC address of the device.
It is given as command line parameter to Squeezelite via -m aa:bb:cc:dd:01:02
LMS uses the claimed MAC to identify the player - for a real Squeezebox this would be the real MAC address and therefore unique.

[magiczambo]

Try specifying different "MAC" address and name for each Squeezelite.
The MAC address parameter does not have to be related to the real Network MAC address of the device.
It is given as command line parameter to Squeezelite via -m aa:bb:cc:dd:01:02
LMS uses the claimed MAC to identify the player - for a real Squeezebox this would be the real MAC address and therefore unique.

Perfect thanks thats it!

[Paul Webster]

Great.
Maybe if you let Steen(?) know he can incorporate the mechanism into the picoplayer menu system.

[magiczambo]

Thats the solution
You can put this lines into the /opt/bootlocal.sh

Code: Select all

/mnt/mmcblk0p2/tce/squeezelite-armv6hf -n piCorePlayer  -o sysdefault:CARD=Set_1 -a 80:4
/mnt/mmcblk0p2/tce/squeezelite-armv6hf -n piCorePlayer2 -o sysdefault:CARD=Set   -a 80:4 -m ab:cd:ef:12:34:01 -z
/mnt/mmcblk0p2/tce/squeezelite-armv6hf -n piCorePlayer3 -o sysdefault:CARD=ALSA  -a 80:4 -m ab:cd:ef:12:34:02 -z

So you start 3 instances with 3 Outputs.
Set and Set_1 are USB Outputs e.g., ALSA is the analog Output. The MACs are virtual.