Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
I purchased an icd2 clone with an RS232 connection to my PC. It has never worked correctly. I have read the forum about all the problems others have had. I have tried most of the suggestions to get it going. No joy. Now I want to go back to basic principles.
How does the boot loader actually work? It isn't very long. I can disassemble it and reverse engineer it. I can also compare the disassembled code to other non-icd2 boot loaders to gain a better understanding.
Before I do that I thought I would ask if someone has already done the work or the original author would share his/her code and documentation.
Here is the kind of questions that make me go mmm...
Issues:
RS232: set baud rate; hardware hand shake; tx/rx character buffering; interface definition to rest of boot loader code;
Memory: write control for 877 and 877A parts.
Thread of control: once an OS has been boot loaded how is the OS called? is the bootloader RS232 driver used by the OS? Does the OS use any resources of the boot loader?
As you can see I have jillions of questions. I am hoping someone with the source code can provide many of the answers.
To vaughanatworld
I some ask
1.you use MPLAB version 7.30 with ICD-Clone ( 18F877A or 18F877 ) ?
2.It is work good with DsPicxxx ?
3. you can post shema + pcb + bootloader run MPLAB 7.30 ?
Thank you
1. I have tried both 876 and 876A and a variety of of hex boot loaders published on EDA and from MPLAB
2. I have not done any work with DsPicxxx. My problems come before selecting any particular target PIC.
3. The hardware design is quite simple and matches closely the work already published on EDA.
To move forward I have ordered up a genuine ICD2 directly from Microchip. Then I can use the USB port.
Also I am trying to put together a Windows 98 system. The serial port device drivers for this OS are less sophisticated than those for XP and Win2000.
This problem bugs me more than anything else. I have moved from the place of I just want it to work. Now I want to know why it doesn't work.
I want to build this shematic for icd2 but .. i don't know the configuration for J2 TARGET conector ... and nowhere is writen this ....
I'll appreciate if someone could tell me this configuration. I discover some pins but not all pins
1 - MCLR
2 - Vcc
3 - GND
4 - Data
5 - Clock
6 - ????
Hi everybody!
I read this post from beginnig, and after that I decide to make my own ICD2. After a week of working, I finnished and I have a working ICD2. I will comeback with details an pictures soon; and I hope that details to help other people.
Thank everybody for a very helpful hints and ideeas!
Ok ... i make my board ... it's working fron first run .... it's ok ....
Only one change .... i put in place of R3 - 2K2 a variable rezistance 2K2 to make the fine adjust to have the right voltage on Vdd ...
Hello. I build a IC2. programs the target pic very well and run after programing.
but not work in debug mode,
when i connect icd2 and press DEBUG PROGRAM , appear this message:
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
Target Device PIC12F629 found, revision = Rev 0x10
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Running Target
Entering Debug Mode
...Programming GOTO 0x00 command ICD0083: Debug: Unable to enter debug mode. Please double click this message for more information.
ICD0069: Debug: Unable to run target Entering Debug Mode
...Programming GOTO 0x00 command
MPLAB ICD 2 Ready
i don't test with others PIC, but test with 4 differents PIC12F629.
Help me pleace.
Sorry, but mi english is very bad.
Hello. I build a IC2. programs the target pic very well and run after programing.
but not work in debug mode,
when i connect icd2 and press DEBUG PROGRAM , appear this message:
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to MPLAB ICD 2
Target Device PIC12F629 found, revision = Rev 0x10
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Running Target
Entering Debug Mode
...Programming GOTO 0x00 command ICD0083: Debug: Unable to enter debug mode. Please double click this message for more information.
ICD0069: Debug: Unable to run target Entering Debug Mode
...Programming GOTO 0x00 command
MPLAB ICD 2 Ready
i don't test with others PIC, but test with 4 differents PIC12F629.
Help me pleace.
Sorry, but mi english is very bad.
I build a icd2.
It programs the target pic very well,when i release the reset , taget runs.
but after i using it in debug mode, i connect icd2, it's ok,and i press the menu , debugger->program
the message:
MPLAB ICD 2 Ready
Connecting to MPLAB ICD 2
...Connected
Setting Vdd source to target
Target Device PIC16F876A found, revision = b4
...Reading ICD Product ID
Running ICD Self Test
...Passed
MPLAB ICD 2 Ready
Programming Target...
...Erasing Part
...Programming Program Memory (0x0 - 0x7FF)
...Loading DebugExecutive
...Programming DebugExecutive
...Programming Debug Vector
Verifying...
...Program Memory
...Debug Executive
...Debug Vector
...Verify Succeeded
Programming Configuration Bits
.. Config Memory
Verifying configuration memory...
...Verify Succeeded
Connecting to debug executive
ICD0083: Target not in debug mode, unable to perform operation
MPLAB ICD 2 Ready
The programmer and debugger are two separate functions for MPLAB 7.40 (and other versions).
You can only run ONE at a time.
The debugger requires DEBUG code as well as your code in the target.
If you change function from Programmer to Debugger, MPLAB buffer still contains the image from Programmer - without the necessary Debug code.
Your project will need rebuilding and MPLAB creates a new image and includes the Debug code.
Program target with new image and run.
If you change from Debugger to Programmer you will only need to reprogram the target - no rebuild is necessary - Programmer ignores Debug code - MPLAB bug.
Note: VERIFY after change from Debug to Program without a reprogram is invalid
- I have discussed this at length and othe bugs with Mchip Techies - it is under review!
The simplest way is to always rebuild your project before you program.
Tanks wjr1955 and polymath. but today i test the ICD2 with a PIC16F628A and had the same problem. ??? i made the steps indicates in the post: first rebuild the projet in ICD mode, reprogram de target and them RUN DEGUB.
i don't understand for what i have use an adapters for debug?
the program don't need adapters, this work very well.
i need a tutorial for this.
the ICD2 original say support debug for 12F629 and 16F628A.
Help!!! pleace.
sorry and be patience with mi english, is very bad. i speak spanish.
best regards.
This applies to the 16F628A
If you want to try DEBUG use 16F877A - it has the DEBUG hardware built-in
Read the link/.PDF above for list of PICs that require special ICD chip or read PIC data sheet.
It would save you time if you read the links that are posted.
MPLAB supports DEBUG in these models but you will need PIC16F628A-ICD silicon
mounted on a Header that has a Microchip Standard RJ12 socket - see .PDF
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
