[PIC]

[Clint Jay]

How odd, A few weeks after receiving one of the 'phantom' Microchip order
confirmations, I received a PIC16F18446 board yesterday, no recollection of
ordering it (I'm old but not that old).


Cute little board and it's a nice mashup of Atmel and Microchip as it seems
to use an ATSAMD21 as USB interface and programmer for the 'F18446.

[James Burkart]

I received one too, but I do remember someone on this list letting us know
of the promo and ordering one for myself.

Post by Clint Jay
How odd, A few weeks after receiving one of the 'phantom' Microchip order
confirmations, I received a PIC16F18446 board yesterday, no recollection of
ordering it (I'm old but not that old).
Cute little board and it's a nice mashup of Atmel and Microchip as it seems
to use an ATSAMD21 as USB interface and programmer for the 'F18446.
--
Clint. M0UAW IO83
*No trees were harmed in the sending of this mail. However, a large number
of electrons were greatly inconvenienced.*
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

[C. Abney]

I received two, since the first order seemed to have no result and I
was interested enough to try again.

I tried poking around for ways to use the (m?n?)eDBG interface of the
atmel chip. I haven't seen anything that looks like a method, or even
an API.

the virtual COM port over USB let's you connect using [mini|pico]com,
but I can't figure out what commands can be sent.

Of course, MPLAB knows nothing about this.

Post by James Burkart
I received one too, but I do remember someone on this list letting us know
of the promo and ordering one for myself.

Post by Clint Jay
How odd, A few weeks after receiving one of the 'phantom' Microchip order
confirmations, I received a PIC16F18446 board yesterday, no recollection of
ordering it (I'm old but not that old).
Cute little board and it's a nice mashup of Atmel and Microchip as it seems
to use an ATSAMD21 as USB interface and programmer for the 'F18446.
--
Clint. M0UAW IO83
*No trees were harmed in the sending of this mail. However, a large number
of electrons were greatly inconvenienced.*
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

[Denny Esterline]

I have yet to get around to playing with it, but the aspect that intrigued
me was
the programmer is supposed to act as a storage device and mount as a drive.
Supposedly it is programmable by saving a new hex file.

Post by C. Abney
I received two, since the first order seemed to have no result and I
was interested enough to try again.
I tried poking around for ways to use the (m?n?)eDBG interface of the
atmel chip. I haven't seen anything that looks like a method, or even
an API.
the virtual COM port over USB let's you connect using [mini|pico]com,
but I can't figure out what commands can be sent.
Of course, MPLAB knows nothing about this.

Post by James Burkart
I received one too, but I do remember someone on this list letting us

know

Post by James Burkart
of the promo and ordering one for myself.

Post by Clint Jay
How odd, A few weeks after receiving one of the 'phantom' Microchip

order

Post by James Burkart

Post by Clint Jay
confirmations, I received a PIC16F18446 board yesterday, no recollection of
ordering it (I'm old but not that old).
Cute little board and it's a nice mashup of Atmel and Microchip as it seems
to use an ATSAMD21 as USB interface and programmer for the 'F18446.
--
Clint. M0UAW IO83
*No trees were harmed in the sending of this mail. However, a large number
of electrons were greatly inconvenienced.*
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--
If you're in my band you can't have too much of a sense of dignity. --
"Weird Al" Yankovic
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

[Harold Hallikainen]

Post by Denny Esterline
I have yet to get around to playing with it, but the aspect that intrigued
me was
the programmer is supposed to act as a storage device and mount as a drive.
Supposedly it is programmable by saving a new hex file.

That's interesting! Doesn't do much for debug, though. The bootloaders
I've written all take the hex file directly. Some take it as an HTTP post
where it's parsed to a binary image for the chip, saved in external flash,
then copied back to internal flash. Others accept the hex file over UART
or SPI, then parse and write directly to internal flash. This is great for
field updates, but, of course, does not support debug.

Harold

[Ryan O'Connor]

I also got one of those tiny boards. But how do I use it? There seems to be
a usb-type plug but I don't have any cables which fit it.

Ryan

Post by Denny Esterline

Post by Denny Esterline
I have yet to get around to playing with it, but the aspect that

intrigued

Post by Denny Esterline
me was
the programmer is supposed to act as a storage device and mount as a drive.
Supposedly it is programmable by saving a new hex file.

That's interesting! Doesn't do much for debug, though. The bootloaders
I've written all take the hex file directly. Some take it as an HTTP post
where it's parsed to a binary image for the chip, saved in external flash,
then copied back to internal flash. Others accept the hex file over UART
or SPI, then parse and write directly to internal flash. This is great for
field updates, but, of course, does not support debug.
Harold
--
FCC Rules Updated Daily at http://www.hallikainen.com
Not sent from an iPhone.
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

[C. Abney]

Eh? It takes micro-B, and to use it you simply plug it in to your
computer, and drop your .hex file onto the (ramdisk type) directory
that shows up in your filesystem.

How one uses the eDBG features, though, is beyond me.

Post by Ryan O'Connor
I also got one of those tiny boards. But how do I use it? There seems to be
a usb-type plug but I don't have any cables which fit it.
Ryan
On Fri, 29 Jun 2018 at 06:45, Harold Hallikainen

Post by Denny Esterline

Post by Denny Esterline
I have yet to get around to playing with it, but the aspect that

intrigued

Post by Denny Esterline
me was
the programmer is supposed to act as a storage device and mount as a drive.
Supposedly it is programmable by saving a new hex file.

That's interesting! Doesn't do much for debug, though. The bootloaders
I've written all take the hex file directly. Some take it as an HTTP post
where it's parsed to a binary image for the chip, saved in external flash,
then copied back to internal flash. Others accept the hex file over UART
or SPI, then parse and write directly to internal flash. This is great for
field updates, but, of course, does not support debug.
Harold
--
FCC Rules Updated Daily at http://www.hallikainen.com
Not sent from an iPhone.
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

[Ryan O'Connor]

It seems that it uses Data Gateway Interface. Can you find any further
documentation on that?

Ryan

Post by C. Abney
Eh? It takes micro-B, and to use it you simply plug it in to your
computer, and drop your .hex file onto the (ramdisk type) directory
that shows up in your filesystem.
How one uses the eDBG features, though, is beyond me.

Post by Ryan O'Connor
I also got one of those tiny boards. But how do I use it? There seems to

be

Post by Ryan O'Connor
a usb-type plug but I don't have any cables which fit it.
Ryan
On Fri, 29 Jun 2018 at 06:45, Harold Hallikainen

Post by Denny Esterline

Post by Denny Esterline
I have yet to get around to playing with it, but the aspect that

intrigued

Post by Denny Esterline
me was
the programmer is supposed to act as a storage device and mount as a drive.
Supposedly it is programmable by saving a new hex file.

That's interesting! Doesn't do much for debug, though. The bootloaders
I've written all take the hex file directly. Some take it as an HTTP

post

Post by Ryan O'Connor

Post by Denny Esterline
where it's parsed to a binary image for the chip, saved in external flash,
then copied back to internal flash. Others accept the hex file over UART
or SPI, then parse and write directly to internal flash. This is great for
field updates, but, of course, does not support debug.
Harold
--
FCC Rules Updated Daily at http://www.hallikainen.com
Not sent from an iPhone.
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

--
If you're in my band you can't have too much of a sense of dignity. --
"Weird Al" Yankovic
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

[Chris Roper]

This may help:

Atmel EDBG-based Tools Protocols
Introduction
SIDEBAR <https://www.microchip.com/webdoc/protocoldocs/ch01s02.html#> PREV
<https://www.microchip.com/webdoc/protocoldocs/ch01s01.html> | UP
<https://www.microchip.com/webdoc/protocoldocs/protocoldocs.Introduction.html>
| NEXT
<https://www.microchip.com/webdoc/protocoldocs/protocoldocs.cmsis_dap.html>
Atmel EDBG-based tool implementations

The protocol-set described in this document is intended for use on EDBG
platforms as well as standalone debuggers. The JTAGICE3 firmware version 3
upgrades that tool to support SAMD20, and implements parts of the
protocol-set described here. EDBG implementations are very limited subsets
os this protocol which support the particular Atmel controller mounted on
that board.

*Table 1. Atmel EDBG-based tool implementations*
ToolUSB PIDSupportsNotes
EDBG 0x2111

Only the Atmel device mounted on that board

CDC Virtual COM port and Atmel Data Gateway Interface support varies
between different kits

As used on Xplained Pro boards
mEDBG 0x2145

Only the Atmel device mounted on that board

CDC Virtual COM port

As used on Xplained Mini boards
JTAGICE3 0x2140

Programming of all Atmel AVR devices using SPI, PDI, JTAG and aWire

Debugging of all Atmel AVR devices with on-chip debug capability using
debugWIRE, PDI, JTAG and aWire

Programming and debugging of all Atmel SAMD, SAM3 and SAM4 devices using
SWD and JTAG

FW version 3 and later
Atmel-ICE 0x2141

Programming of all Atmel AVR devices using SPI, TPI, PDI, JTAG and aWire

Debugging of all Atmel AVR devices with on-chip debug capability using
debugWIRE, PDI, JTAG and aWire

Programming and debugging of all Atmel SAMD, SAM3 and SAM4 devices using
SWD and JTAG


Note that capability of each implementation should be queried from the tool
itself rather than based upon the lists here.

Future Atmel standalone debuggers will also implement the same CMSIS-DAP
based protocol as described here.

JTAGICE3 (FW version 2 and earlier) implements a custom USB interface which
is no longer supported.
https://www.microchip.com/webdoc/protocoldocs/ch01s02.html

[C. Abney]

To Chris and Ryan,

I've pored over those pages for awhile as well and, based on that
cursory reading, DGI CMSIS, etc., may be restricted to the pins.

I want to send something over the virtual COM port using some terminal
emulation program, and get some response.

For example, I can connect using "picocom /dev/ttyACM0", but then...
what? I've tried various things, in vain. It doesn't act like a
modem, it cannot see the files on the ramdisk, and I don't receive an
OK if I try some of those commands on that eDBG protocol page that
should elicit one.

poop. This means that debugging must be done using MPLABs virtual
machine :(. I can't even use my pickit3.

Post by Chris Roper
Atmel EDBG-based Tools Protocols
Introduction
SIDEBAR <https://www.microchip.com/webdoc/protocoldocs/ch01s02.html#> PREV
<https://www.microchip.com/webdoc/protocoldocs/ch01s01.html> | UP
<https://www.microchip.com/webdoc/protocoldocs/protocoldocs.Introduction.html>
| NEXT
<https://www.microchip.com/webdoc/protocoldocs/protocoldocs.cmsis_dap.html>
Atmel EDBG-based tool implementations
The protocol-set described in this document is intended for use on EDBG
platforms as well as standalone debuggers. The JTAGICE3 firmware version 3
upgrades that tool to support SAMD20, and implements parts of the
protocol-set described here. EDBG implementations are very limited subsets
os this protocol which support the particular Atmel controller mounted on
that board.
*Table 1. Atmel EDBG-based tool implementations*
ToolUSB PIDSupportsNotes
EDBG 0x2111
Only the Atmel device mounted on that board
CDC Virtual COM port and Atmel Data Gateway Interface support varies
between different kits
As used on Xplained Pro boards
mEDBG 0x2145
Only the Atmel device mounted on that board
CDC Virtual COM port
As used on Xplained Mini boards
JTAGICE3 0x2140
Programming of all Atmel AVR devices using SPI, PDI, JTAG and aWire
Debugging of all Atmel AVR devices with on-chip debug capability using
debugWIRE, PDI, JTAG and aWire
Programming and debugging of all Atmel SAMD, SAM3 and SAM4 devices using
SWD and JTAG
FW version 3 and later
Atmel-ICE 0x2141
Programming of all Atmel AVR devices using SPI, TPI, PDI, JTAG and aWire
Debugging of all Atmel AVR devices with on-chip debug capability using
debugWIRE, PDI, JTAG and aWire
Programming and debugging of all Atmel SAMD, SAM3 and SAM4 devices using
SWD and JTAG
Note that capability of each implementation should be queried from the tool
itself rather than based upon the lists here.
Future Atmel standalone debuggers will also implement the same CMSIS-DAP
based protocol as described here.
JTAGICE3 (FW version 2 and earlier) implements a custom USB interface which
is no longer supported.
https://www.microchip.com/webdoc/protocoldocs/ch01s02.html
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist