Re: Testing firmware developed on CCS compiler

nehallove · Joined: 16 Jan 2008 Posts: 61

Hi All,

I am new to this embedded system development. And I am in testing phase of my firmware. I wanted to know how people test their firmware developed on CCS compiler.

Currently I just go into debugger and call function and pass different values according to test plan. Is there anyway that i could use some scripting language and link to code and do automated testing?

I never have this kind of experience before. If someone can guide me through it, it would be a great help.

Thank you,
nehal
_________________
nehal

SherpaDoug · Joined: 07 Sep 2003 Posts: 1640 Location: Cape Cod Mass USA

A lot of the problems I have are to do with critical timing, not values. So my LogicPort logic analyzer is more valuable than the debugger.

Its not just WHAT you know but WHEN you know it.
_________________
The search for better is endless. Instead simply find very good and get the job done.

bkamen · Posted: Wed Apr 21, 2010 11:38 pm

Yea, I have an Agilent mixed signal scope.

I love it. It's my best friend when looking at SPI/I2C buses.

Having a good scope will probably be your best friend too.
(digital is recommended for capture/storage)

-Ben
_________________
Dazed and confused? I don't think so. Just "plain lost" will do. :D

sjb · Joined: 13 Apr 2010 Posts: 34 Location: UK

Similar here. I mostly use an Agilent 54641D mixed mode oscilloscope for testing things like I2C, spi and CAN, and anything where timing is critical.

I also do a range of white, black and grey box testing - which depends on circumstance - using purpose built test code to exercise functionality. Test code is often run with with the gnu c compiler, so that the algorithms get tested independently of the compiler.

I also like to lint as I go using splint, or PCLint or by just compiling with gnu c if the code is generic enough, or with other PIC compiler(s) if it's h/w centric.

Last, but not least, we code review with independent firmware engineer.