I have found that basic example code from MCU suppliers is often too complex. Vendors want to write one example for their entire product range, so you often end up with a spaghetti of code and linker script that weaves in CMSIS, USB, drivers for fancy peripherals and whatever else. Even if you wanted to strip it down to basics, you would have to deal with multiple file dependencies in a web of directories that make the job harder than it should be.
For new board bring up, once I have shown sign of life using low level JTAG (see this post), the next thing I like is the simplest possible software set-up that I can get working.
Nice theory. Where do I download some code? I was surprised at how much I had to search to find anything useful. So this post has a simple example I made for a new STM32F100C8 board. It should work or at least help for many CortexM0 or M3 MCUs.
In the below diagram, the pieces of code we need to supply for this simple approach are in blue:
There are countless
Powering up a new board design or even skiing off-piste with an eval board without vendor-suppled code? This post shows a way to look for first signs of life without depending on working debug toolchain or working target software.
I use a Segger JTAG probe that I covered in a previous post.
Some recent eval boards like the one for Nordic Micro’s nRF51822 ship with an on-board USB debug connection that has a USB-JTAG decoder chip on board. This board uses the same Segger driver as their JTAG box embedded in the decoder, so the below approach should also work.
Segger JLINK application driver has a series of useful commands for examining directly addresses in memory:
- mem Read memory. Syntax: mem , (hex)
- mem8 Read 8-bit items. Syntax: mem8 , (hex)
- mem16 Read 16-bit items. Syntax: mem16 , (hex)
- mem32 Read 32-bit items. Syntax: mem32 , (hex)
Since many MCUs have a factory-programmed ID register, you can use JTAG to read this value and check for signs of life.
To start with, I target a STM32F100C8. This MCU has a register at 1FFFF7E0 hex containing a 16-bit value with the flash size of the MCU. This is covered in the STM32F100 programming manual on