As such, here's the list of functions that will be created for now:ġ️⃣ A transmit_raw_data function that will serve to transmit data to the device whenever needed. Those would be functions that require more algorithmic involvement. Any additional special features/functions like drawing specific characters or supporting larger displays I reserve for step 5 in the series. This is all information provided by the datasheet. The functions would be ones that would enable one to initialize and control all possible device functionality and be able to light up any LED.
NUCLEO F401RE DRIVERS DRIVER
In creating my initial swipe at the driver code I want to list out the basic functions that the driver is going to provide. Note that if the code on the git repo is slightly different then it means that it was modified to enhance the code quality or accommodate any HAL/Rust updates. I figure that rather than presenting a solution right away, showing the problem would help explain why the solution is the way it is.Īll the code presented in this post in addition to instructions for the environment and toolchain setup are available on the apollolabsdev Nucleo-F401RE git repo. So why am I doing this? hopefully to make a point and better explain the proper way of how doing things in Rust looks like. As a matter of fact, the code here will also be less flexible (not platform agnostic) as we'll see. Though due to certain patterns in embedded Rust, like the singleton pattern, it will show that the code is still not going to be optimal. Note that here in what I am going to be doing here, I'm taking sort of the typical approach one would maybe in other languages like C. So this means that right now the goal is to replace repetitive code with functions that can be utilized to drive the MAX7219 instead. Step 2 in bold is where we stand now in the series. Add advanced features to the driver and introduce a new version of the crate.Register the driver in crates.io and publish its documentation.Refactor code in the second step to incorporate embedded-hal traits and create a platform-agnostic driver.This step would also create a driver that isn't platform agnostic. Refactor and optimize the code in the first step by adding functions.Create simple code to configure and test the MAX7219 with a simple application.To reach that goal, as a reminder, here are the steps I had laid out for the series: The goal ultimately was to create a platform agnostic driver for the MAX7219. In this post, I continue the work I started in the previous post where I created a simple SPI application driving an LED dot matrix through the MAX7219 LED Driver IC.
0 kommentar(er)
