There will be weekly meetings, in person. The schedule is TBD and announced on Discord.
We develop our code on linux, and the setup is consistent if you are using linux.
-
The recommended option is dual booting, a tutorial to do so can be found here: How to Dual Boot Any Linux Distribution With Windows – and Get Rid of It When You Need To
-
A member has successfully been able to accomplish this in VMWare, so if thats a route you want to go, it's viable.
-
It is also possible to complete the following steps on Mac, however they are less documented and are more likely to sporadically stop working, but many members are currently doing so, so theres a good support group.
You can run example code in the ARM mbed Simulator. One thing to keep in mind with the simulator is that this is an older version of mbed. While most things are the same, sleep commands and other timing, threading, interrupt related things may be different in syntax when you transition to a real board.
If you will be using the simulator, there is no setup. You can run code here.
If you will be using a board then follow the steps on the TR-mbed readme.
The most you can do without a physical board to test your setup is to build a blinky and see if it compiles. All the rest of our training program, can be done on the online simulator. However, it is highly recommended you use a board if you have one.
For Week 0 you have to turn in a .bin or .elf file from the first build of the code. Build a basic blinky or anything you want and submit the bin or elf file. Make sure to also read our coding style guide. While you probably won't need all of it now, you definitely will once you become and embedded member.
If you have trouble with setup, compilation, or anything else, contact us on Discord @Embedded TA.