Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

The firmware team is responsible for developing control software to drive all the electrical systems in our car. If you have experience or an interest in low-level programming, embedded systems development, or are just curious about how software in cars even works, this is the place for you!

There is no application process and you don’t need to have any experience when you join (many of our members don’t). All it takes to be a member is interest in what we’re doing, attending meetings twice a week, and putting in effort into helping us build the best software we can. Welcome to the team!

Member Responsibilities

  • Gain exposure to firmware and various software skills such as:

    • writing firmware in C to run on microcontrollers or emulated microcontrollers

    • writing software in python and C to create tools for validating firmware

    • writing software in various languages for projects like our telemetry system or driver display

    • write tests for firmware and other software to validate your work

  • Attend twice weekly standups (mandatory)

Required Skills

  • Know the basics of programming

  • That’s pretty much it, you can learn as you go

Communication

 

Firmware Lead: Jarvis Weng

About: 3A CE. Been on the team since September 2019. Worked with in C++, Python, JS, Java, Bash

Ask me about: C/C++, Python, Java, setting up your dev environment, anything you’re stuck on, or if you just want to chat

Hobbies: Anime & Manga

 

Firmware Lead: Mitchell Ostler

About: I’m in 2B CE, and I’ve gained experience in embedded development from several different companies in Ontario.

Ask me about: General programming/embedded system questions, drivers, libraries, setting up dev environments, the meaning of life

Fun Facts: Terribly self taught piano player, big fan of sci-fi and fiction novels

New Members

  • Join our Slack for all team communications. Team Communication

    • Make sure you join the #elec-firmware and #general channels! That is where all our firmware conversations and updates happen

    • [Optional] Add our google calendar for all meeting times Midnight Sun Calendar

    • Follow @uwmidsun on instagram/LinkedIn!

  • Take a look at Intro to Solar Car Electrical Systems if you’re interested, to get an overview of the project we’re working on. Even though you’ll be working on firmware, it’s important to understand the context of the projects you work on. Intro to Solar Car Electrical Systems

Onboarding Process

To become an active member, there is an onboarding process that helps you get up to speed with the technologies we use and learn about what you’ll be working on. This consists of weekly training sessions on Saturdays at the start of every term, and a project associated with each session. The full process is covered below

Part 1 - First Steps

  1. Attend Firmware 101

    1. Every term we hold an introductory training session to tell people what we’re all about. If you’re still not convinced what team you want to be a part of, this is a great place to start. Check Elec-firmware for updates on when this will be taking place, or take a look at previous notes (Firmware 101 - Getting Started ) if you want to get ahead

  2. Background learning

    1. There are several tools/technologies we use to help us run a mean, clean software organization. These are:

      1. Git

      2. Shell Environments (Linux)

      3. C programming

    2. If you don’t have a lot of experience with these, luckily we have Midnight-Sun-specific Shell Environments, Git, and C Programming videos creates by the legendary Arshan Khanifar (a retired firmware lead). Tutorial Videos There is also the page: C Reference for Midnight Sun Firmware Team and lots of resources available online.

Part 2 - Setup and Learning our Systems

  1. Get your environment set up with Module 1 of Software 101. Setup

  2. Attend Firmware 102-104 (held weekly):

    1. Each session has a live component (training session), as well as supplementary notes and homework. They are all contained in Firmware 102 - Embedded Systems . Feel free to read/work ahead if you’re feeling ambitious 🤩

Part 3 - Your first project and beyond!

  1. After you have completed Firmware 104 (and the homework) you are ready for your first task!

    1. Reach out to one of the leads, and they will assign you something on Jira. You are now ready to start contributing!

Once you’ve completed these steps, pat yourself on the back, you’re now a fully onboarded Midnight Sun firmware member!

  • No labels