DEC-LED Counter Project

This bid request includes IMPORTANT additional attached files. Please download and read fully before bidding. ## Deliverables All files must be formated to latest release for IAR Systems\Embedded Workbench from Texas Instruments downloadable from Texas Instruments web site. The firmware code must be written for MSP430F2013 chip from Texas Instruments. MSP430F2013 chip is located on target board, which is part of eZ430-F2013, a USB stick-based full emulation and development tool from Texas Instruments. I am going to supply with descriptions and other technical data, and you will prepare for my approval the algorithms and block-diagrams, prior writing the code. The algorithms and block-diagrams needs to be approved by me first. The resulting firmware code should be written in C/C++ and/or assembler. The code should have a reasonable commentary. The resulting files have to be compatible with tools form Texas Instruments as a part of eZ430-F2013 KIT: IAR Embedded Workbench Kickstart 4.0 (Free 4KB IDE) <[login to view URL]> Tool Name: IAR Embedded Workbench Kickstart Version 4 Contents: IAR 4.10E/WIN, FET 5.11/WIN (zip, slac050) I did supply you with a lot of documents were you should look for all information related to my project. For example: [login to view URL] diagram will explain to you what I/O port needs to be used for I2C bus; [login to view URL] document and LED_ [login to view URL] diagram give you exact list of address has to be used in order to access the LED Display modules. For example, look again at [login to view URL] document: TPIC2810D_ADDR 0xC0 // Fixed hardware address for LED’s TPIC2810D_SUBADDR 0x44 // Sub address is 0x44, write both PCA9542A_ADDR 0xE0 // Fixed hardware address for PCA9542A PCA9542A_ADDR_RD 0xE1 // Fixed hardware address to read PCA9542A PCA9542A_LED_PRG 0x04 // Configuring PCA9542A to program LED’s PCA9542A_THROUGH 0x05 // Configuring PCA9542A to pass data through PCA9542A_STATUS_INT 0x30 // All interrupt bits in PCA9542A PCA9542A_STATUS_INT0 0x10 // INT0 interrupt bit at PCA9542A PCA9542A_STATUS_INT1 0x20 // INT1 interrupt bit at PCA9542A According to Project Requirements I have placed for you at the beginning of the project, please refer to [login to view URL] diagram and [login to view URL] document, I/O ports of MSP430F2013 for I2C bus have to be assigned as following: 1). [login to view URL] file contains “I2C Interface?? table: Pin ??" 9:? SDA; LD-SDMA (Pin 13, U216) Pin ??" 8:? SCL; LD-SCMA (Pin 12, U216) 2). [login to view URL] file contains “I2C bus must be driven based on the following specifications?? table: -? ? SDA, P1.7 (Pin 9 of MSP430F2013 on Target Board) connected to LD-SDMA (Pin 13 of U216 on LED Display module) -? ? SCL, P1.6 (Pin 8 of MSP430F2013 on Target Board) connected to LD-SCMA (Pin 12 of U216 on LED Display module) You are not first coder I am working with. And all coders I worked with did not have hardware. And they were able to find the way to troubleshoot the code and to eliminate the bags. Nobody perfect. Everybody make mistakes. Writing the code is not easy task, but troubleshooting your own code is even more difficult task. If you willing to use Yahoo! Messenger I can run IAR Embedded Workbench on my PC with hardware attached and read the registry value for you, or we can set breakpoints to stop the code at certain point and use Quick Watch or Watch features to indicate the value of any variable in your code. When you write the code I want you to test it in your system prior you release it to me. And then after the code proving good, I want you to pack it with ZIP and send it to me over RAC. All I wish to do will be just simple operation:? to unpack the files and run the code. Michael