Page 1 of 2

chipKIT-core v1.3.0 and v1.3.1 released

Posted: Wed Sep 07, 2016 1:53 am
by EmbeddedMan
The chipKIT development team is very proud to announce two new versions of chipKIT-core.

Both versions are available through the Arduino IDE Board Manager, and as separately installable zip files (from here :

Release notes on what has changed can be found here : ... ease_notes

For instructions on how to use and install chipKIT-core, please see

Re: chipKIT-core v1.3.0 and v1.3.1 released

Posted: Fri Oct 21, 2016 6:17 am
by fleatech
I noted the following...

Version 1.3.0 (August 30, 2016)

Major changes/fixes
#246 Update pulseIn() to support different CPU clock rates
#253 Improved PWM - new functions analogWriteFrequency(Hz) and analogWriteResolution(bits), maintains duty cycle of PWM when settings are changed.

Are there any notes on the use of these new and update functions ???

Re: chipKIT-core v1.3.0 and v1.3.1 released

Posted: Fri Oct 21, 2016 10:16 am
by majenko
pulseIn() looks no different to how it always did - it just behaves properly now.

analogWriteResolution() is a standard Arduino function and is documented here: ... Resolution

analogWriteFrequency() takes one parameter - the carrier frequency to run PWM at.

Both the latter two are shown in an example sketch AnalogWriteFrequencyAndResolution which can be found in the "Analog" section of "Examples" ("Examples" is a dummy library - find it in the list of library examples).

Re: chipKIT-core v1.3.0 and v1.3.1 released

Posted: Fri Nov 11, 2016 10:55 am
by C D Frost
I am using the current release with the Arduino IDE to program a Clicker2 for PIC32MX - this works well with MacOS (with a MacBook Pro) but does not work well with the Linux machine we normally use to programme various boards. The error occurs in the final download to the board once it is ready to load.

Re: chipKIT-core v1.3.0 and v1.3.1 released

Posted: Fri Nov 11, 2016 12:39 pm
by majenko
And what is the error you get?

Re: chipKIT-core v1.3.0 and v1.3.1 released

Posted: Fri Nov 11, 2016 6:19 pm
by C D Frost

Below is a copy of the output of the IDE... in this case I was trying the simple 'Blink' example...

Sketch uses 6,504 bytes (1%) of program storage space. Maximum is 500,000 bytes.
Global variables use 2,888 bytes of dynamic memory.
Programmer for Microchip PIC32 microcontrollers, Version 2.1.24
Copyright: (C) 2011-2015 Serge Vakulenko

*** Enter programming mode now. ***

UHB bootloader not found: vid=1234, pid=0001, serial=(none)

No target found.
An error occurred while uploading the sketch

Re: chipKIT-core v1.3.0 and v1.3.1 released

Posted: Fri Nov 11, 2016 9:12 pm
by majenko
Does your user have access to that USB device? It's a common issue in Linux that by default a user can't talk to just any USB devices.

The "proper" way of granting access is through udev.

As root, create a file /etc/udev/rules.d/50-clicker.rules and in it put:

Code: Select all

ATTRS{idVendor}=="1234", ATTRS{idProduct}=="0001", MODE="0666", GROUP="plugdev"
Then restart UDEV:

Code: Select all

$ sudo /etc/init.d/udev restart
Now it should start working...

Re: chipKIT-core v1.3.0 and v1.3.1 released

Posted: Mon Nov 14, 2016 1:07 pm
by C D Frost

Thanks this seems to work! I had (wrongly) assumed that as the USB port had been used for various other boards that it would work for the Clicker 2, but clearly it required a bit more adjustment to the Linux system. Many thanks.

Re: chipKIT-core v1.3.0 and v1.3.1 released

Posted: Mon Nov 14, 2016 2:39 pm
by majenko
Most USB boards present a virtual serial port, and being in the "dialout" group gives you access to those. However the clicker2 uses a HID bootloader instead, so a device node /dev/ttyACMx isn't created. Since your existing permissions are keyed to the group that node is in, if there isn't one then your existing permissions are no longer used - you need to create a different set of permissions that work in a different way - and that is what udev is now doing for you.

Your existing permissions are still valid for accessing a USB serial port created by your sketch, of course.

Re: chipKIT-core v1.3.0 and v1.3.1 released

Posted: Thu Dec 15, 2016 12:30 am
by rasmadrak
I've been using MPIDE 0023 for ages and thought I'd upgrade to the new fancy Arduino 1.6.13 with 1.3.1 chipKIT core. Wooh yeah!
I haven't updated my coding environment in years, but my WinXP laptop is running on it's final prayers now and MPIDE 0023 is no longer supported, and is considered "a threat", in OSX. I have an interesting problem to report. I must say, I'm not sure where exactly the problem is - and bear with me - but:

I've gotten my old code to compile after a few tweaks (still requires disabling DSPI2 and DSPI3 on my MAX32 board def though).
But the problem is that Serial2 doesn't seem to work properly. It does work somewhat, but the communication "stutters", in lack of a better word. I have a Arduino Mega2560 connected to it (on 500 000 baud ) that handles a light matrix on its end, and the lights go haywire. When sending proper data over the interface it does get there, but it's like trying to read a book in darkness while someone flicks the light on and off all the time.

These are facts:
* I've changed from WinXP MPIDE 0023 to Mac OSX 10.10.5 Arduino 1.6.13 + core 1.3.1. (big jump!)
* A simple empty sketch causes Serial2 to "glitch"/"stutter", so it's not my code - it's in the core.
* There has been trouble with DSPI (not used or linked at the moment though) and hardware serials before.
* Serial(0) and Serial3 are confirmed to work reliably with computer serial com and serial com with a wavTrigger. Unsure about Serial1.

I realise this might be stupid questions, but nonetheless important;
1) What has changed when it comes to hardware serials from MPIDE to the new core?
2) Is the core 100% compatible with Arduino 1.6.x, or at least the same functionality as MPIDE 0023?
3) Are custom baud rates unsupported and could this be the problem? (It's a bit of an inconvenient process to update the Mega)
4) Any tricks, tips or things I can try to help verify/resolve this?