Hi all...I've written code for my stuff at home. You know, the stuff you experimentwith. Not meant to be pretty or a full blown project. If it is something Iwill use in the future - like an LCD init function - I fully document it andplace it in a special "custom" folder.I can write code and it is good. I have a EE and I've being working for 2years now. Little stuff like test boxes and the like are no problem. Atwork, I was told I'm going to get a whole project soon - the boss wasimpressed with a silly test box I made, now he thinks I can make a spaceshuttle. Are they all this clueless ?. I know each part of the design so I'mnot panicking just yet :-). I'm thinking how to implement the differentparts but I don't feel comfortable writing this project like I did my seniorproject. BTW my senior project worked with very few glitches.I just feel I need more info on writing code for embedded systems (that's agood magazine: Embedded Systems Programming ). Before I start cranking outcode, I'd like to get more info on ways of writing code. Can you suggest abook or reference where to start ?ThanksBTW no need for a RTOS. The project is not that complex. It's going to use amicrochip PIC18Fxxxx. I haven't decided which one yet.

No. You're probably just being tested. Just about every programmereventually gets a "I'll never be able to do all this by myself"project. Ie, the boss knows you can write the components, but wantsto see how you handle having to organize a larger project.I'd look at an existing projects or programs that are similar to whatyou will do and see how they were laid out. I don't know any booksoff the top of my head.I'd start by mapping out what the high level components are going tobe and how they will interact with each other. When you've got thelarge chunky jobs and modules figured out, then subdivide them intosmaller pieces. It doesn't have to be incredibly detailed, justenough to give you a roadmap.You don't have to do everything by yourself either; draw up a diagramof what you are planning and show it to your boss and coworkers to seewhat they think.-- Darin Johnson "Floyd here now!"

You will find several articles about Embedded System programming at:Sandeep-- 2.0 - Real-time and Embedded System Design CASE Tool

Hilarious and useful :-) !Thanksaouta

In article , qwelk179 writesFor any one using MISRA-C there is MISTRAY-C that does a similar job:-)see (the serious stuff is on ////////////////////////////// Chris Hills Staffs England //////// ////////////////////////////

How to write better code for your projects ?

Feb 20, 2004 24 Replies

Rate this thread:

EventHelix.com 22 years ago

You will find several articles about Embedded System programming at:

formatting link

Sandeep

formatting link

EventStudio 2.0 - Real-time and Embedded System Design CASE Tool

Vote

qwelk179 22 years ago

I'm surprised nobody has mentioned "How To Write Unmaintainable Code" at

formatting link

- study it, particularly the Naming, Documentation, and Program Design sections. Your project will then reflect actual programming practices, rather than esoteric academic strictures.

Vote

Rodo 22 years ago

Hilarious and useful :-) !

Thanks

out

Vote

Chris Hills 22 years ago

For any one using MISRA-C there is MISTRAY-C that does a similar job :-)

see

formatting link

(the serious stuff is on

formatting link

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/\ /\/\/ snipped-for-privacy@phaedsys.org

formatting link

\/\/ \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Vote

John Larkin 22 years ago

Wow, after reading this, and a few other references, I'm sure glad I program in assembly.

John

Vote

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required