Prev: STR912 ARM with SSD1906 TFT controller
Next: another bizarre architecture
From: mInfo on 29 Jan 2007 15:37
I'm currently searching the coder (firmware) who has experience
with I2C bus. I am looking for firmware solutions for my prototype
that will be used in manufacturing testing for I2C LED Modules. Each
module contains six of TPIC2810 LED Driver chips with Address from
1100000X to 1100101X. All of 8 outputs for each LED Driver are loaded
with LED. I need to use LED Display Module for displaying the counters
located at MSP430F2013 Microcontroller. Each LED Display Module has
two push-buttons. Pressing on one of push-buttons will generate
interrupt for MSP430F2013 Microcontroller. PCA9542A I2C switch with
interrupt manager is used to detect the source of interruption. Each
interruption from push-buttons will update the counter by increasing
or decreasing the previous value depending on which push-button was
pressed. I2C switch is used to manage multiple-module structure on I2C
bus.

The firmware code must be written for MSP430F2013 chip from Texas
Instruments. MSP430F2013 chip is part of eZ430-F2013, a USB stick-
based full emulation and development tool from Texas Instruments. I am
going to supply with schematics, algorithms and block-diagrams.
The resulting code must be written in C/C++ and assembler. The
code must have commentary for each line of code. The code should be
written to be used only with tools form Texas Instruments as a part of
eZ430-F2013 KIT:
1. IAR Embedded Workbench Kickstart 4.0 (Free 4KB IDE)
2. TI Code Composer Essentials Evaluation v2.0 (Free 8KB IDE) FET
3. TI Code Composer Essentials Professional v2.0 (Unlimited Code
Space)

Code examples: http://www-k.ext.ti.com/SRVS/CGI-BIN/WEBCGI.EXE/,/?
St=52,E=0000000000007406960,K=9621,Sxi=4,Case=obj(39245)

From: larwe on 29 Jan 2007 16:20


On Jan 29, 4:37 pm, "mInfo" <mas...(a)limosinfo.com> wrote:
> The resulting code must be written in C/C++ and assembler. The
> code must have commentary for each line of code. The code should be

Sounds like this is a school project. If it was a valid contract job,
you would not have nonsensical requirements like the above.

From: mInfo on 30 Jan 2007 00:42
On Jan 29, 1:20 pm, "larwe" <zwsdot...(a)gmail.com> wrote:
> On Jan 29, 4:37 pm, "mInfo" <mas...(a)limosinfo.com> wrote:
>
> > The resulting code must be written in C/C++ and assembler. The
> > code must have commentary for each line of code. The code should be
>
> Sounds like this is a school project. If it was a valid contract job,
> you would not have nonsensical requirements like the above.

Did you say "nonsensical requirements like the above"? Have you ever
paid attention when you were reading the text? It says absolutely
clear "testing code" to test the prototype only. Yes, it has to be at
'school project' level, simple code to test the hardware.

From: larwe on 30 Jan 2007 09:33


On Jan 30, 12:42 am, "mInfo" <mas...(a)limosinfo.com> wrote:
> On Jan 29, 1:20 pm, "larwe" <zwsdot...(a)gmail.com> wrote:
>
> > On Jan 29, 4:37 pm, "mInfo" <mas...(a)limosinfo.com> wrote:
>
> > > The resulting code must be written in C/C++ and assembler. The
> > > code must have commentary for each line of code. The code should be
>
> > Sounds like this is a school project. If it was a valid contract job,
> > you would not have nonsensical requirements like the above.Did you say "nonsensical requirements like the above"? Have you ever
> paid attention when you were reading the text? It says absolutely

Yes. And, like most other people in this NG, I have experience doing
an awful lot of school projects. I also have experience doing an awful
lot of customer projects for people who don't know what the buzzwords
they are using actually mean.

If you had written "adequately commented code developed with free
tools" I would not have had a problem.

I'd still bet money that this is a school project cut and pasted from
your homework sheet, but I'll grant the outside possibility that it is
a legitimate (though unpalatable) contract and you are simply
regurgitating specification bullet points you don't really understand.

From: Elan Magavi on 30 Jan 2007 12:19

"larwe" <zwsdotcom(a)gmail.com> wrote in message
news:1170167621.271945.256720(a)v45g2000cwv.googlegroups.com...
>
>
> On Jan 30, 12:42 am, "mInfo" <mas...(a)limosinfo.com> wrote:
>> On Jan 29, 1:20 pm, "larwe" <zwsdot...(a)gmail.com> wrote:
>>
>> > On Jan 29, 4:37 pm, "mInfo" <mas...(a)limosinfo.com> wrote:
>>
>> > > The resulting code must be written in C/C++ and assembler. The
>> > > code must have commentary for each line of code. The code should be
>>
>> > Sounds like this is a school project. If it was a valid contract job,
>> > you would not have nonsensical requirements like the above.Did you say
>> > "nonsensical requirements like the above"? Have you ever
>> paid attention when you were reading the text? It says absolutely
>
> Yes. And, like most other people in this NG, I have experience doing
> an awful lot of school projects. I also have experience doing an awful
> lot of customer projects for people who don't know what the buzzwords
> they are using actually mean.
>
> If you had written "adequately commented code developed with free
> tools" I would not have had a problem.
>
> I'd still bet money that this is a school project cut and pasted from
> your homework sheet, but I'll grant the outside possibility that it is
> a legitimate (though unpalatable) contract and you are simply
> regurgitating specification bullet points you don't really understand.
>

In 25 years I have never actually seen code with every line commented. Ever.



 |  Next  |  Last
Pages: 1 2
Prev: STR912 ARM with SSD1906 TFT controller
Next: another bizarre architecture