20.07.2015 Views

M16C/62 Group DATASHEET

M16C/62 Group DATASHEET

M16C/62 Group DATASHEET

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix Standard Serial I/O Mode (Flash Memory Version)Mitsubishi microcomputers<strong>M16C</strong> / <strong>62</strong> <strong>Group</strong>SINGLE-CHIP 16-BIT CMOS MICROCOMPUTERID CheckThis command checks the ID code. Execute the boot ID check command as explained here following.(1) Send the “F516” command code in the 1st byte of the transmission.(2) Send addresses A0 to A7, A8 to A15 and A16 to A23 of the 1st byte of the ID code in the 2nd, 3rdand 4th bytes of the transmission respectively.(3) Send the number of data sets of the ID code in the 5th byte.(4) The ID code is sent in the 6th byte onward, starting with the 1st byte of the code.CLK1RxD1(<strong>M16C</strong> receptiondata)TxD1(<strong>M16C</strong> transmitdata)RTS1(BUSY)F516 DF16 FF16 0F16ID size ID1 ID7Figure 1.31.16. Timing for the ID checkID CodeWhen the flash memory is not blank, the ID code sent from the peripheral unit and the ID code writtenin the flash memory are compared to see if they match. If the codes do not match, the command sentfrom the peripheral unit is not accepted. An ID code contains 8 bits of data. Area is, from the 1st byte,addresses 0FFFDF16, 0FFFE316, 0FFFEB16, 0FFFEF16, 0FFFF316, 0FFFF716 and 0FFFFB16. Writea program into the flash memory, which already has the ID code set for these addresses.Address0FFFDC16 to 0FFFDF160FFFE016 to 0FFFE3160FFFE416 to 0FFFE7160FFFE816 to 0FFFEB160FFFEC16 to 0FFFEF160FFFF016 to 0FFFF3160FFFF416 to 0FFFF7160FFFF816 to 0FFFFB160FFFFC16 to 0FFFFF16ID1ID2ID3ID4ID5ID6ID7Undefined instruction vectorOverflow vectorBRK instruction vectorAddress match vectorSingle step vectorWatchdog timer vectorDBC vectorNMI vectorReset vector4 bytesFigure 1.31.17. ID code storage addresses264

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!