This is a blog to talk about the NuttX RTOS with a link to original project!
I was writing before I was trying some stack to write documentation. This stack I want to share with you. I think it works very well! If you have any questions please ask!
Multiple output formats are possible, think about HTML, ePub, and PDF…
We have made a patch to make the Extended ID work in the mcp2515 driver with Nuttx. Its a really strong feature in CANBus. Below are some pictures which show the different setups. We used a Nucleo-F411RE and a Microchip solution with CAN-SPI Modules.
The PINOUT which is used:
PA5 = SCK, PA6=MISO, PA7=MOSI, PA1=INT, PA4=CS and +5V and GND
Did you ever have that feeling where you are using tooling and where you just had an error once too much? Like in Nuttx when you are getting a -19 fault (“No such device”), and when you touch the wires, it works again?
Like always, I then want a solution to this problem. So sniffing the internet and grasping my mind, I am re-inventing an old-school solution! And one that seems forgotten and needs revival if it’s on my watch! And that technique is Wire Wrapping!
So let’s get rid of breadboards! And those shady wires!
And what’s next when you make the discission to use this technique? Not only do you have to buy the patented tool and AWG-30 wire-wrapping wire. But you also need some prototyping board. So let’s make one! And we are using: Pertinax 2.54mm.
This was an epiphany!!! Some more pictures to get you going……. Let me know your experience!
Tomorrow we will post a video about setting up Nuttx for Modbus Master with a Nucleo-F411RE
In the last period, I am trying out the different “bus drivers” in Nuttx. One reason is that I want to understand everything deeper. So secondly, because I am doing great things with a company in Groningen, where I was asked to coach a student. This student is also busy with Nuttx. An RTOS was part of his assignment, and why not use something I think is “the perfect RTOS,” and I also know more about every day. Also, he helps me by asking questions. Such a winning team!
I am also writing in Asciidoctor and use it with Jenkins and Git within Visual Studio Code. An excellent combination if I might say. In the early days, I was a Tex fan and Markup. However, I think this is a refreshing solution.
