Replies to This Discussion

Permalink Reply by William Premerlani on August 10, 2009 at 3:29am

Hi Dev,

If verification works, everything is ok. Go ahead and solder the headers, if you want. I doubt that Aaron will want to swap the UAVBoard with you, it is clear that the problem is with the ICD2. In any case, Sparkfun does not salvage any UAVBoards that are returned to them, so it does not make any difference.

It is still a good idea to contact Aaron, I am glad that you are going to do that. He will probably want to swap just the ICD2 with you, but obviously he cannot do that until Sparkfun receives a shipment of ICD2s from Olimex.

Best regards,
Bill

• ▶ Reply

Permalink Reply by Sam on August 10, 2009 at 5:56am

I figure it’s worth noting that I also have been unsuccessful in connecting the UAV DevBoard to the ICD2 in MPLAB v8.x.
I have E-mailed Spark fun and my understanding is that they are waiting on shipment of the new ICD2’s. However no amount of playing with the files would allow me to compile any of the code (test, matrix nav, etc…) in MPLAB v7.5.
FYI v8.x didn’t connect, but v7.5 did, so it seems I’m having the same problems as everyone else. Anyway, I’m going to wait until the shipment arrives and query if I can exchange the board.

Sam.

• ▶ Reply

Permalink Reply by William Premerlani on August 10, 2009 at 6:24am

Hi Sam,

You should be able to compile the code with MPLAB v7.5, without an ICD2 connected. However, you will have to rebuild the projects, because MPLAB v7.5 does not recognize v8.x project files. Here is what you need to do:

1. Make sure that you have the Microchip C compiler. If not, download the free evaluation copy from Microchip.

2. Find the files p30f4011.gld and libdsp-coff.a in the Microchip libraries, and copy them into your project directory. I am going to try to attach them here, but sometimes I have trouble uploading them.

3. Run the project creation wizard under MPLAB v7.5, and include all of the .c and .h files in the released firmware, plus the p30f4011.gld and libdsp-coff.a file.

4. Edit the file options.h and add a line at the beginning of the file, either #define ConfigRed, or #define ConfigGreen, depending on whether you have a red board or a green board.

Best regards,
Bill

Attachments:

• libdsp-coff.a, 141 KB
• p30f4011.gld, 49 KB

• ▶ Reply

Permalink Reply by Ron Johnson on September 5, 2009 at 4:42pm

I have an ICD2 made by Microchip and have the same issue with a dsPIC30F4011 40 pin dip. I had MPLAB 8.33 and was able to program a dsPIC30F6014, PIC18F87J50 and a PIC18LF4620 without issue. I spent 8 hours tearing my board apart assuming I had made a mistake.

I installed MPLAB 7.5, copied the ICD10010508.hex file, then installed MPLAB 8.36. It still didn't work. I downloaded the ICD10010508.hex file, hit cancel when it tried to upgrade immediately after and then was able to program my part with MPLAB8.36.

I don't think this bug is necessarily limited to clones.

• ▶ Reply

Permalink Reply by William Premerlani on September 6, 2009 at 4:18am

Ron,

Very interesting. Since you have a Microchip ICD2, they should be willing to help you track this down.

Regarding the Olimex clone of the ICD2, Olimex investigated this issue and claims they figured out what the problem is. They have changed the design of their ICD2 by adding a 330 ohm resistor as a load on the MCLR reset line. Apparently the dsPIC30F4011 does not draw enough current for the ICD2 to stabilize the high voltage supply on that line to within the tolerance demanded by the latest releases of MPLAB.

John_Mac has been doing some tests on the new Olimex ICD2. He was having the same problem you are talking about with the previous Olimex ICD2. So far, the new ICD2 has been working fine for John with the latest version of MPLAB, so maybe Olimex has indeed figured out this bug.

Best regards,
Bill

• ▶ Reply

Permalink Reply by Belli Button on September 6, 2009 at 10:36am

Hi All,

FWIW, I have Microchip ICD2 and it programs fine under 8.30 and 8.36 and probably 7.5 too. I think what is happening is when you start MPLab, it will give you this message. JUST IGNORE IT!

I've attached a screen shot of a typical start up screen with MPLab, this is perfectly normal.

Cheers,
Greg

Attachments:

• MPLab.JPG, 79 KB

• ▶ Reply

Permalink Reply by Sandra B on October 11, 2009 at 1:14pm

Hello ,

Just for information. ( the same problem append to me now )

I have a green board and never had problem to program it with my original ICD3 and a custom made cable.

But since I tryed to program an other board with a dspic33 on it .
Nothing is working any mode.

It can not read the device ID anymore.
I can't program any devices anymore .
except the dsPIC33 on the explorer board from microchip with original cable delivered with the ICD3.

did somthing fried in my ICD3 ??

Just a adding a layer to the mistery :-)

regards

Sandra

• ▶ Reply

Permalink Reply by William Premerlani on October 11, 2009 at 4:00pm

Sandra,

I am not sure if I undestand what your situation is. Are you saying that you can no longer program the green board? If so, I might be able to help you. Are you saying that you can no longer program a dsPIC33? If so, I do not have any experience with the dsPIC33, I cannot help you there.

I do not think you have fried your ICD3. If there is a problem with the ICD3, it may be with the operating system that gets downloaded into it by MPLAB when you change versions of MPLAB or different dsPICs.

I assume that you purchased your ICD3 from Microchip. In that case, they should be able to help you.

If you are having trouble programming the green board with your ICD3, make sure that you have the correct processor selected, perhaps MPLAB is still set to the dsPIC33.

If that is not the case, you could try reloading the operating system into the ICD3. I do not have an ICD3, so I cannot tell you how to do that, but there is probably an option on the ICD3 menu to reload the ICD3 operating system.

Best regards,
Bill

• ▶ Reply

Permalink Reply by Sandra B on October 13, 2009 at 2:05am

Hi, bill thanks for the fast reply .

May, be you are right my problem is quite different from those with the ICD2.

I went to a friend yesterday, and i could program my GreenBoard with a his ICD2 on iDE 8.36

Looking at the microchip forum . There is a kind of bug with the icd3 and the new version of the IDE 8.33 and 8.36.

It looks like it can't upgarde the firmware of the iCD3 for different Dspics any more.

So for now i can olny work with my exporer 16 board .

Thanks

Sandra

• ▶ Reply

Permalink Reply by Khalid Saeed on November 16, 2009 at 12:04am

Hey gang, I'm trying to "make" the project and I keep getting this error. Any ideas? I'm stymied! Thanks!

Make: The target "Z:\AileronAssistRv8b\aileronCntrl.o" is out of date.
Executing: "C:\Program Files\Microchip\MPLAB C30\bin\pic30-gcc.exe" -mcpu=30F4011 -x c -c "aileronCntrl.c" -o"aileronCntrl.o" -g -Wall
Microchip MPLAB C30 License Manager Version v3_20 (Build Date Aug 24 2009).
Copyright (c) 2008 Microchip Technology Inc. All rights reserved.
The installed license is invalid for this device.
pic30-coff-cc1.exe: error: Your license is invalid for the device selected.
Select an appropriate device, or acquire the correct license.
Visit http://www.microchip.com/ to purchase a new key.
Halting build on first failure as requested.
----------------------------------------------------------------------
Release build of project `Z:\AileronAssistRv8b\AileronAssistRed.mcp' failed.
Language tool versions: pic30-as.exe v3.20, pic30-gcc.exe v3.20, pic30-ld.exe v3.20, pic30-ar.exe v3.20
Mon Nov 16 01:57:43 2009
----------------------------------------------------------------------
BUILD FAILED

• ▶ Reply

Permalink Reply by William Premerlani on November 16, 2009 at 8:03am

Khalid,

This is the first time I've seen this error message, so I am not sure.

What I think it might be is that you downloaded the purchased version of the compiler rather than the evaluation version. For the purchased version you would need to buy a license, so you probably don't want to do that.

You do not need the purchased version, the free evaluation version will work just fine. You get a "temporary" free license to use it, but once it expires, you can continue to use it anyway. Its just that certain compiler options, which we do not use, will no longer work, and you will get a warning.

Bill

• ▶ Reply

Permalink Reply by William Premerlani on November 16, 2009 at 8:14am

Khalid,

Here is the address of the evaluation version of the compiler. You will need to create an account to download it:

https://www.microchip.com/wwwregister/default.aspx?ReturnURL=http:/...

Bill

• ▶ Reply

• ‹ Previous
• 1
• 2
• 3
• 4
• 5
• Next ›
• Page