7 Steps to Make RS232 ExpressCard Download Flash to 218X

Author: jackdrogba

Step One: Install CCS2.2 and check your RS232 Interface

To ensure that your source code can be compiled to Download Source: xxx.out file.

Step two: Install Serial Programming Algorithm project file: sdf28xx_v3_0_serial more information, please read the included: SDFlash_Serial_RefGuide_v3_0.pdf and Expresscard RS232.pdf files.

Step Three: In the algorithm set up the project file, the corresponding clock frequency, and generates. 1 SDFLASH 1.63 download, serial download support. 2 SDFLASH algorithm libraries

(1) In the CC file to import F2812SerialFlash.pjt

File directory: C: \ CCStudio_v3.1 \ specdig \ sdflash \ mydrivers \ DSP281x_v3_0 \ DSP281x_serial \ build \ F28xxSerialFlash

(2) set up your target board clock frequency of the corresponding

The Flash280x_API_Config.h the corresponding PLL clock, I use the 20M crystal Chun chose: define CPU_RATE 10.000L / / for a 100MHz CPU clock speed (SYSCLKOUT) (3) Save and compile the project file, generate F2812SerialFlash.out file stored in: C: \ CCStudio_v3.1 \ specdig \ sdflash \ mydrivers \ DSP281x_v3_0 \ DSP281x_serial \ bin

Note: Make sure your flash program space defined in paragraph (in the CMD file changes). IF there is no RS232 Inteface,just install a RS232 Expresscard serial port adapter.

Step four: Install SdFlashV1.60 or later

Fifth Step: Edit sdopts.cfg file that is stored in your installation of windows of the System32 directory

(1) Use Notepad to open the way sdopts.cfg.

(2) "# End of sdopts.cfg" before adding the following text:

[EmulatorId = C1]

EmuPortAddr = 0xC1

EmuPortMode = RS232

EmuProductName = SERIAL_FLASH

[EmulatorId = C2]

EmuPortAddr = 0xC2

EmuPortMode = RS232

EmuProductName = SERIAL_FLASH

[EmulatorId = C3]

EmuPortAddr = 0xC3

EmuPortMode = RS232

EmuProductName = SERIAL_FLASH

[EmulatorId = C4]

EmuPortAddr = 0xC4

EmuPortMode = RS232

EmuProductName = SERIAL_FLASH

Step six: Open SDFlash, according to the methods provided by SDFlash_Serial_RefGuide_v3_0.pdf specify a file path algorithm

In the Project settings, if you chose to use the PC emulator of COM1 for the C1, COM2 select the C2

Seventh Step: The DSP-SCI_A and PC-RS232 port/Expresscard RS232 connection. Will be as follows DSP-foot tube set to the corresponding level, and then reset

Reset time: GPIOF4 = 0 GPIOF12 = 0 GPIOF3 = 1 GPIOF2 = 1

Note: GPIOf4 for SCI_A TXD terminal, reset should be restored after the completion of the original DSP is able to carry the signal state

Step seven: Click SdFlash menu Flash items --- "Click Start, you can!!!. Check your RS232 or Expresscard 34 RS232 Serial Port can work normally!

About the Author:

jackdrogba is interested in computer technology..

Article Source: ArticlesBase.com - 7 Steps to Make RS232 ExpressCard Download Flash to 218X

CAN BUS MESSAGE FRAMES - Overload Frame,Interframe Space

An overload frame, shown in Figure 2-5, has the same
format as an active error frame. An overload frame,
however, can only be generated during an interframe
space. In this way, an overload frame can be differentiated
from an error frame (an error frame is sent during
the transmission of a message). The overload frame
consists of two fields: an overload flag followed by an
overload delimiter. The overload flag consists of six
dominant bits followed by overload flags generated by
other nodes (and, as for an active error flag, giving a
maximum of twelve dominant bits). The overload
delimiter consists of eight recessive bits. An overload
frame can be generated by a node as a result of two
conditions:
1. The node detects a dominant bit during the
interframe space, an illegal condition.
Exception: The dominant bit is detected during
the third bit of IFS. In this case, the receivers will
interpret this as a SOF.
2. Due to internal conditions, the node is not yet
able to begin reception of the next message. A
node may generate a maximum of two
sequential overload frames to delay the start of
the next message.

CAN BUS MESSAGE FRAMES - Interframe Space

The interframe space separates a preceding frame (of
any type) from a subsequent data or remote frame.
The interframe space is composed of at least three
recessive bits called the Intermission. This allows
nodes time for internal processing before the start of
the next message frame. After the intermission, the
bus line remains in the recessive state (bus idle) until
the next transmission starts.

http://ww1.microchip.com/downloads/en/DeviceDoc/21801d.pdf

CAN BUS MESSAGE FRAMES - Error Frame

An error frame is generated by any node that detects a
bus error. An error frame, shown in Figure 2-4, consists
of two fields: an error flag field followed by an error
delimiter field. There are two types of error flag fields.
The type of error flag field sent depends upon the error
status of the node that detects and generates the error
flag field.

2.4.1 ACTIVE ERRORS
If an error-active node detects a bus error, the node
interrupts transmission of the current message by
generating an active error flag. The active error flag is
composed of six consecutive dominant bits. This bit
sequence actively violates the bit-stuffing rule. All other
stations recognize the resulting bit-stuffing error and, in
turn, generate error frames themselves, called error
echo flags.

The error flag field, therefore, consists of between six
and twelve consecutive dominant bits (generated by
one or more nodes). The error delimiter field (eight
recessive bits) completes the error frame. Upon
completion of the error frame, bus activity returns to
normal and the interrupted node attempts to resend the
aborted message.

2.4.2 PASSIVE ERRORS
If an error-passive node detects a bus error, the node
transmits an error-passive flag followed by the error
delimiter field. The error-passive flag consists of six
consecutive recessive bits. The error frame for an errorpassive
node consists of 14 recessive bits. From this it
follows that, unless the bus error is detected by an erroractive
node or the transmitting node, the message will
continue transmission because the error-passive flag
does not interfere with the bus.

If the transmitting node generates an error-passive flag,
it will cause other nodes to generate error frames due
to the resulting bit-stuffing violation. After transmission
of an error frame, an error-passive node must wait for
six consecutive recessive bits on the bus before
attempting to rejoin bus communications.
The error delimiter consists of eight recessive bits and
allows the bus nodes to restart bus communications
cleanly after an error has occurred.

http://ww1.microchip.com/downloads/en/DeviceDoc/21801d.pdf

CAN BUS MESSAGE FRAMES - Remote Frame

Normally, data transmission is performed on an
autonomous basis by the data source node (e.g., a
sensor sending out a data frame). It is possible,
however, for a destination node to request data from
the source. To accomplish this, the destination node
sends a remote frame with an identifier that matches
the identifier of the required data frame. The
appropriate data source node will then send a data
frame in response to the remote frame request.
There are two differences between a remote frame
(shown in Figure 2-3) and a data frame. First, the RTR
bit is at the recessive state and, second, there is no
data field. In the event of a data frame and a remote
frame with the same identifier being transmitted at the
same time, the data frame wins arbitration due to the
dominant RTR bit following the identifier. In this way,
the node that transmitted the remote frame receives
the desired data immediately.

http://ww1.microchip.com/downloads/en/DeviceDoc/21801d.pdf