Now, let's have a chat about the hardware and software that we're going to use to actually support
this development.
ToolChain, the set up we're going to use in this course is to use our Mac and PC primary as our editing
environment.
A Raspberry Pi primaries build environment and then the Pico has our target environment for running
the code.
So on our laptop, we've got an idea or integrated development environment that we're going to code
in and to run the puckering interface on the Raspberry Pi itself.
We've got the build server, so we've got all the combining tools and it's got the pipes that connect
over to Pico to allow us to automatically deploy code and actually debugging.
And finally, the pico itself, which is just not Target's environment.
Using the Raspberry Pi as a build server has the advantage that we're using the software promoted and
supported by the Raspberry Pi Foundation directly.
So we've got the updates and we've got things that we can actually go and get help out more quickly.
Whereas running the compiler on our Macs directly or on a PC directly, that can be a little bit more
tricky to get working.
The Raspberry Pi also being plugged directly in via these probes into the speaker means that there's
no more fumbling to unplug and plug in the Pico to hold down that boot select button and all of those
things you saw me fumble through into the introduction VIDEO.
All of that we can move away from creating an environment where it's actually really easy just to go
through that iterative cycle.
On the laptop or desktop, we're going to use an integrated development environment in this course,
we will focus on eclipse, but you could also use for your visual studio or other ideas to enable debugging.
We unfortunately need to put on the new GTP application onto the laptop.
I've tried a number of ways to get around this and to avoid this, but this is the only successful way
I can get that debugger to continue to work.
Finally, we need a way of connecting to the Raspberry Pi to be able to run commands to Tree of Mikes
and deployments and to run up debugging servers etc on windows.
You're going to need a separate application for you to be able to use SSI to connect to the Raspberry
Pi.
I suggest using putty and we can talk about that and open more patrons, of course, on the Mac.
Of course, we've actually got a terminal built in, so we don't need any additional software on the
Raspberry Pi.
Will we use?
See, Mike has our project built control software.
We used the Canyou CC compiler and Cross Compile mode with the configuration provided by the Raspberry
Pi foundations.
We also use some JAYANTH utilities to be able to do things like look at what the size of the code and
use of RAM that was built.
The Pico SDK, of course, is important for us from the Raspberry Pi Foundation and the utility that
they've enhanced called open obesity open.
Okta manages the proops that connects the picker, allowing us to deploy and deeper code.
In the next section.
We talk about how to install all of this software and gets it running.