DEBUGGING SUB FORUM

Community Suggestions for the Arduino Project
1

Hi

I would suggest to start a DEBUGGING sub forum here that will be deal with debugging issues in design time and in run time .

Thanks
EC

2

Can you explain what you mean by debugging in design time? I have my associations but I like to hear what you intent.
Maybe explain the diff?

3

elico copped a bit if flack on another thread for using the term.

FWIW my definition is that "design time" is any time before the product ships or at least before the point at which the code is locked and you are just stress testing with no debugging code in place. IE as it will run in the field.

"run time" (although I wouldn't use that term in this context) is actually after the above point but probably really "in the field" is a better expression.

So back to the original question, a new forum. Good luck with that because AFAIK not one single request of this nature has ever been acknowledged let alone implemented.

That said I think there is a real need for a method to show newbies how to debug code and hardware.

How many times do we tell people to print out a variable to see what it is? To disable code sections to isolate an error etcetera etcetera. (Apologies to Yul Brynner)

Actually I think a Saleae logic analyser should be shipped with every Arduino :), but that's another story.

Rob

4

The way to get a new sub-forum started is to overrun some existing forum with so much discussion that the other people using it start complaining, and insist that you move to your own spot.

Go ahead and start discussing debugging in the "Microprocessors" forum; after all, you're likely to touch on Debugwire, JTAG, and primitive capabilities of the CPU. AND besides, that's one that I read regularly!

5

That said I think there is a real need for a method to show newbies how to debug code and hardware.

If so there is also a need to do: (loosely described)

  • requirements - learning to describe properly what the system must do in what context. (GOAL)
  • analysis - understanding details of the requirements, check feasability, interference between requirements (WHAT)
  • design - make a logical decomposition, what must be done in HW what must be done in SW what can be done in both, (HOW)
    (includes reading datasheets of sensors etc)
    further
  • soldering course
  • communciation protocols ( I agree with GrayNomads Saelogic idea although with every Arduino might be overkill :wink:

and of course some things about the process

  • some lessons about version control, making back ups, documentation of your sketch

Time to develop an MBA course? - MBA = "Master in Building Arduinoware"