AT89C5122. Application Note. Preventing Windows XP from Displaying Unknown device Message at Startup

Transcription

1 Preventing Windows XP from Displaying Unknown device Message at Startup 1. Features Applicable only to AT89C5122 products embedding the DRV or DSU bootloaders Prevents Windows XP Operating System from displaying Unknown device message when the AT89C5122 is plugged in the USB connector AT89C5122 Application Note Note: The bootloader embedded in the ROM is identified by a 3-letter code (DSU) marked on the upper right hand side of the package Rev. 1

2 2. Reference Documents 3. Problem Description AT89C5122 s DSU Bootloader AT89C5122 s Errata-Sheet When the AT89C5122 product is plugged in the USB connector, Windows XP may display temporarily the message Unknown Device for some seconds. The root cause of this problem is the excessive time occuring between the presence detection of the USB device by the operating system and the USB enumeration process performed by the firmware. This time is at least 1.2s while the USB standard requests a maximum of 130 ms. By default, at reset, the AT89C5122 activates the pull-up on D+ line of USB interface to configure the device in Full-Speed mode. When the D+ pull-up is enabled, the device is said attached to USB port. This pull-up is sensed by the operating system to detect the presence of a new USB device and its speed mode. The operating system sends an enumeration request on the USB bus and expects a response within a maximum of 130 ms from device. Upon reset, the AT89C5122 enables the D+ pull-up on USB bus and executes the bootloader program from an internal ROM. This bootloader transfers the user program from an internal E2PROM on to a Code RAM (CRAM) memory. Once completed, the bootloader executes a call to the CRAM lowest address and the MCU starts executing the user program. This transfer process takes about 1.2s, during which the D+ pull-up is enabled and the firmware is unable to answer the enumeration request from the host. Hub port power ok MCU reset Pull-up enabled Begin of Enu- -meration process USB System software reads device speed Execution of user code Hub port power-on VBus Debouncing time USB reset VIH D+ D- 130 ms max 1.2s min 2

3 4. Workaround 4.1 Description The attach / detach operation (activation / deactivation of the pull-up on D+ line) can be controlled by firmware. The workaround consists upon downloading the firmware from the internal E2PROM to the CRAM in two steps : a. First step: at reset, a minimum code is transferred by the bootloader into the CRAM and executed. This minimum code implements a USB detach operation which occurs about 24 ms after reset (MCU freq. = 48 MHz/X1) While the device is physically connected to the USB port, the host is unable to sense the presence of the device and does not display any error message anymore. b. Second step: the firmware downloads the rest of the code into the CRAM and executes it. The firmware has to re-attach the device to the USB port and answer to the enumeration request from the host. Hub port power ok Hub port power-on VBus MCU reset Pull-up enabled Minimum code Firmware detach Firmware attach rest of the code Begin of Enu- -meration process USB System software reads device speed USB reset Debouncing time time VIH downloaded by the bootloader downloaded by the firmware D+ D- 24ms max 130 ms max 1.2s min 4.2 Limitation For this workaround to work, the minimum code must be mapped in the lower part of the CRAM. Therefore, this workaround does not work in user codes mapped beyond address 0F00h. For these codes, the minimum code that the bootloader would have to download would be greater than 3840 bytes and it would take more than 130 ms to download. 3

4 5. Mode of Operation 5.1 Activating the Two-Step Download Feature The two-step download feature is implemented in a specific startup.a51 file provided by Atmel. This file must be included in the customer s firmware development project. The two-step feature is disabled by default and can be enabled by setting the pre-processor symbol BOOTSTRAP to 1. The definition of this symbol can be made in startup.a51 file itself or any customer configuration file. If the preprocessor symbol is defined in startup.a51 file, add the following instruction to the startup.a51 file: BOOTSTRAP EQU 1 If the preprocessor symbol may be defined in a customer s configuration file like config.h for instance: - add the following instruction in startup.a51 file: #include "config.h" - add the following instruction in config.h file: #define BOOTSTRAP Configuring the Bootloader to Download the Minimum Code The size of the code downloaded by the bootloader is a parameter configurable by the user. This parameter is located at addresses (07FFEh, 07FFFh) of the internal E2PROM : 07FFEh= MSB(code size) 07FFFh= LSB(code size) The minimum code size to download is given by the value of start_download label included in startup.a51 file. The minimum code size is by default 017Eh if the Atmel s original startup.a51 file has not been changed. However, it is highly recommended that in all cases the user checks that the compiler keeps giving start_download label this default value. If it is not the case, the user must retain this new value. The code size parameter is disabled by default and must be enabled by setting size bit in the SIB byte (SIB.3). SIB is located at address 07FFDh : SIB = XXXX 1XXX b The other bits of the SIB byte allows to enable or disable some other paramaters. Refer to the bootloader datasheet for further information. The SIB and code size bytes are part of the firmware and are all programmed at the same time. 4

5 6. Programming the Part to Support the Two Step Download 6.1 Minimum Code Size Before starting the programming procedure, it is necessary to get the minimum code size. This information is available in the mapping file created during the compilation process of the user code and given by the value of start_download label defined in startup.a51 file. For instance, for developpers using Keil s C51 compiler, open file with extension M51 and search for start_download label. TYPE BASE LENGTH RELOCATION SEGMENT NAME * * * * * * * D A T A M E M O R Y * * * * * * * REG 0000H 0008H ABSOLUTE "REG BANK 0" DATA 0008H 0009H UNIT _DATA_GROUP_ DATA 0011H 0004H UNIT?DT?TIMER_SOFT 0015H 000BH *** GAP *** BIT 0020H H.3 UNIT?BI?SCIB_API BIT 0020H H.3 UNIT?BI?USB_CCID BIT 0020H H.3 UNIT _BIT_GROUP_ BIT 0021H H.2 UNIT?BI?USB_TASK 0021H H.5 *** GAP *** IDATA 0022H 0001H UNIT?STACK * * * * * * * X D A T A M E M O R Y * * * * * * * XDATA 0000H 011DH UNIT?XD?USB_CCID XDATA 011DH 004FH UNIT _XDATA_GROUP_ XDATA 016CH 0021H UNIT?XD?SCIB_API XDATA 018DH 0002H UNIT?XD?TIMER_SOFT XDATA 018FH 0001H UNIT?XD?SCIB_TASK XDATA 0190H 0001H UNIT?XD?USB_TASK * * * * * * * C O D E M E M O R Y * * * * * * * CODE 0000H 0003H ABSOLUTE 0003H 0008H *** GAP *** CODE 000BH 0003H ABSOLUTE 000EH 0005H *** GAP *** CODE 0013H 0003H ABSOLUTE 0016H 003DH *** GAP *** CODE 0053H 0003H ABSOLUTE 0056H 0015H *** GAP *** CODE 006BH 0003H ABSOLUTE 006EH 000EH *** GAP *** CODE 007CH 0102H ABSOLUTE <--- MINIMUM CODE MAPPED HERE CODE 017EH 0508H UNIT?C?LIB_CODE <--- BEGIN OF CODE TO DOWNLOAD C:017EH SYMBOL START_DOWNLOAD <--- MINIMUM CODE VALUE... 5

6 6.2 FLIP and BatchISP Versions FLIP and BatchISP are usefull tools to program the device. They are supplied in a common software package and can be downloaded from the Atmel s web site : If bootloader is and if interface used is Use and select if device used is FLIP s GUI displays DRV USB port Serial Port - FLIP 2.X.X - BatchISP or later - FLIP FLIP or later - BatchISP or later AT8XC5122 AT8XC5122 AT89C5122 AT85C5122 AT89C5122 AT85C5122 Bootloader Ver. = Device Boot IDs = 8904 Bootloader Ver. = Device Boot IDs = 8504 Bootloader Ver. = Device Boot IDs = 8904 Bootloader Ver. = Device Boot IDs = 8504 DSU USB port Serial Port - FLIP 2.X.X - BatchISP or later AT8XC FLIP FLIP or later AT8XC BatchISP or later AT89C5122 AT85C5122 AT89C5122 AT85C5122 Bootloader Ver. = Device Boot IDs = 8904 Bootloader Ver. = Device Boot IDs = 8504 Bootloader Ver. = Device Boot IDs = 8904 Bootloader Ver. = Device Boot IDs = 8504 When FLIP downlaods the user.hex file, it calculates the user code size and writes it by default at locations 07FFEh and 07FFFh of the buffer. This feature is not compatible with the two steps download one and the user will need to manually replace the user code size by the minimum code size in the FLIP s buffer so that the bootloader transfers only the code needed to complete the first step. The complete procedure is explained in the following pages. 6

7 6.3 USB Interface FLIP Run FLIP, select AT8XC5122 device and click on OK button Select device Click on OK button 7

8 2. Select communication interface, USB intererface and open USB port Select communication interface Select USB interface Open USB port 8

9 3. Check Bootloader Version and Device Boot IDs Bootloader Ver = for DRV Bootloader Ver = for DSU The two step download feature is only applicable to DRV or DSU bootloaders Device Boot Ids = 8904 for AT89C5122 Device Boot Ids = 8504 for AT85C5122 The two step download feature is only applicable to AT89C5122 devices Check Bootloader Version Check Device Boot Ids 9

10 4. Load the firmware s hex file in FLIP s buffer 10

11 5. Select Buffer Options and select Whole Buffer option in Address programming Range section This option forces FLIP to program the device with the contents of the whole buffer. If this option is not selected, the device is programmed with only the part of buffer containing the user code. Select buffer options Select Whole Buffer option 11

12 6. Edit FLIP s buffer and write minimum code size at locations (07FFEh,07FFh). The minimum code length is given by the value of start_downlaod label implemented in startup.a51 file after firmware compilation. (07FFEh)=MSB(minimum code length) (07FFFh)=LSB(minimum code length) Write LSB(Minimum Code Size) Write MSB(Minimum Code Size) Then click on OK button 12

13 7. Select options Erase, Blank Check, Program and Verify on FLIP s GUI and click on RUN button By default, FLIP clear the SIB byte at location 07FFDh just before programming the device. At this stage, the internal E2P contains the following bytes : (07FFDh)=SIB byte=00h (07FFEh)=MSB(minimum code size) (07FFFh)=LSB(minimum code size) Select all options Then click on RUN button 13

14 8. Select size bit option on FLIP s GUI and click on SET ALL button The size bit of SIB byte has been set at location 07FFDh of the internal E2PROM. Select Size Bit option Then click on Set All button 14

15 9. Edit buffer and clear buffer The next two steps are optional if steps from 1 to 8 were correctly done. The aim here is to check that the device is correctly programmed. It is advised to perform them at least at the first run. Edit buffer Then clear buffer 15

16 10. Read device from addresses 0h to 07FFh Optional step. See comments on the previous step. Select Device Read option Specify address range from 0000h to 7FFFh Start read device by clicking on Read Button 16

17 11. Check if E2P locations from 07FFDh to 07FFFh contains the expected values. The FLIP s buffer must contain the following bytes : (07FFDh)=SIB byte. Refer to datasheet bootloader to determine the appropriate value versus the options selected on FLIP s GUI. (07FFEh)=MSB(minimum code length) (07FFFh)=LSB(minimum code length) If this is not the case the programming procedure must be re-started from step 4. Programmed SIB byte Programmed LSB(Minimum Code Size) Programmed MSB(Minimum Code Size) 17

18 12. Click on Start Application button to run the firmware At this stage, the device is programmed and ready to be used in the application. However, the user can click on start application to verify it. Click on Start application button to run the firmware 18

19 6.3.2 FLIP Run FLIP, select AT8XC5122 device and click on OK button Select device Click on OK button 2. Select communication interface, USB interface and open USB port Select communication interface Select USB interface Open USB port 19

20 3. Check Bootloader Version and Device Boot IDs Bootloader Ver = for DRV Bootloader Ver = for DSU The two step download feature is only applicable to DRV or DSU bootloaders Device Boot Ids = 8904 for AT89C5122 Device Boot Ids = 8504 for AT85C5122 The two step download feature is only applicable to AT89C5122 devices Check Bootloader Version Check Device Boot Ids 20

21 4. Load the firmware s hex file in FLIP s buffer 21

22 5. Edit FLIP s buffer and write minimum code size at locations (07FFEh,07FFh). (07FFEh)=MSB(minimum code length) (07FFFh)=LSB(minimum code length) Location 07FFDh (SIB byte) is initialized by default at 08h by FLIP when it downloads the hex file in buffer. This value of SIB selects the size bit by default. Write LSB(Minimum Code Size) Write MSB(Minimum Code Size) SIB set to 08h by default Then click on OK button 22

23 6. Select options Erase, Blank Check, Program and Verify on FLIP s GUI and click on RUN button Once the device is programmed, the internal E2P contains the following bytes : (07FFDh)=SIB byte=08h (07FFEh)=MSB(minimum code size) (07FFFh)=LSB(minimum code size) Once the device is programmed the GUI is updated with the SIB byte and the minimum code size values of device : The Size Bit option is set by default DO NOT CHANGE IT Select all options Minimum code size Then click on RUN button 23

24 7. Click on Start Application button to run the firmware At this stage, the device is ready to be used in application. However, the user can click on start application to verify it. Click on Start application button to run the firmware BatchISP or Later Getting Started It is necessary to install FLIP or a later release to get an appropriate version of BatchISP. Get the following files and install them in the directory where card-reader.hex file is. cardreader.hex is the result of the compilation of the complete user program sources. These files have been specifically developped to support the implementation of the two step download feature and are not part of FLIP s software package realease. progtsdusb.bat progtsdusb.txt progtsdcmd.txt Run progtsdusb.bat. This executable file calls for progtsdusb.txt and progtsdcmd.txt files. The progtsdusb.bat can be called from Windows Operating System or from KEIL project. In KEIL s project insert the name of executable file progtsdusb.bat in after make section from menu : project / options for target / output 24

25 Check this box Insert name of executable file : progtsdusb.bat Source of progtsdusb.bat OFF ECHO ******************************************* ECHO * TWO STEP DOWNLOAD PROGRAMMING PROCEDURE * ECHO * FOR USB INTERFACE * ECHO ******************************************* 25

26 ECHO * Version : 1.0 * ECHO * Date : 10 DEC 2004 * ECHO ******************************************* ECHO * Product : AT8xC5122 * ECHO * Bootloader : DSU - V1.2.1 * ECHO ******************************************* ECHO. PATH=C:\windows;C:\windows\command;"C:\Program Files\ATMEL\FLIP 2.4.2\bin" <----- Check if the environment path is compliant with the system where this file is executed ECHO. ECHO!!! Check that bootloader is running in ISP mode!!! ECHO. REM PAUSE REM CLS batchisp -cmdfile progtsdusb.txt ECHO. ECHO ****************************** ECHO * PART PROGRAMMING COMPLETED * ECHO ****************************** REM PAUSE :END Source of progtsdusb.txt : -device AT8XC5122 -hardware USB -operation INCLUDE "progtsdcmd.txt" Source of progtsdcmd.txt : # # This file contains the procedure # to program the device by batchisp tool # to support the two step download feature #

27 ONFAIL IGNORE ECHO "!!! Check that Bootloader Version is equal to or 1.2.1!!!" WAIT 1 ECHO "Reading device Boots Ids..." RBOOTID1 RBOOTID2 ECHO "!!! Check that Device Boots Ids are equal to 8904 => AT89C5122!!!" ADDRANGE 0x0000 0x7FFF FILLBUFFER 0x00 LOADBUFFER "card-reader.hex" ECHO "" ECHO "Setting Size Bit in SIB at address 0x7FFD..." #Refer to bootloader datasheet for further information ADDRANGE 0x7FFD 0x7FFD FILLBUFFER 0x08 ECHO "" ECHO "Writing MSB of minimum code size at address 0x7FFE..." #This value is given by value of start_download label of startup.a51 file ADDRANGE 0x7FFE 0x7FFE FILLBUFFER 0x01 <----- check if this value matches the MSB of start_download label value. This value must be extracted from memory mapping file generated by the compilation process of the user program. The start_download label is defined in the startup.a51 file. ECHO "" ECHO "Writing LSB of minimum code size at address 0x7FFF..." #This value is given by value of start_download label of startup.a51 file ADDRANGE 0x7FFF 0x7FFF FILLBUFFER 0x7E <----- check if this value matches the LSB of start_download label value. This value must be extracted from memory mapping file generated by the compilation process of the user program. The start_download label is defined in the startup.a51 file. 27

28 ECHO "" ECHO "Programming the device..." ADDRANGE 0x0000 0x7FFF ERASE F BLANKCHECK PROGRAM VERIFY ECHO "" ECHO "Activating code protection mode..." #Refer to bootloader datasheet for further information ADDRANGE 0x7FFD 0x7FFD FILLBUFFER 0x28 Change it if not appropriate to your application PROGRAM_RANGE <----- This value enables to active the code protection mode. #START NORESET 0 <----- The start application instruction is not activated. Remove the # sign to re-activate the start application during development or debugging sessions Result of execution ******************************************* * TWO STEP DOWNLOAD PROGRAMMING PROCEDURE * * FOR USB INTERFACE * ******************************************* * Version : 1.0 * * Date : 10 DEC 2004 * ******************************************* * Product : AT8xC5122 * * Bootloader : DSU - V1.2.1 * *******************************************!!! Check that bootloader is running in ISP mode!!! Running batchisp on Fri Dec 10 15:52:

29 AT8XC USB - USB/DFU Device selection... PASS Hardware selection... PASS Opening port... PASS Reading Bootloader version... PASS1.2.1!!! Check that Bootloader Version is equal to or 1.2.1!!! Waiting 1sec... PASS Reading device Boots Ids... Reading Boot ID1... PASS0x89 Reading Boot ID2... PASS0x04!!! Check that Device Boots Ids are equal to 8904 => AT89C5122!!! Setting Address Range... PASS0x000000x07FFF Filling buffer... PASS0x000000x07FFF0x00 Parsing HEX file... PASScard-reader.hex Setting Size Bit in SIB at address 0x7FFD... Setting Address Range... PASS0x07FFD0x07FFD Filling buffer... PASS0x07FFD0x07FFD0x08 Writing MSB of minimum code size at address 0x7FFE... Setting Address Range... PASS0x07FFE0x07FFE Filling buffer... PASS0x07FFE0x07FFE0x01 Writing LSB of minimum code size at address 0x7FFF... Setting Address Range... PASS0x07FFF0x07FFF Filling buffer... PASS0x07FFF0x07FFF0x7E Programming the device... Setting Address Range... PASS0x000000x07FFF Erasing... PASS Blank checking... PASS0x000000x07FFF Programming memory... PASS0x000000x07FFF 29

30 Verifying memory... PASS0x000000x07FFF Activating code protection mode... Setting Address Range... PASS0x07FFD0x07FFD Filling buffer... PASS0x07FFD0x07FFD0x28 Programming memory... PASS0x07FFD0x07FFD Starting Application... PASSNORESET0x00000 Summary: Total 25 Passed 25 Failed 0 ****************************** * PART PROGRAMMING COMPLETED * ****************************** 30

31 6.4 SERIAL Interface FLIP Run FLIP, select AT8XC5122 device and click on OK button Select device Click on device list Select AT8XC5122 device Click on OK button 2. Select communication interface, RS232 interface, COM port, baud rate and click on Connect button Bootloaders DRV and DSU supports only baud rate 31

32 Select communication interface Select RS232 interface Select COM port Select baud Click on Connect button 3. Check Bootloader Version and Device Boot IDs Bootloader Ver = for DRV Bootloader Ver = for DSU The two steps download feature is only applicable to DRV or DSU bootloaders Device Boot Ids = 8904 for AT89C5122 Device Boot Ids = 8504 for AT85C5122 The two steps download feature is only applicable to AT89C5122 devices 32

33 Check Bootloader Version Check Device Boot Ids 4. Load the firmware s hex file in FLIP s buffer 33

34 5. Select Buffer Options and select Whole Buffer option in Address programming Range section This option forces FLIP to program the device with the contents of the whole buffer. If this option is not selected, the device is programmed with only the part of buffer containing the user code. Select buffer options Select Whole Buffer option 34

35 6. Edit FLIP s buffer, write SIB byte at location (07FFDh) and write minimum code size at locations (07FFEh,07FFh). - SIB byte : refer to datasheet bootloader to determine the appropriate value versus the options choosen. The size bit must be set to 1. - The minimum code size is given by the value of start_downlaod label implemented in startup.a51 file after firmware compilation. (07FFEh)=MSB(minimum code length) (07FFFh)=LSB(minimum code length) Write LSB(Minimum Code Size) Write MSB(Minimum Code Size) Write SIB byte Then click on OK button 35

36 7. Select options Erase, Blank Check, Program and Verify on FLIP s GUI and click on RUN button Select all options Then click on RUN button 36

37 8. Edit buffer and clear buffer The next two steps are optionnal if steps from 1 to 8 were correctly done. The aim here is to check that the device is correctly programmed. It is advised to perform them at least at the first run. Edit buffer Then clear buffer 37

38 9. Read device from addresses 0h to 07FFh Optional step. See comments on the previous step. Select Device Read option Specify address range from 0000h to 7FFFh Start read device by clicking on Read Button 38

39 10. Check if E2P locations from 07FFDh to 07FFFh contains the expected values. The FLIP s buffer must contain the following bytes : (07FFDh)=SIB byte. If only size bit option has been selected, SIB byte should be equal to 08h (07FFEh)=MSB(minimum code length) (07FFFh)=LSB(minimum code length) If this is not the case, the programming procedure must be re-started from step 4. Programmed SIB byte Programmed LSB(Minimum Code Size) Programmed MSB(Minimum Code Size) 39

40 11. Click on Start Application button to run the firmware At this stage, the device is programmed and ready to be used in the application. The user can click on start application to verify it. Click on Start application button to run the firmware 40

41 6.4.2 FLIP Run FLIP, select AT8XC5122 device and click on OK button Select device Click on OK button 2. Select communication interface, RS232 interface, COM port, baud rate and click on Connect button Bootloaders DRV and DSU supports only baud rate Select communication interface Select RS232 interface Select COM port Only baud rate option is supported Click on Connect button 41

42 3. Check Bootloader Version and Device Boot IDs Bootloader Ver = for DRV Bootloader Ver = for DSU The two step download feature is only applicable to DRV or DSU bootloaders Device Boot Ids = 8904 for AT89C5122 Device Boot Ids = 8504 for AT85C5122 The two step download feature is only applicable to AT89C5122 devices Check Bootloader Version Check Device Boot Ids 42

43 4. Load the firmware s hex file in FLIP s buffer 43

44 5. Edit FLIP s buffer and write minimum code size at locations (07FFEh,07FFh). (07FFEh)=MSB(minimum code length) (07FFFh)=LSB(minimum code length) Location 07FFDh (SIB byte) is initialized by default at 08h by FLIP when it downloads the hex file in buffer. This value of SIB selects the size bit by default. 6. Select options Erase, Blank Check, Program and Verify on FLIP s GUI and click on RUN button Once the device is programmed, the internal E2P contains the following bytes : (07FFDh)=08h : SIB byte (07FFEh)=MSB(minimum code size) (07FFFh)=LSB(minimum code size) Write LSB(Minimum Code Size) Write MSB(Minimum Code Size) SIB set to 08h by default Then click on OK button 44

45 Once the device is programmed the GUI is updated with the SIB byte and the minimum code size values of device : The Size Bit option is set by default DO NOT CHANGE IT Select all options Minimum code size Then click on RUN button 7. Click on Start Application button to run the firmware At this stage, the device is ready to be used in application. However, the user can click on start application to verify it. Click on Start application button to run the firmware 45

46 6.4.3 BatchISP or Later Getting Started It is necessary to FLIP or a later release to get an appropriate version of BatchISP. Get the following files and install them in the directory where card-reader.hex file is. cardreader.hex is the result of the compilation of the complete user program sources. These files have been specifically developped to support the implementation of the two step download feature and are not part of FLIP s software package realease. progtsduart.bat progtsduart.txt progtsdcmd.txt Run progtsduart.bat. This executable file calls for progtsduart.txt and progtsdcmd.txt files. The progtsduart.bat can be called from Windows Operating System or from KEIL project. In KEIL s project insert the name of executable file progtsduart.bat in after make section from menu : project / options for target / output 46

47 Check this box Insert name of executable file : progtsduart.bat 47

48 Source of progtsdusb.bat OFF ECHO ******************************************* ECHO * TWO STEP DOWNLOAD PROGRAMMING PROCEDURE * ECHO * FOR UART INTERFACE * ECHO ******************************************* ECHO * Version : 1.0 * ECHO * Date : 10 DEC 2004 * ECHO ******************************************* ECHO * Product : AT8xC5122 * ECHO * Bootloader : DSU - V1.2.1 * ECHO ******************************************* ECHO. PATH=C:\windows;C:\windows\command;"C:\Program Files\ATMEL\FLIP 2.4.2\bin" <----- Check if the environment path is compliant with the system where this file is executed ECHO. ECHO!!! Check that bootloader is running in ISP mode!!! ECHO. REM PAUSE REM CLS batchisp -cmdfile progtsduart.txt ECHO. ECHO ****************************** ECHO * PART PROGRAMMING COMPLETED * ECHO ****************************** REM PAUSE :END Source of progtsdusb.txt : #---- Setup of the hardware device AT8XC5122 -hardware RS232 -port COM1 -baudrate

49 -operation INCLUDE "progtsdcmd.txt" Source of progtsdcmd.txt : # # This file contains the procedure # to program the device by batchisp tool # to support the two step download feature # ONFAIL IGNORE ECHO "!!! Check that Bootloader Version is equal to or 1.2.1!!!" WAIT 1 ECHO "Reading device Boots Ids..." RBOOTID1 RBOOTID2 ECHO "!!! Check that Device Boots Ids are equal to 8904 => AT89C5122!!!" ADDRANGE 0x0000 0x7FFF FILLBUFFER 0x00 LOADBUFFER "card-reader.hex" ECHO "" ECHO "Setting Size Bit in SIB at address 0x7FFD..." #Refer to bootloader datasheet for further information ADDRANGE 0x7FFD 0x7FFD FILLBUFFER 0x08 ECHO "" ECHO "Writing MSB of minimum code size at address 0x7FFE..." #This value is given by value of start_download label of startup.a51 file ADDRANGE 0x7FFE 0x7FFE FILLBUFFER 0x01 <----- check if this value matches the MSB of start_download label value. This value must be extracted from memory mapping file generated by the compilation process of the user program. The start_download label is defined in the startup.a51 file. 49

50 ECHO "" ECHO "Writing LSB of minimum code size at address 0x7FFF..." #This value is given by value of start_download label of startup.a51 file ADDRANGE 0x7FFF 0x7FFF FILLBUFFER 0x7E <----- check if this value matches the LSB of start_download label value. This value must be extracted from memory mapping file generated by the compilation process of the user program. The start_download label is defined in the startup.a51 file. ECHO "" ECHO "Programming the device..." ADDRANGE 0x0000 0x7FFF ERASE F BLANKCHECK PROGRAM VERIFY ECHO "" ECHO "Activating code protection mode..." #Refer to bootloader datasheet for further information ADDRANGE 0x7FFD 0x7FFD FILLBUFFER 0x28 Change it if not appropriate to your application PROGRAM_RANGE <----- This value enables to active the code protection mode. #START NORESET 0 <----- The start application instruction is not activated. Remove the # sign to re-activate the start application during development or debugging sessions Result of execution ******************************************* * TWO STEP DOWNLOAD PROGRAMMING PROCEDURE * * FOR UART INTERFACE * ******************************************* * Version : 1.0 * * Date : 10 DEC 2004 * 50

51 ******************************************* * Product : AT8xC5122 * * Bootloader : DSU - V1.2.1 * *******************************************!!! Check that bootloader is running in ISP mode!!! Running batchisp on Fri Dec 10 16:01: AT8XC RS232 - COM Device selection... PASS Hardware selection... PASS Opening port... PASS Synchronizing target... PASS Reading Bootloader version... PASS1.2.1!!! Check that Bootloader Version is equal to or 1.2.1!!! Waiting 1sec... PASS Reading device Boots Ids... Reading Boot ID1... PASS0x89 Reading Boot ID2... PASS0x04!!! Check that Device Boots Ids are equal to 8904 => AT89C5122!!! Setting Address Range... PASS0x000000x07FFF Filling buffer... PASS0x000000x07FFF0x00 Parsing HEX file... PASScard-reader.hex Setting Size Bit in SIB at address 0x7FFD... Setting Address Range... PASS0x07FFD0x07FFD Filling buffer... PASS0x07FFD0x07FFD0x08 51

52 Writing MSB of minimum code size at address 0x7FFE... Setting Address Range... PASS0x07FFE0x07FFE Filling buffer... PASS0x07FFE0x07FFE0x01 Writing LSB of minimum code size at address 0x7FFF... Setting Address Range... PASS0x07FFF0x07FFF Filling buffer... PASS0x07FFF0x07FFF0x7E Programming the device... Setting Address Range... PASS0x000000x07FFF Erasing... PASS Blank checking... PASS0x000000x07FFF Programming memory... PASS0x000000x07FFF Verifying memory... PASS0x000000x07FFF Activating code protection mode... Setting Address Range... PASS0x07FFD0x07FFD Filling buffer... PASS0x07FFD0x07FFD0x28 Programming memory... PASS0x07FFD0x07FFD Starting Application... PASSNORESET0x00000 Summary: Total 26 Passed 26 Failed 0 ****************************** * PART PROGRAMMING COMPLETED * ****************************** 52

53 Atmel Corporation 2325 Orchard Parkway San Jose, CA 95131, USA Tel: 1(408) Fax: 1(408) Regional Headquarters Europe Atmel Sarl Route des Arsenaux 41 Case Postale 80 CH-1705 Fribourg Switzerland Tel: (41) Fax: (41) Asia Room 1219 Chinachem Golden Plaza 77 Mody Road Tsimshatsui East Kowloon Hong Kong Tel: (852) Fax: (852) Japan 9F, Tonetsu Shinkawa Bldg Shinkawa Chuo-ku, Tokyo Japan Tel: (81) Fax: (81) Atmel Operations Memory 2325 Orchard Parkway San Jose, CA 95131, USA Tel: 1(408) Fax: 1(408) Microcontrollers 2325 Orchard Parkway San Jose, CA 95131, USA Tel: 1(408) Fax: 1(408) La Chantrerie BP Nantes Cedex 3, France Tel: (33) Fax: (33) ASIC/ASSP/Smart Cards Zone Industrielle Rousset Cedex, France Tel: (33) Fax: (33) East Cheyenne Mtn. Blvd. Colorado Springs, CO 80906, USA Tel: 1(719) Fax: 1(719) Scottish Enterprise Technology Park Maxwell Building East Kilbride G75 0QR, Scotland Tel: (44) Fax: (44) RF/Automotive Theresienstrasse 2 Postfach Heilbronn, Germany Tel: (49) Fax: (49) East Cheyenne Mtn. Blvd. Colorado Springs, CO 80906, USA Tel: 1(719) Fax: 1(719) Biometrics/Imaging/Hi-Rel MPU/ High Speed Converters/RF Datacom Avenue de Rochepleine BP Saint-Egreve Cedex, France Tel: (33) Fax: (33) Literature Requests Disclaimer: The information in this document is provided in connection with Atmel products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Atmel products. EXCEPT AS SET FORTH IN ATMEL S TERMS AND CONDI- TIONS OF SALE LOCATED ON ATMEL S WEB SITE, ATMEL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL ATMEL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDEN- TAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF ATMEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Atmel makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Atmel does not make any commitment to update the information contained herein. Atmel s products are not intended, authorized, or warranted for use as components in applications intended to support or sustain life. Atmel Corporation All rights reserved. Atmel, logo and combinations thereof are registered trademarks, and Everywhere You AreSM is the trademark of Atmel Corporation or its subsidiaries. Windows, is the registered trademark of Microsoft Corporation. Other terms and product names may be trademarks of others. Printed on recycled paper. xm