Debug

For Flowcode users to discuss projects, flowcharts, and any other issues related to Flowcode 5.
To post in this forum you must have a registered copy of Flowcode 5 or higher.

Moderator: Benj

Post Reply
echase
Posts: 429
Joined: Mon Jun 11, 2007 11:55 am
Has thanked: 49 times

Debug

Post by echase »

Are any of the debug features of PICkit 3 usable in Flowcode?

Afraid I don’t really understand what debug tools are all about. Do you have a tutorial? As my application is a high speed and real time one I can’t get my head around the point of stepping through a programme slowly as it would miss all the real time external triggers so fail to work properly/at all. Same reason my Flowcode simulations don’t work well as there is no waveform generator in Flowcode to trigger them. Think of it like a frequency counter application. If you step through slowly, whilst inputting a high frequency, the programme will entirely miss a proper measurement of the signal and mis trigger.

So generally I do debugging by writing intermediate variables to an LCD in real time and correct the code when the variables dispaly the wrong value.
Last edited by echase on Wed May 23, 2012 10:07 am, edited 1 time in total.

User avatar
Benj
Matrix Staff
Posts: 15312
Joined: Mon Oct 16, 2006 10:48 am
Location: Matrix TS Ltd
Has thanked: 4803 times
Been thanked: 4314 times
Contact:

Re: Debug

Post by Benj »

Hello,

Flowcode cannot debug directly using the PICkit 3,

You can either use the Flowkit to debug on a flowchart level from inside Flowcode or you can import the Flowcode generated C code into MPLAB and debug using your PICkit 3. You will need your own license for the BoostC compiler to be able to do this.

Flowcode ICD allows things like breakpoints so you can run the program and get it to automatically jump out at the right point to allow you to step through.

Another helpful tool is our EB070 digital test pod using the USBee technology. This allows you to record and decode the external signals to help track down issues that may be hardware based rather then purely software based.

Writing values to a LCD is another valid form of debugging. I use it a lot :D

Post Reply