Conversation
|
We have received the PICkit3, but I'm still struggling to flash the device from Linux. Not sure which tool I need to install and the |
|
You need MPLAB-IPE: http://www.microchip.com/mplabx-ide-linux-installer http://microchip.wikidot.com/ipe:installation I have stopping using MPLAB though and I'm using this instead (written https://github.com/sergev/pic32prog The only issue with this, is you have to reflash the firmware on the http://ww1.microchip.com/downloads/en/DeviceDoc/PICkit3%20Programmer%20Application%20v3.10.zip Neil On 11/21/16 16:16, Oleg Hahm wrote:
|
|
Thanks for the super fast response. I'm currently following this guide: http://www.electropepper.org/blog/item/linux-terminal-only-pic-programming If this doesn't work, I will try to see if I can find a Windows computer. |
|
You could try pickle if you have a Ci40 as well: https://docs.creatordev.io/clicker/guides/quick-start-guide/#programming-a-6lowpan-clicker Some more help here: https://docs.creatordev.io/wifire/guides/wifire-programming/ Neil On 11/21/16 16:27, Oleg Hahm wrote:
|
|
Couldn't get the Clicker to get programmed, but at least the Wifire. Maybe I connected the pins wrong. |
|
My board has resistor links on the back to select between ICSP (pickit) On 11/21/16 17:39, Oleg Hahm wrote:
|
|
Will try to come back to this next week. |
|
Lately the weeks are getting looooooong... |
2ea04a6 to
390ab20
Compare
|
Hi there seems to be something odd going on with the CI system. /opt/jenkins/workspace/RIOT_PR_PR-6092-SJA35D5NQ53ATHG7JEZVLUVZD4XF653KSXZJCQIBIKAGQUBXUZUA/jenkins_bin/ (used by mips-malta and pic32-clicker) Which results in random build failures each time the CI is run. |
kaspar030
left a comment
There was a problem hiding this comment.
- minor nitpicks about the license header blocks
- some possible code duplication
Looking forward to have "real" mips boards supported! ;)
cpu/mips_pic32_common/periph/uart.c
Outdated
| @@ -0,0 +1,76 @@ | |||
| /* | |||
| * Copyright 2016, Imagination Technologies Limited and/or its | |||
There was a problem hiding this comment.
Here and in all other files: please use "Copyright (C) 2016 ...", for consistency.
| * This file is subject to the terms and conditions of the GNU Lesser | ||
| * General Public License v2.1. See the file LICENSE in the top level | ||
| * directory for more details. | ||
| */ |
There was a problem hiding this comment.
Please add a newline after each license block. (This file and some others)
| @@ -0,0 +1,52 @@ | |||
| /* | |||
| * Copyright 2016, Imagination Technologies Limited and/or its | |||
| * affiliated group companies. | |||
There was a problem hiding this comment.
Here and other files: please add newline before license text.
| @@ -0,0 +1,3 @@ | |||
| MODULE = p32mz2048efg100 | |||
There was a problem hiding this comment.
No need for MODULE if the name equals the folder name.
cpu/mips_pic32mz/Makefile.include
Outdated
| @@ -0,0 +1,69 @@ | |||
| ifndef MIPS_ELF_ROOT | |||
There was a problem hiding this comment.
IIRC this file looks a lot like cpu/mips32r2_common/Makefile.include. Is it possible to share similarities?
|
@kaspar030 Should be easy to address these issues. Can you remove the "waiting for other PR tag" now the common mips code is merged. Ta. |
a13e366 to
1c827f3
Compare
|
@kaspar030 If your happy with the copyright changes I'll squash those down. |
|
@kaspar030 happy for me to squash these ? |
|
Rebased, Squashed, Dependants merged, 3 ticks, time to merge I think ;-) |
|
I see an ACK and three greens. |
|
Yes, might as well do this all in one place instead of holding this up.
…On 03/30/17 08:14, Joakim Nohlgård wrote:
I see an ACK and three greens.
@neiljay <https://github.com/neiljay> is you intent to refactor the
ldscripts in a follow up? (referring to #6092 (comment)
<#6092 (comment)>)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6092 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AUEU6s5OqU3DLiOsg0BUXEii4tqD6NPWks5rq1ZngaJpZM4KtZ6Y>.
|
|
Thanks all !
…On 03/30/17 08:16, Joakim Nohlgård wrote:
Merged #6092 <#6092>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6092 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AUEU6kcSYlHwDR_aYOdWbK-n8v9FT2okks5rq1a-gaJpZM4KtZ6Y>.
|
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
Note: in contrast to mips-malta, these boards are still available for purchase.
This means that if the issued listed below were to be fixed (and the boards
maintained by a person versed in the architecture) then adding them back
would be a valid possibility.
The pic32-clicker and pic32-wifire have severe issues affecting their usability,
maintainability and have no maintainer.
1. Usability
============
I doubt the current implementation of these board can be use for any serious
development.
This is a problem with MIPS-RIOT integration in general and was explained in the
PR removing mips-malta:
> a. Makes development & debugging way harder.
> b. It is impossible to run interactive tests.
> b.1. Constrains the rest of the platforms by providing an incentive to not
> make tests interactive.
> c. The lack of UART is a witness to the poor quality of the port.
This alone should have been enough reson not to merge this boards in the first place.
pic32-wifire is the least worse. At least it can be flashed from Linux, though it
is not an easy task. From dist/tools/pic32prog/doc.md
>It will require flashing a specific firmware on the PICkit3.
> As this can only be done from a Windows computer, that not many Linux users
> have, the following steps explain how to setup a Windows VirtualBox virtual
> machine and flash the PICkit3 from it.
>
> Informations come from this comment
>
> RIOT-OS#6092 (comment)
pic32-clicker HAS NO FLASHER and requires one to use MPLAB.
2. No maintainer
================
There is no (active) RIOT maintainer with deep knowledge of the boards and
platform. A quick search through the issues and PRs shows this.
3. Maintainability
==================
As a consequence of (1) and (2) many tests are not run in these boards. At the
same time, RIOT maintainers - especially those working on the build system - still
have to modify and migrate mips-foo boards.
The rest of the arguments here are the same as presented with the mips-malta
removal.
Note: in contrast to mips-malta, these boards are still available for purchase.
This means that if the issued listed below were to be fixed (and the boards
maintained by a person versed in the architecture) then adding them back
would be a valid possibility.
The pic32-clicker and pic32-wifire have severe issues affecting their usability,
maintainability and have no maintainer.
1. Usability
============
I doubt the current implementation of these board can be use for any serious
development.
This is a problem with MIPS-RIOT integration in general and was explained in the
PR removing mips-malta:
> a. Makes development & debugging way harder.
> b. It is impossible to run interactive tests.
> b.1. Constrains the rest of the platforms by providing an incentive to not
> make tests interactive.
> c. The lack of UART is a witness to the poor quality of the port.
This alone should have been enough reson not to merge this boards in the first place.
pic32-wifire is the least worse. At least it can be flashed from Linux, though it
is not an easy task. From dist/tools/pic32prog/doc.md
>It will require flashing a specific firmware on the PICkit3.
> As this can only be done from a Windows computer, that not many Linux users
> have, the following steps explain how to setup a Windows VirtualBox virtual
> machine and flash the PICkit3 from it.
>
> Informations come from this comment
>
> RIOT-OS#6092 (comment)
pic32-clicker HAS NO FLASHER and requires one to use MPLAB.
2. No maintainer
================
There is no (active) RIOT maintainer with deep knowledge of the boards and
platform. A quick search through the issues and PRs shows this.
3. Maintainability
==================
As a consequence of (1) and (2) many tests are not run in these boards. At the
same time, RIOT maintainers - especially those working on the build system - still
have to modify and migrate mips-foo boards.
The rest of the arguments here are the same as presented with the mips-malta
removal.
Note: in contrast to mips-malta, these boards are still available for purchase.
This means that if the issued listed below were to be fixed (and the boards
maintained by a person versed in the architecture) then adding them back
would be a valid possibility.
The pic32-clicker and pic32-wifire have severe issues affecting their usability,
maintainability and have no maintainer.
1. Usability
============
I doubt the current implementation of these board can be use for any serious
development.
This is a problem with MIPS-RIOT integration in general and was explained in the
PR removing mips-malta:
> a. Makes development & debugging way harder.
> b. It is impossible to run interactive tests.
> b.1. Constrains the rest of the platforms by providing an incentive to not
> make tests interactive.
> c. The lack of UART is a witness to the poor quality of the port.
This alone should have been enough reson not to merge this boards in the first place.
pic32-wifire is the least worse. At least it can be flashed from Linux, though it
is not an easy task. From dist/tools/pic32prog/doc.md
>It will require flashing a specific firmware on the PICkit3.
> As this can only be done from a Windows computer, that not many Linux users
> have, the following steps explain how to setup a Windows VirtualBox virtual
> machine and flash the PICkit3 from it.
>
> Informations come from this comment
>
> RIOT-OS#6092 (comment)
pic32-clicker HAS NO FLASHER and requires one to use MPLAB.
2. No maintainer
================
There is no (active) RIOT maintainer with deep knowledge of the boards and
platform. A quick search through the issues and PRs shows this.
3. Maintainability
==================
As a consequence of (1) and (2) many tests are not run in these boards. At the
same time, RIOT maintainers - especially those working on the build system - still
have to modify and migrate mips-foo boards.
The rest of the arguments here are the same as presented with the mips-malta
removal.
Define a RIOT_PIC32PROG to allow setting 'PIC32PROG' globally from environment. https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
Define a RIOT_PIC32PROG to allow setting 'PIC32PROG' globally from environment. https://github.com/sergev/pic32prog For PICkit3 it requires having it with scripting mode firware. Source ------ RIOT-OS#6092 (comment)
This PR is dependant on #6060 and #6066.Add support for PIC32 MX devices which use a MIPS M4K core.
This PR adds basic support for Microchip PIC32MX devices, including
bootstrapping the device, the build system produces a hex image loadable via
MPLAB-IPE. It has been tested on a MikroE Clicker board.
NOTE: This port requires the use of the GCC based MIPS Codescape SDK toolchain
available here:
https://community.imgtec.com/developers/mips/tools/codescape-mips-sdk/download-codescape-mips-sdk-essentials/
You cannot use Microchip's MPLAB / Harmony tools to build this port.
The port has been tested with the following examples:
hello-world
ipc_pingpong
timer_periodic_wakeup
riot_and_cpp
Note this is a re-work of #5885 with review comments addressed but now broken down into 3 separate PR's of which this is the third (and final).