Can ECO-C be adapted to own targets? In ECO-C there is the possibility to control alphanumeric displays. Unfortunately these displays cannot be directly connected to the TLX+. Is it yet possible to use these displays? The graphic LC-Display G1216 from Seiko cannot be directly connected to the TLX+. Is there a solution for that? Graphic Library: Which boards are supported? Graphic Library: Which displays are supported? Graphic Library: How to write programs with ECO-C? Graphic Library: How to write programs with WinECO-C? M11: M11 uses the DTR signal to reset the board. What about the reset level? M11: Under Linux M11 runs as root only. How can a normal user run M11? M11: How is the numbering of the serial ports under Linux? What is the TLX+/PIF bus and what can be connected to it? What is the SPI and which components can be used with it? The target does not respond. The Soft-LED blinks irregularly, why?
Useful tips can also be found in our MCT-Mails!
If you have further questions you can contact us directly.
Can ECO-C be adapted to own targets?
Yes, if the target uses a 68k-based processor.
New target for ECO-C (detailed description with example)
In ECO-C there is the possibility to control alphanumeric displays. Unfortunately these displays cannot be directly connected to the TLX+. Is it yet possible to use these displays?
The displays must be connected to the TLX+ via a special interface.
Alphanumeric display at the TLX+
The graphic LC-Display G1216 from Seiko cannot be directly connected to the TLX+. Is there a solution for that?
The TLX+ signals must first be converted into a form suitable for the displays.
Graphic display at the TLX+
Graphic Library: Which boards are supported?
The Graphic Library can be used with 68k and CPU32 single board computers.
Graphic Library: Which displays are supported?
There are drivers for the LC-Displays Toshiba TLX1741, Toshiba TLX1013, Toshiba TLX711 and Seiko G1216 available. In addition output on a terminal is possible, if the terminal supports ANSI. In this case no LCD is needed.
It is relatively easy to program drivers for other LCDs.
New driver for the Graphic Library
Graphic Library: How to write programs with ECO-C?
You must install the package in your ECO-C folder.
Example: You want to use the display TLX1741 with the ZWERG332. Your program is called "main.c" and is located in the ECO-C folder. Then you compile as follws:
ecoc -Wall -target zwerg332 main.c libsrc/sysshare/tlx1741.c -lgraph
The executable program is called "a.out".
Graphic Library: How to write programs with WinECO-C?
You must install the package in your WinECO-C folder.
Link the Graphic Library to your project by adding it in the settings window
The library to use depends on your target. If you have a MEGA332 for example, the appropriate library is "libgraph.a" in the folder "lib/mega332".
In addition the correct low-level functions must be compiled. If you use the display TLX1741, you must add the file "tlx1741.c" in the folder "libsrc/sysshare" to your project:
M11: M11 uses the DTR signal to reset the board. What about the reset level?
M11 tries first *DTR active (= +12V on the V.24 side) to reset the target. If unsuccessful, *DTR inactive (= -12V on the V.24 side) is used. This means that the level is not that important, except for the fact that resetting with +12V is a little faster, because the first attempt succeeds.
M11: Under Linux M11 runs as root only. How can a normal user run M11?
For a "normal" user to be able to use M11, it must be installed suid root. So, in the folder where M11 is installed enter (as root):
chown root. m11; chmod 4755 m11
M11: How is the numbering of the serial ports under Linux?
M11 accesses (even in the Linuxversion) the hardware (i.e. the port device) directly. Specifying the port is the same under DOS and Linux. For example
selects the 2nd serial channel (COM2 under DOS). Under Linux this normally corresponds to /dev/cua1 or /dev/ttyS1, although M11 is not aware of devices like /dev/cua oder /dev/ttS.
What is the TLX+/PIF bus and what can be connected to it?
TLX+ is an extension of TLX, a INTEL-type bus. This bus was created by Toshiba for interfacing Graphic LCDs. You can directly connect LC-Displays to it and, with the extensions to the TLX+ it can be used to simply connect application-specific peripherals (components with INTEL-like bus interface e.g. 8255 are particulary easy to connect).
In the meantime TLX+ is also known as "PIF" (Parallel InterFace) bus and there are various standard modules available.
The TLX+/PIF is a 26-pin connector with
- 8 data bits, 4 address bits
- 4 chip selects
- Reset, interrupt
- GND, VCC and VEE (contrast voltage for LC-Displays)
Pin Signal Signal Pin 1
On boards with 16Bit data bus there are 8 Pins more for data (one could say TLX++), thus making the full data bus width usable for peripherals too.
What is the SPI and which components can be used with it?
SPI means Serial Peripheral Interface. Due to the name one could think that SPI is a "normal" serial Interface. In contrast to the RS232 (+/-12V, asynchronous with start/stop bits, one transmitter, one receiver) the SPI works with TTL-levels, a separate clock line (synchronous) and has a master and an unlimited number of slaves (with only one active slave at a time).
Each slave has its own chip select line and two shift registers as I/O interface. With each clock pulse (from the master) one bit is shifted in and simultaneously one (result)bit shifted out.
For example to connect a 10Bit ADC to the SPI, one transmit, receive, clock and chip select line is required. Nothing changes if a 24Bit ADC is used instead. For each slave more, only one more chip select line is needed.
It is obvious that the wiring is drastically simpler compared to connecting parallel interface components.
SPI (detailed description with manufacturers and components list)
The target does not respond. The Soft-LED blinks irregularly, why?
An error was detected during selftest in the C-Start (srt0.c). The blinking is a kind of Morse code:Code Meaning . . . _ Not enough RAM available (< minimal configuration). . . _ . The program in ROM is incorrectly relocated. . . _ _ Wrong ROM-Checksum (only NICO). . _ . . No RAM available. Checking the lower 32 bytes failed. . _ . _ Peripheral device failure. Scotty08: MFP-access failed.www.mct.net