static void __init omap3_beagle_config_mcspi3_mux(void)However, it does not work. I am still trying to figure out a solution.
{
// NOTE: Clock pins need to be in input mode
omap_mux_init_signal("etk_d3.mcspi3_clk",
OMAP_PIN_INPUT);
omap_mux_init_signal("etk_d2.mcspi3_cs0",
OMAP_PIN_OUTPUT);
omap_mux_init_signal("etk_d7.mcspi3_cs1",
OMAP_PIN_OUTPUT);
omap_mux_init_signal("etk_d0.mcspi3_simo",
OMAP_PIN_OUTPUT);
omap_mux_init_signal("etk_d1.mcspi3_somi",
OMAP_PIN_INPUT_PULLUP);
}
1) STM32F10x Evaluation Module
STM32F103 Evaluation Module was purchased from Olimex (www.olimex.com). This hardware toolkit is a test-bench to evaluate the features and performance of STM32 ARM Cortex-M3 microprocessors. In order to explore its on-chip peripheral devices, one may need an expansion board to provide connectors and interfaces.
Fig. 1: STM32F10X Evaluation Module
2) JTAG / Parallel Port Dongle
ARM-JTAG Dongle is a hardware toolkit to download user code into STM32 ARM. It helps to program the on-chip flash memory and debug the program as well. Note that all ARM microprocessors provide JTAG interfaces for the debugging. However, PC does not have such sort of ports, and, instead, prefers its parallel port to manage these tasks. Thus, ARM-JTAG Dongle works as an adapter between ARM and PC, exchanging data between JTAG and the parallel port.
Fig. 2: ARM-JTAG Dongle
3) Debugging Server Software
The host PC requires software to communicate with ARM-JTAG Dongle. A software tool named “H-JTAG” is selected as a server to control the programming, downloading, and debugging of ARM codes. It is a professional tool that can work with almost all ARM7, ARM9, ARM10, X-Scale, and Cortex processors. Although it is free, its downloading speed (up to 30kb/s) is even faster than commercial grade products. Also, it works well with many IDEs for ARM. See “H-JTAG” website (www.hjtag.com) and its user manual to setup this software.
There are lots of IDEs available for ARM. (i.e.: ADS from ARM, MDK from Keil, Embedded Workbench from IAR, WinARM from GNU community, etc.) The most popular ones are MDK and Embedded Workbench. Both of them work along well with H-JTAG. MDK offers more customizations as well as debugging features, and is thus selected as the IDE used in this project. The evaluation version of MDK is free, but within a limit of code size (less than 32KB). See Keil’s website for details (www.keil.com/arm/).
During the stage of development, it is suggested to perform SRAM-based debugging. With no needs of erasing or programming flash memory, the debugger (H-JTAG) is able to download the code into on-chip SRAM directly. This could be way faster than flash operations, thus saving time for the debugging. Also, this method protects the flash memory, which can be erased or programmed for limited times.
1) Install “H-JTAG” and “MDK” according to their user manuals.
2)
3)
Fig. 3: H-JTAG has detected the target microprocessor
4) Run “MDK” (Keil uVision3). Create a project by selecting STM32F103xb and its start code.
5) Select the “target” and right click to invoke the dialog of “option for target”.
6) Go to tab “Target” and setup ROM and RAM options as shown in Fig 4.
Fig.4: setup of on-chip ROM / RAM memory space
7) Go to tab “Linker” and select the option “Use Memory Layout from Target Dialog”.
Fig. 5: setup of the linker
8) Go to tab “Debug”. Select “H-JTAG CORTEX-M3” Hardware Debugger.
9) Create a file named “ram.ini”. It includes the following codes. Make it as the initialization file.
FUNC void Setup (void)
{
SP = _RDWORD(0x20000000); // Setup Stack Pointer
PC = _RDWORD(0x20000004); // Setup Program Counter
_WDWORD(0xE000ED08, 0x20000000); // Setup Vector Table Offset Register
}
LOAD nav_arm.axf INCREMENTAL // Download
Setup(); // Setup for Running
g, main
Fig. 6: setup of the debugger
10) Go to tab “Utilities”. Select “H-JTAG CORTEX-M3” as the driver for flash programming.
Fig. 7: setup of the utilities
11) Finish the writing of ARM program and compile it. Then, start the debug session.
Once the code was verified and optimized, it can be downloaded to the flash memory of the microprocessor. In order to release the product, we need to perform Flash-based programming to store the firmware we’ve designed. As non-volatile memory device, flash is ideal to store the code no matter the power supply is available or not.
Fig. 8: setup of on-chip memory space for the flash programming
Fig. 9: setup of output files
Fig. 10: Using H-Flasher to program STM32F10x’s on-chip flash memory
