Startup Mode of 4_28335 project development record 4_28335 (Serial Port flash burning)

Ipv335 supports multiple startup modes as follows:

//       $Boot_Table:////         GPIO87   GPIO86     GPIO85   GPIO84//          XA15     XA14       XA13     XA12//           PU       PU         PU       PU//        ==========================================//            1        1          1        1    Jump to Flash <- "boot to Flash"//            1        1          1        0    SCI-A boot//            1        1          0        1    SPI-A boot//            1        1          0        0    I2C-A boot//            1        0          1        1    eCAN-A boot//            1        0          1        0    McBSP-A boot//            1        0          0        1    Jump to XINTF x16//            1        0          0        0    Jump to XINTF x32//            0        1          1        1    Jump to OTP//            0        1          1        0    Parallel GPIO I/O boot//            0        1          0        1    Parallel XINTF boot//            0        1          0        0    Jump to SARAM//            0        0          1        1    Branch to check boot mode//            0        0          1        0    Boot to flash, bypass ADC cal//            0        0          0        1    Boot to SARAM, bypass ADC cal//            0        0          0        0    Boot to SCI-A, bypass ADC cal//                                              Boot_Table_End$

For a moment, let's talk a little bit about writing programs:

1. When using the CCS + simulator, we burn the program into RAM to run it quickly, facilitating the development and debugging of the actual project;

Note that the 28335_ram_lnk.cmd file is used.

2. when the project is completed, we usually choose to burn the program into flash to get rid of the dependency on the simulator. When we connect the file with f28335.cmd, the program will be burned into the flash in 28335. At this time, it can be run out of the simulator; start from FLASH; -- that is, the above

XA15     XA14       XA13     XA12

That is, when the value is equal to 1 1 1 1, jump to flash;

Of course, the specific configuration is not only as simple as modifying the CMD file, but sometimes the program runs well in ram, and the problem will occur in Flash;

The most typical function is us_delay. The latency in Ram is precise, but it is different in flash;

3. End the nonsense and go to the topic. How can we burn the program into flash when we want to have no simulator?

We look at the starting method at the top of the SCI-A boot, SCI is a serial communication interface, we can start from the serial port boot 28335;

Before that, there are usually jumper settings on the hardware. We can drop the xa12 down to a low level;

In this way, you can set the startup mode to: 1 1 1 0 -- that is, to start the SCI-A

Step 1:

Download hex2000 and use hex2000 to convert the. Out file compiled by CCS to The. HEX file;

Copy the Hex file compiled by CCS to the hex2000 directory;

Start -- run -- enter in the hex2000 directory:
Hex2000.exe-romwidth 16-memwidth 16-I-o led. HEX led. Out

The following information indicates that the conversion is successful:

The second figure shows a feature option for generating hex files using the built-in CCS, so that you do not need to download hex2000;

Step 2:
The Development Board switches to SCI-A startup mode, that is, 1110;
The xa12 grounding can be, other X13-X15 to stay up the 3.3v unchanged;

Step 3:
C2prog: http://www.codeskin.com/c2prog-download

Step 4:
Connect to the serial port, start c2prog, and reset the board to power on;

Use the serial port debugging tool to test the open serial port: Send ABC and other information that should be returned as is;

After c2prog is configured, click program to burn the data.

Step 5:

Switch to flash to start. observe that the program is running;

> PS: I have encountered the following error prompt:
CRC info added at 0x00330809: 0x9d1c 0 57c0 0x0000

* ** Please reset target in SCI boot-loader mode ***
Connecting with target (autobaud)... failed (no response )!

This may be because the serial port 232 or 485 does not work well, or your mode is not correctly switched;

Startup Mode of 4_28335 project development record 4_28335 (Serial Port flash burning)