thanks for the reply Steen!
Unfortunately I'm not yet at the stage where I can see the picoreplayer on my network via my browser.. (I can see other things, e.g. my wireless printer, router set up pages).
My issue is (I think) in getting the Pi B+'s Micro SD card set up properly. 1.18b unzips into a 'mnt' folder with 'mmcblk0p1' inside it and then:
6.0_3163.gz
bootcode.bin
cmdline.txt
config.txt
COPYING.linux
fixup_cd.dat
fixup_x.dat
fixup.dat
LICENCE.broadcom
LICENCE.piCorePlayer
RELEASE.txt
start_cd.elf
start_x.elf
start.elf
zImage3163B.img
inside that. My current basic question is how to configure the Micro SD card - if I just copy the whole mnt structure into it the Pi B+ doesn't boot up (green light on solidly, no output to TV via HDMI). If I just copy the contents of the 'mmcblk0p1' to the 'top level' of the SD card the Pi boots into tiny core, I can see the prompt on my TV and seemingly interact with it via keyboard, but if I type pcicoreplayer at the prompt it says 'not found'.
So when I get to the tinycore prompt as above do I then still have to do the steps in italics below to get things up and running? Is it right that the necessary files are nested 2 folders down in the tar file and I should ignore that structure? Or have I possibly got some other problems?
Thanks for your patience with me/this.
As Picore is running in read only mode om a partition called mmcblk0p1 you need to make another partition where it can have all the configuration files and the extensions and the Squeezelite player.
In order to make such a partition I did this (It was here I had the most difficulties) Each line is the commands I used:
fdisk /dev/mmcblk0
n new
p primary
2 partition number 1-4
6 first cylinder
+20M I made a 20 MB partition for this - you could choose any size you want (up to the CF-card size)
EDIT I Forgot the following two lines in my first description
t change partition Id
83 linux file system
w to write the changes to the card
sudo reboot
Next I formated it to the ext4 format:
mkfs.ext4 /dev/mmcblk0p2
sudo reboot
Then you need to define where Picore will find your extensions, you do that by this command:
tce-setdrive
And then you choose 2= /mnt/mmcblk0p2
Download Squeezelite and put in a writeable place like mnt/mmcblk0p2, you can so that by this command
wget http://squeezelite.googlecode.com/fi...zelite-armv6hf -P /mnt/mmcblk0p2
Then I had some problems that squeezelite would not start - it turned out that I had to allow it to be executed - using this command
chmod 755 /mnt/mmcblk0p2/squeezelite-armv6hf
You need to install Alsa, flac libmad and libvorbis. You do that by using the package manager in Picore called tce. Therefor at command promt write:
tce
s search
a (a in order to search for Alsa) then Enter
select alsa.tcz (at present no 4) enter
q quit
i install
s search
f (f in order to find flac.tcz (present no 9)) Enter
9 enter
q quit
i install
s search
l (l in order to find libmad.tcz (presently no 57)) Enter
57 enter
q quit
i install
s search
l (l in order to find libvorbis.tcz (presently no 88))
88 enter
q quit
i install
sudo reboot
Then in order to automatically to start Squeezelite everytime the Raspberry reboot, you need to add this program to the bootlocal file which is used for this purpose.
As I have been doing this without GUI the only editor present is the vi editor, which also gave me a hard time. But these are the command you have to use:
sudo vi /opt/bootlocal.sh
Then pres i (for insert)
then move the cursor to the first empty line and write:
sudo /mnt/mmcblk0p2/squeezelite-armv6hf -a 80:4
Press "esc" in order to get out of "insert mode"
Then type
:wq and Enter - in order to save and exit vi
These changes is not actually written to the bootlocal.sh file (as it is in read only mode) but insteas the changes is saved another place and during reboot used - so in order to get Picore to save these changes and use them the next time you reboot you have to do a manual backup.
So at command promt type
filetool.sh -b
And now you can reboot and your Raspberry should start Squeezelite. I have tried different Alsa buffer sizes and I think that 80:4 is fine - for me the Squeezelite is in perfect sync with both a Duet and A Logitech radio, if I use to high values like 500:4 or 200:4 the sync is not as perfect. Using 50:4 resulted in some stuttering in the sound
Now you have a dedicated very small Squeezelite player, which boots very rapidly, it doesn't use swap and can survive that you just pull the power plug - so it is almost as an embedded hardware player, like a Duet.
Welcome
FAQ
Downloads
Wiki
