blueroomelectronics
Advanced Member level 5
- Joined
- Sep 17, 2006
- Messages
- 1,681
- Helped
- 180
- Reputation
- 358
- Reaction score
- 77
- Trophy points
- 1,328
- Location
- Toronto, Canada
- Activity points
- 8,696
blueroomelectronics said:Does your 16F887A have the oscillator configured correctly? You must have a running clock to use the debugger.
alunaro said:In previous posts, somebody posted a link to microchip forums which has information about it (i'll post it later because i haven't the info here).
Anyway you have to set your code propertly in order to debug.
When arrive at home I'll post all i know and a working example with 16f877a (blinks a led).
Cu late.
alunaro said:In MPLAB, select ICD2 as programmer, load your project, build, and download to PIC. Set a breakpoint where you want and just run.
blueroomelectronics said:Make sure the oscillator is set to HS
ad_tech said:elec_gu said:To ad_tech:
First of all. Thank you for your answer.
I'm going to scope data and clock lines in order to measure timing. I'll do some comparison 5V vs 3.3v.
Tanks again for your answer. For me this is a sad history. First, I tried to do a USB ICD2 by myself following this page, but it was over my capabilities (double side board etc). Then I bought one by eBay. The seller ad stated it was 3.3v capable, but as far as I can say, it isn't. My following step should be to buy Microchip original one. As you can see, a long, stupid and expensive way of doing things
To : elec_gu
Your story is troubling me.
I ordered some PIC24F and PIC24H a couple of days back.
I guess I may run into problems as you did.
This is just a dumb question. Are you connecting AVDD and AVSS as described in page 46 footnotes 1 and 2 of the PIC24F programming specifications (DS39768B)?
Is there any one out there who has worked with PIC24F/H and ICD2 clones successfully ?
I just made a side by side comparison of the programming timing requirements for PIC18F2xx and PIC24Fx and the results are very interesting to say the least.
To be quick about it, I will only mention 3 parameters of the PGC line.
Clock low, Clock high and Clock period
PIC 18F2x @ 2V 400 ns 400 ns 1000 nS
PIC 18F2x @ 5V 40 ns 40 ns 100 ns
PIC 24Fxx @ 3.3V 40 ns 40 ns 100 ns
This means that the ICD2 OS for PIC18F2x needs to adjust it's timings according to target VDD.
As you can see, clock timing for PIC18 @ 5V and PIC24F @3.3V is the same, but while programming PIC24F, the transmitting buffer is being supplied @ 3.3V which makes it a slower device while the timing requirements remain the same.
I'm guessing that, due to the larger memory of the 24F chips, MICROCHIP has probably ' squeezed ' as much as possible the programming timings to speed up matters.
This may also account for your problems with 24F and not with other devices.
To potyo:
You are right about programming PIC16LFx at low voltage. It can be done.
But the fact is that both buffers and PIC16LFx become slower at low voltages, and ICD2 firmware takes that into account when generating clock and data signals.
The problem is that PIC24 is programmed at a fixed voltage,(according to datasheet) so there is no need to ' adjust timings '.
At 3.3V 74HC devices might just be a tiny bit too slow.
Is there any proud owner of an original ICD2 on the house that could inform us about what type of buffers MICROCHIP ICD2 uses ?
A final note before I go:
As you can all see I joined this forum recently.
It took me about a week to read (several times ) all the messages posted here and one thing became immediately obvious to me.
Less than half a dozen guys really gave their best to put this thing to work.
I imagine they have invested several hundred hours on this with no gain on sight, just that nice feeling of self accomplishment.
To them I would like to leave here my public and deepest appreciation and a ' warm handshake '
Augusto Duro
elec_gu said:To ad_tech, potyo and paperbat1,
Hello again.
Good news from here.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?