chipKIT® Development Platform

Inspired by Arduino™

Uecide compiler warning: -std=c++0x or -std=gnu++0x

Created Sat, 29 Mar 2014 21:36:04 +0000 by tcsaba101

tcsaba101

Sat, 29 Mar 2014 21:36:04 +0000

What I should do to avoid this warning? Thanks, Csaba

majenko

Sat, 29 Mar 2014 21:42:13 +0000

Which UECIDE version are you using?

Which chipKIT board are you compiling for?

majenko

Sat, 29 Mar 2014 21:44:22 +0000

Also, you could try adding in the missing = from the assignment...

tcsaba101

Sat, 29 Mar 2014 22:08:43 +0000

Version: v0.8-1a chipKIT UNO32

How can I add "from the assignment"?

majenko

Sat, 29 Mar 2014 22:18:00 +0000

Version: v0.8-1a chipKIT UNO32 How can I add "from the assignment"?

int config_Pars[CONFIG_PAR_NO] {

should read:

int config_Pars[CONFIG_PAR_NO] = {

And can I suggest upgrading to 0.8.4d and upgrading all your plugins? There's some implrtant fixes in the newer versions.

tcsaba101

Sun, 30 Mar 2014 14:54:53 +0000

Thanks!

The "=" sign was missed in the assignment.

As it is clearly in the referenece:

int myInts[6]; int myPins[] = {2, 4, 8, 3, 6}; int mySensVals[6] = {2, 4, -8, 3, 2}; char message[6] = "hello";

I never used array initialization before.

tcsaba101

Sun, 30 Mar 2014 15:22:56 +0000

I have upgraded the IDE placing in the same dir where the previous was.

Pls. have a look what silly mistake I have done again. The file is in the library, as it was without problem before the upgrade. The other messages I don't have a clue what to do with.

Should have been installed in a new directory?

Thanks

majenko

Sun, 30 Mar 2014 16:28:36 +0000

The trick with dealing with errors is to start right at the top and work down - fix the first error and you'll find other errors disappearing.

From that screenshot the first error is an inability to find the file. Make sure that it's all in the right place, and that the library is in the list of libraries in the sketch menu.

tcsaba101

Sun, 30 Mar 2014 17:04:27 +0000

You are right.

The data in the libraries directory. But not listed in chipKIT library.

Rescan stucks with the message shown. The message is: (access denied)

I couldn't find the Teensy core in the Plugin Manager.

majenko

Sun, 30 Mar 2014 17:30:30 +0000

Not sure why it would be access denied. You could try removing (or moving) the old Teensy folder. I haven't got Teensy ported to the new structure for the new version yet, so it may be killing things somehow.

tcsaba101

Sun, 30 Mar 2014 17:50:42 +0000

I have removed the Teensy dir. The error message disappeared. But Sketch "Rescan Libraries" doesn't picks up the additional libraries from the library directory. All of them worked with the previous version.

majenko

Sun, 30 Mar 2014 22:17:19 +0000

I have finally got round to implementing something I have been meaning to implement for a long time - Debug console. It's now available in version 0.8.4e (Help -> Debug) - it may give some clues.

My best guess for a cure right now though is to delete your entire uecide folder (all the boards, cores, etc) and reinstall them afresh - there may be something in there that's not happy with the current version.

tcsaba101

Tue, 01 Apr 2014 10:52:22 +0000

I have reinstalled the x.1a version (what I used before) that works. If I reinstall the 1.d version, this is the same, no library detected. (Till the moment.)

I have realized first the 1.d version opened the setup location in Appdata/Local, then changed the location to Appdata/Roaming. How can I fix the Setup location at startup? If I change in the Preferences, that relocates, but at new startup it will start with the default location.

majenko

Tue, 01 Apr 2014 12:14:07 +0000

The location change was made so that all the cores, compilers, etc weren't being synced to a user's home folder on a remote server every time they logged in/out on a network. It should be first looking for a uecide folder in the original "roaming" folder, and only if it's not found it'll fall back to a local one.

For most users the actual location makes no difference at all.

tcsaba101

Tue, 01 Apr 2014 14:46:15 +0000

Understood. Now I can control the situation.

If I reinstall the 8a version, load the library dir, after setup the libraries are listed in Sketch/Library/Standard menu. It does not lists the additionals lib items under chipKit menu like in version 8e. But it works, compiling my sketch.

Then I delete the Remote/uecide dir, and reinstall the 8d or 8e version, load the library dir with the same content as above. The library lists only some default items under the chipKit menu like in 8a version. The standard list is missing therefore doesn't compile the code.

tcsaba101

Tue, 01 Apr 2014 14:49:13 +0000

The pictures forgotten.

majenko

Tue, 01 Apr 2014 14:56:42 +0000

Ah!

Ahahah!

I see what is happening here!

The "standard" library location was dropped as it was not wanted any more. You should not be using it, and you should never have been using it. It was a hangover from the old Arduino days.

Libraries go in the Libraries folder in your sketches folder (Documents/UECIDE/Libraries? I don't use Windows, so I can't remember off hand where that is...). You should never be manually adding anything into your Roaming/UECIDE folder.

tcsaba101

Tue, 01 Apr 2014 21:33:09 +0000

I have been dropped the library folder to the uecide folder with both versions (where the uescide.exe has been installed) as you suggested, never in the roaming/local folder.

If I move to the sketch folder version e still do not find it.

Is there a description how to use libraries?

majenko

Tue, 01 Apr 2014 22:56:52 +0000

Sorry, executable folder is what I meant, not the roaming folder...

The "proper" way to install a library is through the Sketch menu using a zip file of the library. That will extract it into where it should be. You might like to try doing that with a library (zip the folder up, then install it through the menu) and see exactly where it installs it to on your system.

It should be c:\Users\YourUsername\Documents\UECIDE\librraies\WhateverTheLibraryIsCalled on windows 7 - "Users" is "Documents and Settings" and "Documents" is "My Documents" on XP.

It's basically the same way as with the Arduino IDE (the NEW way, putting it in the sketch book, not the OLD way of putting it in the IDE program files), which is documented here: [url]http://arduino.cc/en/Guide/Libraries[/url]

tcsaba101

Thu, 03 Apr 2014 09:39:32 +0000

Now I have understood.

I will try.

Tell me how can I use 8a and 8e versions paralel, because 8e overwrites the 8a setup library in the Roaming dir. To chage in preferences works, but I should tell uecide as a parameter the new dir to look for the setup data.

thanks!

majenko

Thu, 03 Apr 2014 10:46:21 +0000

You could change preferences.txt in the lib folder where the executable is.

tcsaba101

Thu, 03 Apr 2014 13:02:32 +0000

Now I can control the situation. Thanks!

If I place in the library dir in the sketch dir (what is defined in the Preferences menü) the Rescan works.

Regarding to parallel using of 8a and 8e: The preferences.txt should be in the Roaming/uecide folder otherwise it opens a new empty directory. And if there is a Roaming/uecide folder, the 8e version overwrites it.

There should be a way to tell to the uecide.exe where to look for the actual preferences.txt file!

majenko

Thu, 03 Apr 2014 13:45:05 +0000

The problem is, all that kind of thing is stored in the preferences file, and it needs to know where to find that preferences file to look in it for where to find the preferences file. Bit of a catch-22 situation really.

tcsaba101

Fri, 04 Apr 2014 06:07:30 +0000

Definitely you can't tell on the same place. It could be a different file or runtime parameter. Forget it, not so important.

There is an MPLAB-X plugin, please provide a link to learn about it.

Thanks!

majenko

Fri, 04 Apr 2014 10:09:18 +0000

The MPLAB-X plugin is very broken. I am in the process of overhauling it, but it won't be working again until the new version of the chipKIT core is properly ready and I have re-written the plugin to use the new style core system.

I have started introducing command line parameters though, so I may add a --config=blahblah parameter (the latest version has a --debug parameter that opens the debug console right at the start)

majenko

Fri, 04 Apr 2014 19:10:24 +0000

Good news!

Version 0.8.4g now has a command line parameter:

--datadir="C:\Path to\the place\you\want\the\files\and\preferences\to\be"

Download the ZIP file of the latest version, extract it, and copy the uecide-0.8.4g folder somewhere convenient (such as the existing C:\Program Files (x86)\Majenko Technologies), then go into it. Create a shortcut on your desktop to the uecide.exe (I right-click-and-drag then select "Create Shortcut"). Edit the shortcut and add

--datadir="C:\Users\MyUsername\UECIDE Settings\0.8.4g"

.. or something similar, to the end of the Target entry (after any " with a space)

You can then run the shortcut and you have a completely fresh and separate installation which won't interfere with any other installation.

tcsaba101

Mon, 07 Apr 2014 17:06:26 +0000

Thanks!

I hope this function will be useful for others too. Especially when migrating from one version to the other, if there is a bug (as it was the case now) the development can be continued with the previous version still the bugs are fixed in the new. I will try and confirm the result.

I was exploring the MPLABX + XC32 on the weekend with MicrostickII & Microstickplus boards. The LEDs are blinking based on Timer1 interrupt.

I have realized how nice and simple is the Arduino/Mpide/Uecide world. Clear documentation (relatively), dozens of examples, busy forums, etc. MPLABX&XC32 is the opposite. I haven't get to the point where I need the device libraries, but as I see, in the library selection there is also a serious contrast between the two systems.

The XC32 IDE and compiler is very confortable, but the lack of detailed documentation and detailed examples requires much more efforts. Maybe in case of bigger projects and teamwork pays back the investment.

The Simulator and HW debug is very nice. The Logic analyser was very slow in my case, I couldn't use it (or I did something wrong). I will recheck later.

Using uecide/Aurduino compiler in MPLABX would be the best for this size of projects what I do. What is the purpose of the MPLABX plugin in the uecide? Please explain.

I have found a document what explains the MPIDE integration with MPLABX. Do you think it should work also with Uecide?

I have red somewhere on a forum, this kind of integration can be done only with licenced MPLABX version. The free version doesn't have the optimizing capabilities what needs for this integration. Could you comment it before I start to sruggle with this integration?

Thanks!

The file is a 2Mb pdf, how can I upload?

majenko

Mon, 07 Apr 2014 17:21:05 +0000

What is the purpose of the MPLABX plugin in the uecide? Please explain.

When it's working again it will export your sketch out into an MPLAB-X project so you can open it directly in MPLAB-X and compile it with XC32. You will need at the very least an XC32 C++ license (which you can get a free version of) to compile. The aim is that the plugin will export everything - your sketch, any libraries used, the core API files, etc, so the MPLAB-X project becomes a completely stand-alone bundle independent of any other IDE or software. It won't work with the current version of the chipKIT core though as it relies on changes that will be in place for the newer chips in the near future.

guymc

Mon, 07 Apr 2014 23:16:35 +0000

I have red somewhere on a forum, this kind of integration can be done only with licenced MPLABX version. The free version doesn't have the optimizing capabilities what needs for this integration.

My understanding is, only a Pro compiler can successfully re-build the bootloader for certain devices. But this is not a general limitation; the free XC++ compiler (registration required) will build many sketches just fine.

Please bear with us, as we work to improve the migration path from MPIDE and UECIDE to MPLAB X. Your help in identifying issues along the way is greatly appreciated.

Cheers

tcsaba101

Thu, 10 Apr 2014 19:53:26 +0000

Code: --datadir="C:\Users\MyUsername\UECIDE Settings\0.8.4g" .. or something similar, to the end of the Target entry (after any " with a space)

It works, thanks.

Please bear with us, as we work to improve the migration path from MPIDE and UECIDE to MPLAB X. Your help in identifying issues along the way is greatly appreciated.

I try my best. I will evaluate the MPIDE MPLABX integration as I will have resources for.

Where I could find the most valuable sources in this topic?

guymc

Fri, 11 Apr 2014 21:02:03 +0000

Where I could find the most valuable sources in this topic?

Keith Vogel has posted some excellent info on how to debug sketches in MPLAB X:

http://www.chipkit.net/forum/viewtopic.php?f=19&t=2458&hilit=source+debugging

Cheers

tcsaba101

Wed, 23 Apr 2014 09:14:46 +0000

Good news!

Based on the class ADA17007 document I have debugged a Rotary Encoder example sketch in the MPLABX environment. I have edited the sketch in MPX, recompiled in MPIDE, then continue on debug without serious bugs.

I used the chipKIT PGM programmaer.

Moreover I could upload to the board at the end of debug the bootloader.

I have expected a much difficult job to do this. I was really surprised how easy was to get the debug work.

If you follow the presentation, almost everything can be accomplished. The only bug was, that MPIDE gave in the verbose list a wrong directory(!?!) identification of the xx.elf file! To set up the link in MPX you have to find the directory path on the disk. Then the recompiling works well.

Thanks, for everyone for encouraging.

The only bad, I don't like MPIDE to work with. Majenko can you tell some good news about the Uecide MPLABX integration?