ST7FLITE09Y0B6 STMicroelectronics, ST7FLITE09Y0B6 Datasheet - Page 121

• Manufacturer Part Number: ST7FLITE09Y0B6
• Description: MCU 8BIT 1.5KB FLASH 128KB 16DIP
• Manufacturer: STMicroelectronics
• Series: ST7r

Specifications of ST7FLITE09Y0B6

• Core Processor: ST7
• Core Size: 8-Bit
• Speed: 8MHz
• Connectivity: SPI
• Peripherals: Brown-out Detect/Reset, POR, PWM, WDT
• Number Of I /o: 13
• Program Memory Size: 1.5KB (1.5K x 8)
• Program Memory Type: FLASH
• Eeprom Size: 128 x 8
• Ram Size: 128 x 8
• Voltage - Supply (vcc/vdd): 2.4 V ~ 5.5 V
• Data Converters: A/D 5x8b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 16-DIP (0.300", 7.62mm)
• Processor Series: ST7FLITE0x
• Core: ST7
• Data Bus Width: 8 bit
• Data Ram Size: 128 B
• Interface Type: SPI
• Maximum Clock Frequency: 8 MHz
• Number Of Programmable I/os: 13
• Number Of Timers: 2
• Operating Supply Voltage: 2.4 V to 5.5 V
• Maximum Operating Temperature: + 85 C
• Mounting Style: Through Hole
• Development Tools By Supplier: ST7FLIT0-IND/USB, ST7FLIT2-COS/COM, ST7FLITE-SK/RAIS, ST7MDT10-DVP3, ST7MDT10-EMU3, STX-RLINK
• Minimum Operating Temperature: - 40 C
• On-chip Adc: 8 bit
• For Use With: 497-6250 - BOARD RGB COLOR CTRL STP04CM596497-5858 - EVAL BOARD PLAYBACK ST7FLITE497-5049 - KIT STARTER RAISONANCE ST7FLITE497-5046 - KIT TOOL FOR ST7/UPSD/STR7 MCU
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 497-5632-5

16 KNOWN LIMITATIONS
16.1 Execution of BTJX Instruction
Description
Executing a BTJx instruction jumps to a random
address in the following conditions: the jump goes
to a lower address (jump backward) and the test is
performed on a data located at the address
00FFh.
16.2
previously
Watchdog option
Description
In-Circuit Programming of devices configured with
Hardware Watchdog (WDGSW bit in option byte 1
programmed to 0) requires certain precautions
(see below).
In-Circuit Programming uses ICC mode. In this
mode, the Hardware Watchdog is not automatical-
ly deactivated as one might expect. As a conse-
quence, internal resets are generated every 2 ms
by the watchdog, thus preventing programming.
The device factory configuration is Software
Watchdog so this issue is not seen with devices
that are programmed for the first time. For the
same reason, devices programmed by the user
with the Software Watchdog option are not impact-
ed.
The only devices impacted are those that have
previously been programmed with the Hardware
Watchdog option.
Workaround
Devices configured with Hardware Watchdog
must be programmed using a specific program-
ming mode that ignores the option byte settings. In
this mode, an external clock, normally provided by
the programming tool, has to be used. In ST tools,
this mode is called "ICP OPTIONS DISABLED".
Sockets on ST programming tools (such as
ST7MDT10-EPB) are controlled using "ICP OP-
TIONS DISABLED" mode. Devices can therefore
be reprogrammed by plugging them in the ST Pro-
gramming Board socket, whatever the watchdog
configuration.
When using third-party tools, please refer the
manufacturer's documentation to check how to ac-
cess specific programming modes. If a tool does
not have a mode that ignores the option byte set-
In-Circuit
programmed
Programming
with
of
Hardware
devices
tings, devices programmed with the Hardware
watchdog option cannot be reprogrammed using
this tool.
16.3 In-Circuit Debugging with Hardware
Watchdog
In Circuit Debugging is impacted in the same way
as In Circuit Programming by the activation of the
hardware watchdog in ICC mode. Please refer to
Section
16.4 Recommendations when LVD is enabled
When the LVD is enabled, it is recommended not
to connect a pull-up resistor or capacitor. A 10nF
pull-down capacitor is required to filter noise on
the reset line.
16.5
Interrupt Routine
When an active interrupt request occurs at the
same time as the related flag or interrupt mask is
being cleared, the CC register may be corrupted.
Concurrent interrupt context
The symptom does not occur when the interrupts
are handled normally, i.e. when:
– The interrupt request is cleared (flag reset or in-
– The interrupt request is cleared (flag reset or in-
– The interrupt request is cleared (flag reset or in-
If these conditions are not met, the symptom can
be avoided by implementing the following se-
quence:
Perform SIM and RIM operation before and after
resetting an active interrupt request
SIM
reset flag or interrupt mask
RIM
Ex:
terrupt mask) within its own interrupt routine
terrupt mask) within any interrupt routine
terrupt mask) in any part of the code while this in-
terrupt is disabled
Clearing
16.2.
ST7LITE0xY0, ST7LITESxY0
Active
Interrupts
Outside
121/124