FSM-55 (Flying Stone Mini 55) is a small board to play 5x5 LED matrix display. It was named after its LED matrix.
Please say, F-S-M “Go” “Go”, since “Go” is the pronunciation of 5 in Japanese.
Your Computing Freedom with Reproducible Product
Hardware design is available as free hardware design. It is designed with KiCAD. The license is CC-BY 3.0 Unported for its schematic design, and CC-BY-SA 3.0 Unported for its PCB design. (This should be described in its README, I’m going to add this soon.)
When you use the PCB design for yourself, please modify it for your own purpose. Please not include the logo of Flying Stone Technology for your PCB.
Firmware is available as Free Software under GPLv3+.
$ git clone –branch cortex-m0-support git://git.gniibe.org/chopstx/chopstx.git
The main program is under: example-fsm-55 directory.
Ah, yes. I use my own thread library for the firmware and ported it to Cortex-M0.
If you are using Windows on your PC, vendor tool works well with CLI. I got a report GUI version doesn’t work well.
On free Operating system, perhaps, newer OpenOCD would work, but it didn’t work for me (as of 0.8 on Debian).
I use my own tool, which originally written for Gnuk Project (for FST-01).
I needed to modify the tool (stlinkv2.py) so that it can work with Cortex-M0 MCU.
$ git clone –branch stlink-m0-support git://git.gniibe.org/gnuk/gnuk.git
It was originally developed for FST-01. And there is something specific to FST-01 like SPI flash checking. You need to invoke it with -i option (inhibit SPI flash checking) for FSM-55.
$ stlinkv2.py -i ...
Reasons: Free Tools are very important for us!
One of major reasons for this board (to be developed) was shutdown of FreeRouting.Net. Although I (gniibe) didn’t use the service, it’s sad incident. I wanted to notice many people about PCB design by Free (as in freedom) tools and current situation.
- FreeRouting.Net: http://freerouting.net/
Another reason for this board was I (gniibe) found that OpenOCD’s SWD support is getting better, it’s not yet perfect. I wanted to have more opportunities to improve situation around OpenOCD and SWD tool, by myself.
- OpenOCD forthcoming 0.9.0: http://openocd.sourceforge.net/
Products available at Seeed Bazaar
FSM-55 LED Matrix Display Kit (October 2014)
SWD Programmer (ST-Link/V2 clone)(March 2015)
NOTE: I’m not sure if ST-Link/V2 clone works for FSM-55. FSM-55 requires NRST pin connected to the programmer. If clone’s pin of #9 works as NRST, it will be OK. But it seems that the NRST pin and SWIM_RST is different in the original ST-Link/V2.
NOTE: I got ST-Link/V2 clone, but I can’t find the way to use it. We need to figure out how to assert pin 9 of SWIM_RST for FSM-55’s NRST. 2015-05-28
NOTE: The firmware of ST-Link/V2 itself is proprietary software. Ideally, it should be free software, too. But, the situation of hardware development is like this, currently. BusPirate or Versaloon could be used, instead, but those are not that stable enough for SWD, yet.
Movies of FSM-55 prototype
Articles by FSM-55 developer
- Articles for FSM-55 by its developer: http://www.gniibe.org/tag/fsm-55.html
Graham Seaman, May 2001, “Free Hardware Design - Past, Present, Future”: https://web.archive.org/web/20140407174608/http://www.opencollector.org/Whyfree/freedesign.html
Free Software and Free Hardware Designs: https://web.archive.org/web/20140407212334/http://www.opencollector.org/Whyfree/whyfree.html
Open Hardware definition in 1998: https://web.archive.org/web/20140407171518/http://www.opencollector.org/Whyfree/open_hardware.html
Benjamin Mako Hill, June 2010, “Free Software Needs Free Tools”: http://mako.cc/writing/hill-free_tools.html
OSHW (which is not enough for FSM-55 developer)
Open Source Hardware: http://freedomdefined.org/OSHW
- Open Design: http://en.wikipedia.org/wiki/Open_design
- GCC ARM Embedded: https://launchpad.net/gcc-arm-embedded
Help us make it better
Welcome to the new documentation system of Seeed Studio. We have made a lot of progress comparing to the old wiki system and will continue to improve it to make it more user friendly and helpful. The improvement can't be done without your kindly feedback. If you have any suggestions or findings, you are most welcome to submit the amended version as our contributor via Github or give us suggestions in the survey below, it would be more appreciated if you could leave your email so that we can reply to you. Happy Hacking!