Debugging Hardware and Software - Revision history

DavidA at 08:35, 2 July 2019

2019-07-02T08:35:20Z

PaulN at 12:45, 27 June 2016

2016-06-27T12:45:01Z

BenR at 18:28, 7 March 2014

2014-03-07T18:28:57Z

BenR at 17:12, 7 March 2014

2014-03-07T17:12:31Z

Admin at 14:53, 1 November 2013

2013-11-01T14:53:33Z

Admin at 14:52, 1 November 2013

2013-11-01T14:52:16Z

ReeceL at 14:54, 5 September 2013

2013-09-05T14:54:11Z

ReeceL at 14:53, 5 September 2013

2013-09-05T14:53:42Z

ReeceL at 14:53, 5 September 2013

2013-09-05T14:53:28Z

ReeceL at 14:53, 5 September 2013

2013-09-05T14:53:12Z

← Older revision		Revision as of 08:35, 2 July 2019
Line 1:		Line 1:
−	~~<sidebar>Sidebar: Flowcode Help Overview:ChipSpecific</sidebar>~~
	Debugging can be a tricky task especially if you are unfamiliar with a specific routine or component and the way it is meant to behave.		Debugging can be a tricky task especially if you are unfamiliar with a specific routine or component and the way it is meant to behave.

← Older revision		Revision as of 12:45, 27 June 2016
Line 15:		Line 15:


−	Another good technique for debugging in v6 is to use the simulation to light the way but also use the downloaded code to sanity check that the simulation and the downloaded code match up. If you start getting inconsistencies then it may well be worth checking your code or asking the author of any specific component code to check and see if they get the same issue.	+	Another good technique for debugging in Flowcode is to use the simulation to light the way but also use the downloaded code to sanity check that the simulation and the downloaded code match up. If you start getting inconsistencies then it may well be worth checking your code or asking the author of any specific component code to check and see if they get the same issue.

	If these two steps fail to help your problem then it may be worth using a user interface device like a LCD or gLCD to display values at runtime to double check that values are as they should be.		If these two steps fail to help your problem then it may be worth using a user interface device like a LCD or gLCD to display values at runtime to double check that values are as they should be.

← Older revision		Revision as of 18:28, 7 March 2014
Line 22:		Line 22:
	The Flowcode ICD interface can be enabled via the Project Options to allow the embedded code to be investigated in more detail if necessary. When ICD is enabled you have the ability to start, stop, pause and step through the code on the microcontroller from within the Flowcode environment. The Matrix EB006 and FlowKit are currently the only means of connecting the Flowcode ICD system to your hardware but there are plans for more ICD and Test platforms in the future.		The Flowcode ICD interface can be enabled via the Project Options to allow the embedded code to be investigated in more detail if necessary. When ICD is enabled you have the ability to start, stop, pause and step through the code on the microcontroller from within the Flowcode environment. The Matrix EB006 and FlowKit are currently the only means of connecting the Flowcode ICD system to your hardware but there are plans for more ICD and Test platforms in the future.

−	If all of the above techniques have failed then report the bug you are having to the [http://www.matrixmultimedia.com/mmforums/index.php Matrix user forums] providing as much detail as you can to allow others to replicate the problem. Attaching your Flowcode project file to the post is usually an easy way to ensure that others are able to help you around any potential pitfalls or problems.	+	If all of the above techniques have failed then report the bug you are having to the [http://www.matrixmultimedia.com/mmforums/index.php Matrix user forums] providing as much detail as you can to allow others to replicate the problem. Attaching your Flowcode project file to the post and describing your hardware setup is usually an easy way to ensure that others are able to help you around any potential pitfalls or problems.

← Older revision		Revision as of 17:12, 7 March 2014
Line 1:		Line 1:
−	<sidebar>Sidebar: ~~Advanced Features~~</sidebar>	+	<sidebar>Sidebar: Flowcode Help Overview:ChipSpecific</sidebar>
	Debugging can be a tricky task especially if you are unfamiliar with a specific routine or component and the way it is meant to behave.		Debugging can be a tricky task especially if you are unfamiliar with a specific routine or component and the way it is meant to behave.

@@ Line 10: / Line 10: @@
 ::Try running a [[One second LED flasher]] program on your hardware to sanity check.
 *Are the [[Component Properties]] setup correctly for your hardware?
-::Try to test the basics before moving onto more advanced features.
+::Try to test the basics on hardware before moving onto more advanced features. Take your time and do a bit at a time. The more stages you can break your required functionality into means the easier it is to pinpoint a problem and resolve it.
 *Is the ICD mode enabled in the Project Options but no ICD hardware available?
 ::A program designed for ICD will not be allowed to run without the start instruction passed from the ICD hardware.

@@ Line 6: / Line 6: @@
 Key things to check for include:
 *Is the clock speed in the [[Project Options]] dialogue setup correctly for your hardware?
-::Try running a one second LED flasher program on your hardware to sanity check.
+::Try running a [[One second LED flasher]] program on your hardware to sanity check.
 *Is the [[Configuring the Chip|device configuration]] in the Project Options setup correctly for your hardware?
-::Try running a one second LED flasher program on your hardware to sanity check.
+::Try running a [[One second LED flasher]] program on your hardware to sanity check.
 *Are the [[Component Properties]] setup correctly for your hardware?
 ::Try to test the basics before moving onto more advanced features.

@@ Line 18: / Line 18: @@
 If these two steps fail to help your problem then it may be worth using a user interface device like a LCD or gLCD to display values at runtime to double check that values are as they should be.
 The Flowcode ICD interface can be enabled via the Project Options to allow the embedded code to be investigated in more detail if necessary. When ICD is enabled you have the ability to start, stop, pause and step through the code on the microcontroller from within the Flowcode environment. The Matrix EB006 and FlowKit are currently the only means of connecting the Flowcode ICD system to your hardware but there are plans for more ICD and Test platforms in the future.
 If all of the above techniques have failed then report the bug you are having to the [http://www.matrixmultimedia.com/mmforums/index.php Matrix user forums] providing as much detail as you can to allow others to replicate the problem. Attaching your Flowcode project file to the post is usually an easy way to ensure that others are able to help you around any potential pitfalls or problems.

@@ Line 5: / Line 5: @@
 Key things to check for include
-:*Is the clock speed in the [[Project Options]] dialogue setup correctly for your hardware?
+*Is the clock speed in the [[Project Options]] dialogue setup correctly for your hardware?
-:::Try running a one second LED flasher program on your hardware to sanity check.
+::Try running a one second LED flasher program on your hardware to sanity check.
-:*Is the [[Configuring the Chip|device configuration]] in the Project Options setup correctly for your hardware?
+*Is the [[Configuring the Chip|device configuration]] in the Project Options setup correctly for your hardware?
-:::Try running a one second LED flasher program on your hardware to sanity check.
+::Try running a one second LED flasher program on your hardware to sanity check.
-:*Are the [[Component Properties]] setup correctly for your hardware?
+*Are the [[Component Properties]] setup correctly for your hardware?
-:::Try to test the basics before moving onto more advanced features.
+::Try to test the basics before moving onto more advanced features.
-:*Is the ICD mode enabled in the Project Options but no ICD hardware available?
+*Is the ICD mode enabled in the Project Options but no ICD hardware available?
-:::A program designed for ICD will not be allowed to run without the start instruction passed from the ICD hardware.
+::A program designed for ICD will not be allowed to run without the start instruction passed from the ICD hardware.
 Another good technique for debugging in v6 is to use the simulation to light the way but also use the downloaded code to sanity check that the simulation and the downloaded code match up. If you start getting inconsistencies then it may well be worth checking your code or asking the author of any specific component code to check and see if they get the same issue.