Análisis Encuestas residentes Atacames y Tonsupa

wrCBAWRSHP address data value symbol

wr SD:002554 FF vbfield.a / .b / .c / .d \\MCC\vbf wr SD:002555 FF vbfield.d / .e \\MCC\vbfield+1 wr SD:002556 F8 vbfield.e \\MCC\vbfield+2 wr SD:002557 00 vbfield \\MCC\vbfield+3 wr SD:002558 FF vbfield.f \\MCC\vbfield+4 wr SD:002559 FF vbfield.f / .g \\MCC\vbfield+5

wr SD:00255A FF vbfield.h \\MCC\vbfield+6

wr SD:00255B FF vbfield.h / .i \\MCC\vbfield+7

w SD:00255C FF vbfield.j \\MCC\vbfield+8

w SD:00255D FF vbfield.j \\MCC\vbfield+9

wr SD:00255E E0 vbfield.k / .l \\MCC\vbfield+0A

SD:00255F 00 vbfield \\MCC\vbfield+0B w SD:002560 FF vbfield.m \\MCC\vbfield+0C w SD:002561 FF vbfield.m \\MCC\vbfield+0D SD:002562 00 \\MCC\vbfield+0E SD:002563 00 \\MCC\vbfield+0F w SD:002564 FF vbfield.n = -1 \\MCC\vbfield+10 w SD:002565 FF \\MCC\vbfield+11 w SD:002566 FF \\MCC\vbfield+12

ICE only

FLAG.OFF

Switch-off flag system

The flag system would be switched off. The program activity doesn't influence the flag information. This command is not possible on real-time emulation.

See also

■ FLAG.state

▲ ’FLAG System’ in ’ICE User’s Guide’

ICE only

FLAG.ON

Switch-on flag system

The flag system would be switched on. Every program and data cycle sets the corresponding flag bit. This command is blocked if real-time emulation is running.

See also

■ FLAG.state

▲ ’FLAG System’ in ’ICE User’s Guide’

FIRE / ICE only

FLAG.RESet

Reset

The whole flag memory will be deleted and released (Unmapped).

See also

■ FLAG.state

Format: FLAG.OFF

Format: FLAG.ON

FIRE / ICE only

FLAG.Set

Set

This command is used to manually set flags before starting real-time emulation. Flag setting is needed to prevent read-before-write triggering on code and initialized data areas. See FLAG.SetSec. In EPROM based embedded controller systems the write flags should be set in the whole EPROM area (To detect malfunction set the write breakpoint too and protect against write).

Map

This option forces mapping of flag memory if necessary.

See also

■ FLAG.state

▲ ’FLAG System’ in ’ICE User’s Guide’

ICE only

FLAG.SetSec

Mark sections

If the object files loaded has correct information about initialized data and code areas, the presetting of the write flag should be done by this command instead of FLAG.Set. Presetting of the write flag prevents from read-before-write (RBW) triggering on code or initialized data access.

See also

■ FLAG.state

Format: FLAG.Set <address> | <addressrange> [/<option> …]

<option>: Read Write Map

flag.s 0x0--0x0ffff /w ; set write flags

ICE only

FLAG.state

State

The state of the flag system is shown. The commands FLAG.Init and FLAG.RESet are executable by mouse-clicking.

See also

■ FLAG.Delete _■ FLAG.Init _■ FLAG.List _■ FLAG.ListFunc ■ FLAG.ListModul _■ FLAG.ListVar _■ FLAG.OFF _■ FLAG.ON ■ FLAG.RESet _■ FLAG.Set _■ FLAG.SetSec

▲ ’FLAG System’ in ’ICE User’s Guide’ Format: FLAG.state

E::w.flag

state commands

OFF Init

FLASH

External FLASH memories and on-chip FLASH memories of microcontrollers can be programmed and erased by the FLASH command group.

An up-to date list of all supported FLASHs you will find at the LAUTERBACH home page under: http://www.lauterbach.com/ylist.html. The list is also available under “List of Supported FLASH Devices” (flashlist.pdf).

For further information please refer to “Onchip/NOR FLASH Programming User’s Guide” (norflash.pdf). The FLASH.Create command allows to define the layout of the FLASH memories on the target. After activating the programming option any memory modification command of TRACE32 will issue a FLASH programming sequence for the devices. Parallel programming of multiple FLASH devices is supported. The programming can be done in two different modes:

• TRACE32 software based

• target controlled (an extra FLASH programming routine is used)

The TRACE32 software based programming needs no programming algorithm running on the target and no target RAM, but is slow (typical about 1 to 5 KByte/s). An exception are buffered FLASH chips (like Intel FlashFile devices) which can be programmed at rates of more than 100 KByte/s.

Target controlled FLASH algorithms are called by TRACE32 with appropriate parameters to program a memory. The advantage of this method is the higher programming speed and more flexibility in the implementation of the programming algorithm.

LAUTERBACH provides ready to run binary files for target controlled FLASH programming. These files are available for most common architectures on the TRACE32 software CD under:

~~\demo\<cpu>\flash

The FLASH algorithms are organized by <bus_width>. The name of the FLASH algorithm corresponds to the <family_code>. To get the <family_code> refer to the FLASH.Create command or to the LAUTERBACH home page under http://www.lauterbach.com/ylist.html.

E.g. the algorithm to program a Am29LV640 at a 16 bit bus with an ARM core working in little endian mode can be found under ~~\demo\arm\flash\word\am29lv100.bin

In production environments, it is recommended to use target controlled FLASH programming and to load the FLASH data in binary format (Data.LOAD.Binary) to get the highest possible programming speed.

See also

■ FLASH.AUTO ■ FLASH.BSDLaccess ■ FLASH.CFI ■ FLASH.CHANGETYPE ■ FLASH.CLocK ■ FLASH.Create ■ FLASH.CreateALIAS ■ FLASH.Delete ■ FLASH.Erase ■ FLASH.List ■ FLASH.LOCK ■ FLASH.MultiProgram ■ FLASH.OFFSET ■ FLASH.Program ■ FLASH.ReProgram ■ FLASH.RESet ■ FLASH.state ■ FLASH.TARGET ■ FLASH.TARGET2 ■ FLASH.UNLOCK ■ FLASH.UNSECUREerase

FLASH.AUTO

Auto programming of FLASH

Activates the auto programming mode for the selected FLASH memory unit or address range or for all defined devices.

The auto programming mode can be used: • to patch code in FLASH.

• to set software breakpoints into FLASH.

Format: FLASH.AUTO [<unit> | <address_range> | ALL | off | CANCEL |

/CENSORSHIP]

<unit> Activate the auto programming mode for all sectors of the specified unit. ALL Activate the auto programming mode for all FLASH sectors.

off With parameter “off” or without argument the auto programming mode is terminated. Terminating the auto programming mode lets you program only the modified sectors.

CANCEL Abort without programming pending changes.

CENSORSHIP CPU specific option: Allows you to program the range where the FLASH security bytes are located.

NOTE: The FLASH.AUTO off and FLASH.ReProgram off commands automatically erase the modified sectors before writing them.

• Consequently, do not use FLASH.Erase when using the auto or reprog programming mode.

• If you do, you will lose the advantage of reprogramming only modified sectors, which will result in a loss of performance.

See also

■ FLASH.state

▲ ’Programming Commands’ in ’Onchip/NOR FLASH Programming User’s Guide’