Hello All.
I am working on a PIC32MX low cost device development board for my lab and I have the programming connector for PicKit and realice on the board and would like to use Flowkit with the board,from
the Flowkit manual I do understand that pins A0 and Do are the analog and digital pin connections for ICT and scope in FC however what is not clear to me from the manual is which pins of Flowkit connect to which pins of the target mcu
to allow for ICD functionality
Please help me understand this
Flowkit 2 Connections
- QMESAR
- Valued Contributor
- Posts: 1287
- Joined: Sun Oct 05, 2014 3:20 pm
- Location: Russia
- Has thanked: 384 times
- Been thanked: 614 times
- Contact:
- LeighM
- Matrix Staff
- Posts: 2178
- Joined: Tue Jan 17, 2012 10:07 am
- Has thanked: 481 times
- Been thanked: 699 times
- Contact:
Re: Flowkit 2 Connections
Hi,
There is some detail on page 8 of the Flowkit2 datasheet.
Flowkit Digital Pin D9 is used for the ICD clock, and D8 for data.
D8 and D9 as marked on the Flowkit and numbered as Arduino.
These are the pins on which the ICD clock and data will appear.
How these are mapped onto target port and pin, and compiled into the ICD debug build, will be determined by the settings in the Flowcode "Debuger (ICD)" dialog window.
Hope that helps,
Leigh
There is some detail on page 8 of the Flowkit2 datasheet.
Flowkit Digital Pin D9 is used for the ICD clock, and D8 for data.
D8 and D9 as marked on the Flowkit and numbered as Arduino.
These are the pins on which the ICD clock and data will appear.
How these are mapped onto target port and pin, and compiled into the ICD debug build, will be determined by the settings in the Flowcode "Debuger (ICD)" dialog window.
Hope that helps,
Leigh
- QMESAR
- Valued Contributor
- Posts: 1287
- Joined: Sun Oct 05, 2014 3:20 pm
- Location: Russia
- Has thanked: 384 times
- Been thanked: 614 times
- Contact:
Re: Flowkit 2 Connections
Hi
Thank you very much it is clear now will use Flowkit on this board in future
Thank you very much it is clear now will use Flowkit on this board in future
https://www.flowcodexchange.com/
Regards QMESAR
Regards QMESAR
- petesmart
- Valued Contributor
- Posts: 395
- Joined: Thu May 06, 2010 11:42 am
- Location: Sydney, Australia
- Has thanked: 187 times
- Been thanked: 140 times
- Contact:
Re: Flowkit 2 Connections
Hi Leigh,
What version flow kit do you suggest to debug MIAC? Also will new MIAC range have GHOST built in?
All the best
Pete
What version flow kit do you suggest to debug MIAC? Also will new MIAC range have GHOST built in?
All the best
Pete
sorry about that Chief!
- LeighM
- Matrix Staff
- Posts: 2178
- Joined: Tue Jan 17, 2012 10:07 am
- Has thanked: 481 times
- Been thanked: 699 times
- Contact:
Re: Flowkit 2 Connections
Hi Pete,
We don't currently have a Ghost solution for MIAC.... maybe V4
Leigh
We don't currently have a Ghost solution for MIAC.... maybe V4
Leigh
- petesmart
- Valued Contributor
- Posts: 395
- Joined: Thu May 06, 2010 11:42 am
- Location: Sydney, Australia
- Has thanked: 187 times
- Been thanked: 140 times
- Contact:
Re: Flowkit 2 Connections
Hi Leigh,
Thanks for the update.... Which flowkit should I use with the soon to be released versions of MIAC?
Best
Pete
Thanks for the update.... Which flowkit should I use with the soon to be released versions of MIAC?
Best
Pete
sorry about that Chief!
- LeighM
- Matrix Staff
- Posts: 2178
- Joined: Tue Jan 17, 2012 10:07 am
- Has thanked: 481 times
- Been thanked: 699 times
- Contact:
Re: Flowkit 2 Connections
Hi Pete,
Sorry, Flowkit will not work with the new MIAC (V3) either.
There are no processor logic level signals available outside the MIAC casing, and we could not use USB in the same way as we did on the original. (Due to all the new variants)
We could consider a software solution, but either way it would be a rather large development, so something we will get into once the dust has settled on current projects.
Regards,
Leigh
Sorry, Flowkit will not work with the new MIAC (V3) either.
There are no processor logic level signals available outside the MIAC casing, and we could not use USB in the same way as we did on the original. (Due to all the new variants)
We could consider a software solution, but either way it would be a rather large development, so something we will get into once the dust has settled on current projects.
Regards,
Leigh