|
|
Post by stefankrupop on Sept 8, 2016 20:08:25 GMT
Pinout of J100 should be:
|-----------\
| 9 7 5 3 1 |
|10 8 6 4 2 |
|-----------|
1 = VCC
2 = AT Pin 20
3 = AT Pin 32 (SWDIO)
4 = AT Pin 19
5 = AT Pin 31 (SWCLK)
6 = AT Pin 18
7 = GND
8 = AT Pin 17
9 = GND
10 = GND
(However, the security bit seems to be set on the SAM D20)
The testpoints are connected to:
TP100 = AT Pin 26 (nRESET)
TP300 = SSM2211 Shutdown / AT Pin 4
TP405 = Q402 Pin 3
TP411 = Si GPIO1
TP414 = Si nIRQ
TP415 = Si GPIO2
Kind regards,
Stefan
|
|
|
|
Post by progman on Sept 11, 2016 16:22:38 GMT
thanks stephan, i uploaded the picture of J100.  and the connection of SI4362   |
|
|
|
Post by fnicoli on Jan 21, 2018 14:28:46 GMT
Do you think the security bit is set because you can't connect a swd probe?
I'm using my raspberry pi as a probe with OpenOCD, but can't connect to the chip. The security bits on the SAMD20 should not disable SWD pins, but if it's set, we will never get the flash content.
Anyway, I was planning on wiping the whole thing to disable the security bit. Then I could hard-code some LED activity and maybe add an nRF24L01 module.
The xyloband I have in hands is the speaker model, but there's no speaker and the amplifier IC is not populated. That frees up some space at the top of the board.
It was used in a concent on Porto Alegre, Brazil, at the end of 2017.
|
|
|
|
Post by fnicoli on Jan 21, 2018 16:59:49 GMT
Now I'm a registered user. Looks like OpenOCD was trying to hot-plug attach into the microcontroller (connect to it while running). SAMD20 devices won't allow this if the chip is protected, but you can cold-plug attach to the target (connect while reseted) using a special sequence of SWCLK and nRST. This OpenOCD mailing list thread explains it for the raspberry pi. |
|
|
|
Post by fnicoli on Jan 21, 2018 20:14:14 GMT
Pinout of J100 should be:
|-----------\
| 9 7 5 3 1 |
|10 8 6 4 2 |
|-----------|
1 = VCC 2 = AT Pin 20 3 = AT Pin 32 (SWDIO) 4 = AT Pin 19 5 = AT Pin 31 (SWCLK) 6 = AT Pin 18 7 = GND 8 = AT Pin 17 9 = GND 10 = GND Also, PA17, PA18, PA19 and PA20 are associated with one SERCOM peripheral. These interfaces can operate as USART, I²C or SPI. I can imagine them being used either for debugging over USART or maybe acting as a SPI slave for configuration without reflashing (zones maybe?). Still, I don't understand why there's no RST pin on this header. Maybe it's programmed with a generic FW over SWD using the test point and then reconfigured through the SERCOM using simpler tools. |
|
