UART debug output in mplabx?

Created Wed, 12 Mar 2014 09:47:25 +0000 by benderamp

benderamp

Wed, 12 Mar 2014 09:47:25 +0000

Hello, is it possible to see debug messages from the board in MPLABX when run program on ChipKIT board (Uno32 or WF32) with PicKIT3?

Also, does PicKIT3 itseft supports UART (or UART-like) interface to send string messages from the board in "Serial.println" style without using on-board FTDI available on ChipKITs?

guymc

Wed, 12 Mar 2014 15:13:24 +0000

Hello, is it possible to see debug messages from the board in MPLABX when run program on ChipKIT board (Uno32 or WF32) with PicKIT3?

Full support in MPLAB X is on our wish list, but we're not there yet. It is possible to source debug chipKIT sketches in X, using a procedure developed by Keith Vogel of Digilent. In that scenario, MPIDE is used as the build environment.

Also, does PicKIT3 itseft supports UART (or UART-like) interface to send string messages from the board in "Serial.println" style without using on-board FTDI available on ChipKITs?

The PICkit 3 hardware does not support that sort of data channel. It would be possible with higher end debuggers, such as ICD 3, with some custom software in X.

majenko

Wed, 12 Mar 2014 16:39:41 +0000

Also, does PicKIT3 itseft supports UART (or UART-like) interface to send string messages from the board in "Serial.println" style without using on-board FTDI available on ChipKITs?

The PICkit 3 hardware does not support that sort of data channel. It would be possible with higher end debuggers, such as ICD 3, with some custom software in X.[/quote] Or lower-end, like the PICkit2...

guymc

Thu, 13 Mar 2014 17:29:37 +0000

Or lower-end, like the PICkit2...

That's a cool idea. I would definitely support and encourage the development of a PICkit scripting solution for chipKIT connectivity.

Here's another issue, possibly related: Keith has pointed out that we really need a easy-to-use method for restoring bootloaders on the various chipKIT and Fubarino boards. Perhaps an application (or MPLAB X plug-in) based on PICkit scripting could accomplish both objectives.

If anyone is inclined to dig into this, let me know and I'll look for ways to help.

Cheers

majenko

Thu, 13 Mar 2014 17:38:20 +0000

That's a cool idea. I would definitely support and encourage the development of a PICkit scripting solution for chipKIT connectivity. Here's another issue, possibly related: Keith has pointed out that we really need a easy-to-use method for restoring bootloaders on the various chipKIT and Fubarino boards. Perhaps an application (or MPLAB X plug-in) based on PICkit scripting could accomplish both objectives. If anyone is inclined to dig into this, let me know and I'll look for ways to help. Cheers

UECIDE already has it using the pk2 and serge's pic32prog program.

guymc

Thu, 13 Mar 2014 18:59:40 +0000

UECIDE already has it using the pk2 and serge's pic32prog program.

Very cool! Does UECIDE know which bootloader belongs on which board? And, does it host the bootloader hex files internally, or does the user have to know where to look and download the correct one?

Please excuse the newbie questions.. :-)

majenko

Thu, 13 Mar 2014 20:21:58 +0000

Each board definition can have a

bootloader=whatevererits.hex

enrty, and the bootloader is distributed with the board definition package.

I'm not sure if it's actually working right at the moment as I have made some changes to how the files work and I'm not sure what stage different bits are at ;)