FSM-55 - Revision history

Unixjazz at 21:03, 22 March 2015

2015-03-22T21:03:46Z

← Older revision		Revision as of 14:03, 22 March 2015
Line 10:		Line 10:
	git clone --branch cortex-m0-support git://git.gniibe.org/chopstx/chopstx.git		git clone --branch cortex-m0-support git://git.gniibe.org/chopstx/chopstx.git

	~~Then, you will have access~~ to ~~code example under~~:		Second step is to install and configure a cross-compiler for the ARM Cortex-m0:

	~~$FSM55_PATH/chopstx/example~~-~~fsm-55~~		After configuring the cross-compiling environment, can compile the firmware by:

	~~Second step is~~ to ~~install and configure a cross-compiler for~~ the ~~ARM Cortex-m0~~:		* Change to directory where we have the code examples:

	~~After configuring the cross~~-~~compiling environment, can compile the firmware by:~~		example-fsm-55/

	* ~~First, creating~~ a symbolic link to the FSM-55 board:		* Create a symbolic link to the FSM-55 board:

	ln -s ../board/board-fsm-55.h board.h		ln -s ../board/board-fsm-55.h board.h

	* ~~Compiling~~ the firmware:		* Compile the firmware:

	make		make

			Now, we are ready to upload the firmware to the board, but first we need to connect the board to the JTAG programmer.

Unixjazz at 20:59, 22 March 2015

2015-03-22T20:59:47Z

← Older revision		Revision as of 13:59, 22 March 2015
Line 8:		Line 8:
	You have to clone the repository with the FSM-55 firmware first:		You have to clone the repository with the FSM-55 firmware first:

	git clone --branch cortex-m0-support git://git.gniibe.org/chopstx/chopstx.git		git clone --branch cortex-m0-support git://git.gniibe.org/chopstx/chopstx.git

	Then, you will have access to code example under:		Then, you will have access to code example under:

	$FSM55_PATH/chopstx/example-fsm-55		$FSM55_PATH/chopstx/example-fsm-55

	Second step is to install and configure a cross-compiler for the ARM Cortex-m0:		Second step is to install and configure a cross-compiler for the ARM Cortex-m0:
Line 18:		Line 18:
	After configuring the cross-compiling environment, can compile the firmware by:		After configuring the cross-compiling environment, can compile the firmware by:

	* First, creating a symbolic link to the FSM-55 board:		* First, creating a symbolic link to the FSM-55 board:

	ln -s ../board/board-fsm-55.h board.h		ln -s ../board/board-fsm-55.h board.h

	* Compiling the firmware:		* Compiling the firmware:

	make		make

Unixjazz at 20:59, 22 March 2015

2015-03-22T20:59:03Z

← Older revision		Revision as of 13:59, 22 March 2015
Line 3:		Line 3:

	Having fun with LED matrices!		Having fun with LED matrices!

			== Getting Started ==

			You have to clone the repository with the FSM-55 firmware first:

			git clone --branch cortex-m0-support git://git.gniibe.org/chopstx/chopstx.git

			Then, you will have access to code example under:

			$FSM55_PATH/chopstx/example-fsm-55

			Second step is to install and configure a cross-compiler for the ARM Cortex-m0:

			After configuring the cross-compiling environment, can compile the firmware by:

			* First, creating a symbolic link to the FSM-55 board:

			ln -s ../board/board-fsm-55.h board.h

			* Compiling the firmware:

			make

Unixjazz at 20:49, 22 March 2015

2015-03-22T20:49:51Z

← Older revision		Revision as of 13:49, 22 March 2015
Line 1:		Line 1:

	== 1. Intro ==		== Intro ==

	Having fun with LED matrices!		Having fun with LED matrices!


	== 2. Connecting your board ==		== Connecting your board ==

	To program the board, we need to use a programmer with support to the SWD protocol. The most common tool is the proprietary device from ST-Electronics, ST-Link v.2. We are not very happy with it, since it has a proprietary firmware. Tentatively, you could try to use a Bus Pirate, which is supposed to support SWD.		To program the board, we need to use a programmer with support to the SWD protocol. The most common tool is the proprietary device from ST-Electronics, ST-Link v.2. We are not very happy with it, since it has a proprietary firmware. Tentatively, you could try to use a Bus Pirate, which is supposed to support SWD.
Line 12:		Line 12:
	So, here is the pinout:		So, here is the pinout:

	== 3. Creating your message ==
			== Creating your message ==

	The fun of this exercise is to create your own message and convert it to a C program.		The fun of this exercise is to create your own message and convert it to a C program.
Line 65:		Line 66:
	};		};

	== 4. Uploading your code ==		== Uploading your code ==


	== 5. Authors ==		== Authors ==

	Gniibe is the author of the FSM-55.		Gniibe is the author of the FSM-55. Unixjazz and Gniibe are the authors of this tutorial.
	Unixjazz and Gniibe are the authors of this tutorial.		It is released under [https://creativecommons.org/licenses/by-sa/2.1/jp/deed.en_US CC-BY-SA-2.1 JP]. Feel free to redistribute it and modify it for your needs.
	It is released under CC-BY-SA-4.~~0 Japan~~. Feel free to redistribute it and modify it for your needs.


	== 5. References ==		== References ==

Unixjazz at 20:48, 22 March 2015

2015-03-22T20:48:24Z

← Older revision		Revision as of 13:48, 22 March 2015
Line 7:		Line 7:
	== 2. Connecting your board ==		== 2. Connecting your board ==

			To program the board, we need to use a programmer with support to the SWD protocol. The most common tool is the proprietary device from ST-Electronics, ST-Link v.2. We are not very happy with it, since it has a proprietary firmware. Tentatively, you could try to use a Bus Pirate, which is supposed to support SWD.

			Usually, you just need two wires to connect your STM32: clock and data lines, but, for the FSM-55 we need the 'reset' line as well.
			So, here is the pinout:

	== 3. Creating your message ==		== 3. Creating your message ==
Line 62:		Line 66:

	== 4. Uploading your code ==		== 4. Uploading your code ==


			== 5. Authors ==

			Gniibe is the author of the FSM-55.
			Unixjazz and Gniibe are the authors of this tutorial.
			It is released under CC-BY-SA-4.0 Japan. Feel free to redistribute it and modify it for your needs.


	== 5. References ==		== 5. References ==

Unixjazz: /* 3. Creating your message */

2015-03-22T20:43:43Z

3. Creating your message

← Older revision		Revision as of 13:43, 22 March 2015
Line 37:		Line 37:
	- - - - - *		- - - - - *

	~~Each character would be presented as~~:		In other to present the message "Happy Hacking!" only the characters we use (including exclamation point and space) are described:

	{ 3, 0 }, /* SPACE */		{ 3, 0 }, /* SPACE */
Line 51:		Line 51:
	{ 2, DATA55V (0x1d, 0x1c, 0x00, 0x00, 0x00) }, /* ! */		{ 2, DATA55V (0x1d, 0x1c, 0x00, 0x00, 0x00) }, /* ! */

	~~To write the expression, "Happy Hacking!", for instance~~:		The message is represented as a string:

	static uint8_t hh[] = {		static uint8_t hh[] = {
Line 60:		Line 60:
	CHAR_SPC, CHAR_SPC, CHAR_SPC,		CHAR_SPC, CHAR_SPC, CHAR_SPC,
	};		};


	== 4. Uploading your code ==		== 4. Uploading your code ==

Unixjazz at 20:39, 22 March 2015

2015-03-22T20:39:53Z

← Older revision		Revision as of 13:39, 22 March 2015
Line 19:		Line 19:

	The user does not need to change the low-level threads (LED and Button), only the Application thread.		The user does not need to change the low-level threads (LED and Button), only the Application thread.
			The data flows from Application -> (some sort of) Video RAM -> LED control

	Messages are encoded in a 5 x 5 grid of LEDs. The 'led' thread loops through each column of 5x5 grid.		Messages are encoded in a 5 x 5 grid of LEDs. The 'led' thread loops through each column of 5x5 grid.
Line 28:		Line 29:
	-----		-----

	Each ~~message~~ is ~~encoded~~ as such:		Each LED is addressed as such:

	-		- 0x00 * 0x00 * 0x00 * 0x00 * 0x00 * 0x00
	-		- - * * * *
	-		- - - * * *
	-		- - - - * *
	-		- - - - - *

			Each character would be presented as:

			{ 3, 0 }, /* SPACE */
			{ 4, DATA55V (0x1f, 0x04, 0x04, 0x1f, 0x00) }, /* H */
			{ 3, DATA55V (0x17, 0x15, 0x0f, 0x00, 0x00) }, /* A */
			{ 4, DATA55V (0x1f, 0x14, 0x14, 0x08, 0x00) }, /* P */
			{ 4, DATA55V (0x19, 0x05, 0x05, 0x1e, 0x00) }, /* Y */
			{ 4, DATA55V (0x0e, 0x11, 0x11, 0x0a, 0x00) }, /* C */
			{ 4, DATA55V (0x1f, 0x04, 0x0c, 0x13, 0x00) }, /* K */
			{ 3, DATA55V (0x11, 0x1f, 0x11, 0x00, 0x00) }, /* I */
			{ 4, DATA55V (0x1f, 0x08, 0x06, 0x1f, 0x00) }, /* N */
			{ 4, DATA55V (0x0e, 0x11, 0x15, 0x07, 0x00) }, /* G */
			{ 2, DATA55V (0x1d, 0x1c, 0x00, 0x00, 0x00) }, /* ! */

			To write the expression, "Happy Hacking!", for instance:

			static uint8_t hh[] = {
			CHAR_H, CHAR_A, CHAR_P, CHAR_P, CHAR_Y,
			CHAR_SPC,
			CHAR_H, CHAR_A, CHAR_C, CHAR_K, CHAR_I, CHAR_N, CHAR_G,
			CHAR_EXC,
			CHAR_SPC, CHAR_SPC, CHAR_SPC,
			};


	== 4. Uploading your code ==		== 4. Uploading your code ==


	== 5. References ==		== 5. References ==

Unixjazz at 20:27, 22 March 2015

2015-03-22T20:27:01Z

← Older revision		Revision as of 13:27, 22 March 2015
Line 1:		Line 1:
	~~'''FSM-55 Tutorial'''~~

	1. Intro		== 1. Intro ==

	~~2. Connecting your board~~		Having fun with LED matrices!


	3. Creating your message		== 2. Connecting your board ==


			== 3. Creating your message ==

	The fun of this exercise is to create your own message and convert it to a C program.		The fun of this exercise is to create your own message and convert it to a C program.

	The program is organized in three threads: LED thread~~, button~~ thread (watchdog), ~~program~~ thread.		The program is organized in three threads:

			* LED thread (dynamic LED control)
			* Button thread (watchdog)
			* Application thread (text screen control)

			The user does not need to change the low-level threads (LED and Button), only the Application thread.

	Messages are encoded in a 5 x 5 grid of LEDs. The 'led' thread loops through each column of 5x5 grid.		Messages are encoded in a 5 x 5 grid of LEDs. The 'led' thread loops through each column of 5x5 grid.
Line 20:		Line 28:
	-----		-----

	4. Uploading your code		Each message is encoded as such:

			-
			-
			-
			-
			-

			== 4. Uploading your code ==

	5. References		== 5. References ==

Unixjazz at 20:21, 22 March 2015

2015-03-22T20:21:25Z

← Older revision		Revision as of 13:21, 22 March 2015
Line 1:		Line 1:
	~~FSF~~-55 Tutorial		'''FSM-55 Tutorial'''

			1. Intro

			2. Connecting your board


			3. Creating your message

			The fun of this exercise is to create your own message and convert it to a C program.

			The program is organized in three threads: LED thread, button thread (watchdog), program thread.

			Messages are encoded in a 5 x 5 grid of LEDs. The 'led' thread loops through each column of 5x5 grid.

			-----
			-----
			-----
			-----
			-----

			4. Uploading your code

			5. References

Unixjazz: Created page with "FSF-55 Tutorial"

2015-03-22T20:03:17Z

Created page with "FSF-55 Tutorial"

New page

FSF-55 Tutorial