Problems with AVR-IoT WG board

Go To Last Post
53 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I was trying some examples using MPLAB X IDE but thing went wrong! I tried an example from Youtube Microchip channel and when I clicked "Debug Main Project" the code got uploaded onto the board and it was working but then, when I tried to get back the Sensor Node code that I've downloaded from 1st item here and compilation returned an whole bunch of errors.

 

I think we should have some kind of thread for troubleshooting for the IDE's used. This might well be just some configuration problem or so! 

 

Topic split and moved to "general wireless", if not the right forum someone can move it - JS

Last Edited: Fri. Jan 4, 2019 - 05:49 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What is the error you are getting?

 

Regards,

Charles

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

charla wrote:

What is the error you are getting?

 

Regards,

Charles

 

It's a little bit confusing but I'll try to explain.

When I first tried to connect the device, while I was following instructions I saw a link to Github to update the firmware to the latest version. I followed it and used the .hex file from there and when I drag & drop it onto the device, all LEDs went OFF and no longer could make the device to work.

 

Then, the only way I found to get the device back was to download some other .hex file from Microchip site, that I presume to be the default Sensor Node code, and upload it onto the device. But even like this, I have to do this procedure several times until the device can connect to my home wireless again.

 

And at this point, after uploading both .hex files several times, I can't be sure if I have the latest firmware versions of both files or not, namely, the one from Github! I have opened an issue in Github site but I think I still haven't any reply there!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You could look at the examples provided in START for AVR-IoT WG  http://start.atmel.com/#examples...

 

Regards,

Charles

Last Edited: Thu. Dec 27, 2018 - 04:55 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

charla wrote:

You could look at the examples provided in START for AVR-IoT WG  http://start.atmel.com/#examples/AVRIoTWG

 

Regards,

Charles

Already did.
I'm using MPLAB X IDE but also there I'm having issues because it complains about #include files not being present. It might be just a matter of configuration but I'm completely blind to MPLAB X IDE. Never worked with it and have no idea how to fix these errors. I have XC8 installed that was installed along with MPLAB X IDE if I'm not mistaken.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Did you check with AVR-GCC?

 

For XC8 you might have to pass the Miscellaneous flags for Compiler from project properties in MPLAB X

 

You will see what miscellaneous flags to pass to compiler available in START 

 

 

Regards,

Charles

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When importing an .atzip file, what should I choose at this window:

 

And for the compileer, this is what I have:

 

 

For my XC8 Global options, I have this:

 

 

Will replace with all those options from Atmel Start and check the result.

 

 

And finally, after adding those options, if I try to "Run the Main project" option, the green left arrow, I get this window:

 

Last Edited: Thu. Dec 27, 2018 - 07:37 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

1) Download latest MPLAB X from https://www.microchip.com/mplab/...

2) Download latest AVR GCC compiler from https://www.microchip.com/mplab/...

3) Import Atmel START project from http://start.atmel.com/#examples...

3) On the select Tool page, the AVR IoT board should list as nEDBG with a serial number select that if you have the board connected to the machine else Simulator.

 

4) In the compiler page select AVR (latest compiler)

5) Finish Project creation.

 

Build and program with MPLAB X.

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have done all that.

 

My avr-gcc version is way different, though.