Lets keep the standard to 4GB.
Hi, Noob question, I have a fresh Pi3, and am writing the PiCroft image to a 32gb sd, can you please confirm that Jessie Lite is part of that image I don’t need to setup my Pi first with the JessLite on the card then partion (gussing here) and put the PiCroft image in the partion. told you I was a noob, I get better when I’ve warmed up, just like Pi3 :D. Mike.
My bad if this is in the wrong place I just thought it was latest Pi post and not enough for a new post. This is my 2nd Pi3 if that makes any reply easier.
Update: After several attempts and fails I have not written the image to the sd card. After a warning that “writing directly to a physical device can corrupt (target device [H;] 'boot”) ." and pressing Write I have “error 23 cyclic redundancy check” at 5% progress, 3 attempts. I did reformat once because the format gave a msg that quick flash had been cancelled even though thats not what I chose.
Update: USB 3 fail USB 2 success.
Hey there!
Yes, the PiCroft image is based on JessieLite, so you don’t need to install that first.
Also, just to confirm, you got it working?
Hi, I did burn the image, as yet I have not booted it. I have bought a USB mic yesterday on TradeMe, (NZ version of eBay), and am just awaiting delivery.
There is mention of CM108 based mic on the github PiCroft page, google returns images of usb soundcards with rca jacks, so I am crossing fingers that the mic I have purchased works. Although rca mics come in some very cool retro models which would be great to have if they worked.
Google search result for CM108 based microphone - images of soundcards no mics.
Thanks for the reply, I’m sure you are all extremely busy.
Those don’t look like RCA jacks; they look like mic in and stereo out, so it’s a usb adapter for standard 3.5 mm stereo jacks.
It’s really just a USB based mic vs a 3.5mm plug mic. Hypothetically, you could get the adapter and plug in a wired mic, but we haven’t tested that.
For example, the one I’ve been using is the cheapest looking one, which is just a USB plug with a mic attached.
It works if you’re speaking right on top of it. I would not expect it to work well at range, though.
My mistake, your right, I will give that a go once I get it up and running, and have a fall back position.
Hey everyone!
Just wanted to let everyone know there is a new image on the original blog post above, so if you haven’t gotten that image, try that if you were having any issues and let us know.
1 Like
OK, so anyone got it talking to Squeeze/PiCore yet?
I prefer to build picroft by myself too. I already have a Pi running Home Assistant and I hope I can add Mycroft into the same Pi without adding another Pi
Great news! quick question will it work on Pi Zero?
That is an excellent question. Can you give it a try and let us know?
I have some secondary school students that want to set up Mycroft using the Pi image. It seems to boot up fine, but they are getting a prompt in the terminal to search for a Mycroft wi-fi hotspot, which nobody seems to be able to find. The are running a Pi2 with a USB wi-fi adapter, though they we are unsure if it is capable of acting as an ad-hoc network. Is there a recommended wi-fi adapter to use?
I’ll have to try this with a Pi2, I only have Pi3s handy at the moment. With a Pi3, the onboard Wifi gets “split” during that initial pairing process. So there is a chance that a USB wifi won’t work. Just to be clear, if you use a laptop or a phone and pull up the list of available Wifi networks, you don’t see a network called “MYCROFT” – correct?
As a work around you can either of two things to get this going:
Plug the unit in using Ethernet.
We just need a network connection, it doesn’t have to be Wifi.
Manually configure the wifi.
It isn’t too difficult if you have the Pi2 plugged in to a keyboard and HDMI monitor:
- Hit Ctrl+C to get to the command line
- Type:
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf - Arrow-key down to the bottom of the file and enter something like this:
network={ ssid="MyNetworkSSID" psk="mypassword" }
(of course, use your own SSID and password 
)
- Hit Ctrl+X to exit and Y,Enter to save your change.
- Type:
sudo reboot now
Let me know if this works for you!
I’ve tried my image on the pi3 and pi zero W, and still have not gotten the wifi to work. It does get an internet connection through ethernet, though, however when it does and I try to register the device, it goes through the process and then after a reboot, it wants to register again. I have tried manually setting up the wifi as @Dan_Andrews said, however it still will not connect.
Also, I’m intrigued by another commenter’s idea of having a single image of Raspian with mycroft built in. I’m going to try to make that happen (if someone already has, please do let me know).
I can, however confirm that Mycroft does work as well on the pi zero w as it does on the pi 3.
Also, I understand that the image is based on Raspian, however unless I’m just not getting all the way through the setup, I haven’t encountered a GUI yet, it’s been all command line. I’m actually aiming for an interface that involves having a touchscreen connected, so Mycroft can show information as well as speak it. I’ve seen some screenshots of Mycroft running in a window on a Linux build, and was inspired by that. Though eventually I intend to make the Mycroft interface the entirety of the GUI shell.
Hey Lucien,
The Picroft image is based on Raspian Lite, so no GUI.
We did have an issue a few weeks ago where you would have to re-register the device after a reboot, but that should be fixed with the newest image file and version.
Also, thanks for the update on the Pi Zero W. It’s something we’ve been wondering about and wanting to test, but everywhere is sold out.
steve.penrod I updated wpa_supplicant.conf and it works, easy as Pi. Thanks very much!
I’m glad it worked for you, @Dan_Andrews!
@Lucien_Storm, I have doubts that even a Pi3 can handle a GUI and running Mycroft at the same time. I fear there just isn’t quite enough computing power there to give you the experience you want. But I’d be happy to be proven wrong!
I have a Pi3 running GUI and Alexa/AVS at the same time, with no performance issues. It’s a very Echo-like experience. Why would Mycroft impose a heavier load?
I should mention that I’m using the Conexant CX0921 mic and audio board to handle wake-word detection, which relieves the mainboard of the need to process all incoming audio except when triggered by the Conexant board. But others have got AVS working satisfactorily on the Pi3 even while running a wakeWordAgent on the main CPU via full Raspbian GUI.
Thank you for the clarification. I had not tried the Lite version before. I’m still going to experiment with a GUI, and see if I can get Mycroft core integrated. Also, I think some of my Wifi issues may have something to do with the login splash page (because it’s a public wifi at my work), however I’m still not seeing the Mycroft network during it’s set up. I haven’t tried the updated image yet. We’ll see if that works any better.