STM8/ST7
- How can I translate OMF files to HEX or BIN format if I use ROM above the 64KB limit
- RLink for different microcontrollers
- Pinout of ST7 adapter
- Windows crashes after installing Ride7 for ST7
A: There is a new tool for creating HEX files with adresses > 64KB.
If you need your application ROM in HEX format and you are using ROM above the 64KB limit, Raisonance has developed a specific tool, OMF2HEX.exe available here, that translates OMF files to HEX or BIN format, and supports files with code at addresses higher than 0xFFFF.
Here is the command-line usage of the OMF2HEX inputfile command:
<Commands>
HEX|HEXstd : Generates a standard HEX file.
HEXext : Generates a extended HEX file (default). Same as HEXstd but with PAGE information.
BIN : Generates a BINARY for each CODE PAGE used.
HEXfile(fname) : Specifies name of the HEX generated file (only with HEXstd and HEXext options).
RANGE(lowaddr-highaddr): Specifies range of addresses converted (only with HEXstd and HEXext options).
CACHE(size) : Specifies alignment of the HEX record generated (only with HEXstd and HEXext options).
EVENODD : Generates one file for even addresses and one file for odd ones (only on 16-bit files).
NOEVENODD : Do not generate separate files for odd and even addresses.
SINGLE : Generates a single file.
NOSINGLE : Does not generate a single file.
This utility will be included in RKit-STM8 starting with version 2.26 (expected October 2009).
Q: I have an RLink, am I able to use it for different microcontrollers?
A: This depends on your version of RLink. To be sure what your RLink can do either:
- enter "RLinkCapab.exe" in any windows cmd prompt if you installed Ride7
- or download the application from this link
- or look at this page.
Q: I have an RLink, I’m interested specifically in the pinout of the ribbon cable and the ST7 adapter.
A: The pinouts from the protocol-specific ADPs are compliant with each protocol's standard. Therefore, in the case of the 10-pin ICC connector that is used for the ST7 devices, the 10-pin connector of the RLink-ICC ADP is compliant with the ICC standard connector as described in the ST specification:
signal | pin(s)
|
GND | 1,3,5,10
ICCDATA | 2
ICCCLK | 4
RESET | 6
VDD | 7
VPP | 8
CLK | 9 (12MHz from RLink)VDD, GND, ICCDATA, ICCCLK, RESET are required.
Note that all 4 GND pins are required, as they are not all connected on RLink.
VPP is required if your ST7 uses it, but not if your ST7 does not use it. (ST7Lite, ...)
You might also want to place a jumper selection for CLK, to allow the application to use the pin if it is clocked by the internal RC, but keep the option to use it for programmation.
You will find more information on this here: "help"->"PDF"->"ST7-Tools"->"Getting Started ST7", especially in the last two chapters.
Also, you can find the schematics of our demo boards for ST7 (and others) in the Ride7 documentation. These boards provide ICP/ICD connectors correctly connected, and you can use them as examples for your design. Click here:
"help"->"PDF"->"ST7-Tools"->"REva"
"help"->"PDF"->"ST7-Tools"->"REva daughter boards for ST7"
Q: After installing Ride7 for ST7, I experience some Windows crashes (blue screen ...) when undocking my laptop computer from its station. Why is that and how can I prevent it?
A: The driver "parstm" installed by STVD 2.0 or by Ride7 (when checking ST drivers) can create problems.
- If you do not use the ST emulators (EMU3, DVP3, ...) but some other debugging feature (RLink, software simulation, ...) then you do not need these ST drivers.
Use your Windows restore point and then reinstall Ride7 without installing the ST emulation drivers. - If you use the ST emulators (EMU3, DVP3, ...): To undock your laptop either stop the PC or, if you still want to work, stop the driver:
- In the "Device Manager" window, make the hidden devices appear: View hidden device.
- The driver is in "Non-Plug and Play Drivers" list and the name is "STM Parallel Driver"
- Modify the Properties to "Stop"
