I got a job, how this CoP helped me this year, and advice for next years CoPES group.

Hey everyone! I hope your senior project went well! I just wanted to drop a post about a few things real quick.

First, I uploaded a quick help guide to how to get a job after school. Just some insights into my job hunting process that got me a very competitive job for the area with great pay, benefits, and starting bonus relative to the national norms. It’s on my page, take a look if you’d like.

Second, this CoP is kind of a neat concept. Meeting up several times this term and the workshop I was able to make was awesome! Just the discussions we had about Jacob’s project that he has going on, as well as talking to other students about their issues and the fun they have with microcontrollers was fun! It also motivated me to take what I know and apply it with what I learned in CoPES.

Finally, for next years group, much like anything else out there, you’re going to get back what you put into this. I wasn’t sure what I was going to do in this CoP, but I knew my senior project was going to involve an MC right from the get go, so I chose this CoP. I did learn a few little things that helped, but one of the main parts it helped was actually knowing that I was not the only one with struggles, and that it was normal to need help figuring things out sometimes! It also motivated to look into something I hadn’t before: I’m a big MATLAB fanboy, and it turns out there are a ton of modules out there for using MATLAB to flash quite a few MC’s. The thought of using a simulink module to  program something has a ton of potential! I hope anyone coming into this CoP has as much fun as I did!

Workshop #3


Hello everyone, this workshop is in general about sensor interfaces, with an application example. Code is currently on the Slack channel, but will be uploaded to the git soon.

Meeting 4-17-19

Hey everyone,

In this meeting we will discuss the schedule this term, course requirements, and provide time for discussing projects and fun things.

Schedule this term

  • Two or three workshops (in-depth interrupts, one-wire, application specific projects, etc)
    • We can buy new microcontrollers to play with as well as any sensors, etc. (ESP, STM32)
    • Week 6, Week 8 are good options
  • One or two open-ended meetings
    • Week 8?
  • Relevant Colloquiums: http://eecs.oregonstate.edu/colloquium-series
    • May 6 – Robust Computing Systems: From Today to the N3XT 1,000X
    • May 13 – Integrated circuit design to enable highly miniaturized wireless sensing systems

Course requirements (seniors)

  • Attend 2 meetings and/or workshops
  • Attend 1 additional workshop and/or colloquium
  • Participate in the slack
  • Mentors (need to make this more helpful)


Spencer Moss


My name is Spencer Moss, and I’m studying Electrical Engineering with a minor in Computer Science here at OSU. This year is my fourth and hopefully last as an undergraduate! My primary interests are embedded systems design (hardware & firmware), Computer Architecture, and VLSI. My design project this year is the Open Source Dumbphone, where we are working on designing an Open Source hardware design for a simple feature-phone with a RISC-V microcontroller at the core.

Link to github page:


Link to resume:


Rudy Abou Moussa

Hey! My name is Rudy Abou Moussa, a senior in Electrical Computer Engineering with a minor in Computer Science. I enjoy making cool projects with Arduino and reading on existing projects that as a kid thought would be impossible.  During my junior design my teammates and I built a PC controllable power supply and I learned a lot from it so let me know if you have any questions. During my senior project, I built a magnetic levitation device that uses magnetic fields, PWM signals, and PID feedback loop system to levitate a load.

Mentor: Austin Robinson ( ECE senior student)



Meeting 2/25

On 2/4, we had the first embedded workshop, where we flashed code onto attiny85 microcontrollers (just 8-pin dip in breadboards), demonstrating some basic IO, timing, and power related things. The goal of this is to show that you can get away with quite a bit even with an extremely simple AVR chip. Details are below:

Embedded Systems Workshop 1

There will likely be a part 2 to this in the near future (TBD), though we may move to a different chip.

Options for a second workshop

  • JTAG debugging
  • One wire interfaces
  • Software interrupts & in depth interrupts
  • Watchdog timer
  • Types of pins
  • Application specific things (LCD, SD cards)

Senior design students, remember that the class requirements are about the same as last term:

  • Attend 2 meetings
  • Attend an event
  • Generate some online content (add to the tutorials page, write a post, spend time on Slack).

STM32F7 Setup – Griffin Haas

I wanted to share some of the insight I’ve got over the past couple weeks. Our group has selected the STM32F7 as our microprocessor for our project. We were looking for something reasonably cheap, as close to bare metal as possible (no OS), for audio DSP. The STM version of the ARM cortex m7 we got is the STM32F746 on this discovery board.
It is reasonably priced at $50 and comes with many peripherals and the drivers for them. This board isn’t supported by Platform.io (another good resource) so programming it with all of ST’s HAL (hardware abstraction layer) drivers was a little daunting at first. The moral of the story is I tried ARM’s Keil uVision IDE as well as an eclipse plugin to program and flash the board. ARM’s Keil uVision was fairly easy to setup but their lite version of the IDE only lets you compile and link 32kB projects. This is unfortunate because the professional version costs $1500/year for a license. Eclipse surely works but I had many issues trying to get the environment setup.
The setup we ended up going with is using visualgdb with visual studio.
While it’s not free they have a 30 day free trail and at $50 with the academic discount is much more affordable than ARM-MDK.
This tutorial is very straight forward compared to setting up eclipse.

Event Planning 11/20

Tuesday (11/20) at 6:00 pm is the final Embedded CoP meeting. We will use the time to plan events for next term. Please bring a laptop and some ideas about events that you would like to organize for next term! If you can’t make it at that time, please add your input via Slack by the end of the week (11/23).
For senior design students, this is required to get credit for your professional development assignment.

Senior design students:

As a reminder, this is what you all need to do in order to get credit for your professional development assignment:
  • Attend most meetings (at least 2) – I keep track of this
  • Generate some online content (website and/or Slack posts) – if you directly edit the website, let me know via Slack
  • Correspond with a mentor (academic, industry, or student if applicable) – send me evidence of correspondence via Slack (directly to me, not just in general)
  • Add portfolio to the website – include at minimum a brief bio, skills, and resume
  • Complete member survey – I will send this out after our final meeting via email
  • Participate in an event/project – participate in the event planning on 11/20 or via Slack by 11/23
If you have been participating in meetings this term, you should be on track! If you have any questions, message me or come see me in office hours.

Meeting 10/30

Senior Design Students,

Thanks to all who attended yesterday evening’s meeting! The next one is scheduled for next Wednesday 11/7 at 6:00 pm, location TBD.
For those who couldn’t attend the last meeting, we made some headway on building our knowledge-base on the website and setting up portfolio pages. For those of you interested in this CoP, please do the following:
  • Make a page on the ESCoP website and title it with your name (message me if you don’t have a profile). Please change the parent page to ‘members’
  • Add a little information about yourself, your skills, and a resume/cover letter to the page. This is your portfolio/profile page.
  • Visit our Slack.