I've been working in IT for a number of years. Here is where I'll share things I'm currently working on. It's a place for notes, for sharing, and for questions. It's also a place for me to attempt to give back to developers who have helped me. I have turned to the internet to learn about most of the tools, methods, and platforms I use in my day to day work. I hope that my articles provide future resources for other developers to rely on, developers learning new things and stretching their skill sets.
This was the build (see Adventures in Nuttx):
Not the qemu part of this article, but the work afterwards, to make sure that the Nuttx simulator works the same as the QEMU running a nuttx shell.
The nuttx simulator does not have to run within a debug application. To run it on it's own....
A couple of years ago I did a little Android application programming using Eclipse as the platform. Today, Android Studio uses a different platform. I explain my process in moving to this new platform in this article.
To launch Android Studio, navigate to the android-studio/bin/ directory in a terminal and execute studio.sh.
Prior to beginning to work with Nuttx with a different configuration setup (board configuration), reset everything running the following from the nuttx/ directory:
QEMU was an interesting possibility. I saw a little demo of it running Nuttx and I actually got to see the Nuttx shell in action
(from terminal window that appears, switch from qemu to nuttx shell with ALT CTRL 3).
Read about this NUTTX Simulator and had a hard time getting it up and running.
I have lots of problems with implementing anything from above website (and I'm not sure why) but in this case, after figuring out that ddd (cli command) was a debugger that I could install on my linux machine, I was successful.
$ sudo apt-get install ddd
This assumes you have the CodeSourcery toolchain (something you need to purchase)
But even still, using the overrides it suggests (CodeSourcery and no buildroot), it still appears to be looking for a buildroot.
DEAD END ON SIMULATOR:
I need to list my dead ends, otherwise, I tend to repeat them over and again.
Nuttx work was the suggestion of a trusted colleague who believed there are earning possibilities associated with Nuttx.
My colleague suggested I purchase:
SAMA6D3 XPLAINED Board
J-Link 9-Pin Cortex-M Adapter
JLINK EDU - JTAG Emulator for Arm Cortex.
I started on the journey. I tried to do the steps in the documentation as I read them. First, download the nuttx tarball.
Since I am familiar with Sourceforge, when I noted the files were there located there, I used that as my starting point.
I started looking a bit at the other link my colleague supplied. However, most of the work in the PX4 project assumes you are working with a Windows computer. So, I decided it would be best for me to see something work on the STM32F4Discovery board, even if it wasn't Nuttx, so began to focus on that.
The following was a good source:
In my situation, on installing to board it just gets hung....
Says to pull the usb cable in and out, but nothing happens.
However, I was able to download the application into the stm32f4discovery in
the following way:
$ openocd -f interface/stlink-v2.cfg -f target/stm32f4x_stlink.cfg