Author |
Topic  |
|
spcmicro

USA
5 Posts |
Posted - 11/02/2007 : 11:50:09
|
The PIC 16F628A shows up in the device list. The device erases. I program the device and it appears to be OK. The data looks valid. The device won't run in the target board. It does nothing. I borrowed a PICStart Plus programmer and programmed the same device. The device runs in the target. I put the part back in the USB Willem programmer and it verifies.
I now re-programmed a part using the Willem USB programmer. I tried verifying the part using the PICStart Plus. Here are the messages I received from the PICStart Plus:
Field : Oscillator Expected: INTOSC: I/O on RA6/OSC2/CLKOUT, I/O on RA7/OSC1/CLKIN Received: RC: CLKOUT on RA6/OSC2/CLKOUT, RC on RA7/OSC1/CLKIN
Field : Watchdog Timer Expected: Off Received: On
Field : Power Up Timer Expected: Enabled Received: Disabled
Field : Brown Out Detect Expected: Disabled Received: Enabled
Field : Master Clear Enable Expected: Disabled Received: Enabled
Field : Low Voltage Program Expected: Disabled Received: Enabled
What is missing here. It's as if the code is programmed properly but the configuration isn't.
Any help would be greatly appreciated.
|
|
Reply #1
ZLM
    
2947 Posts |
Posted - 11/02/2007 : 14:16:40
|
The configuration word is not programmed. The Write button will only write current active buffer. Like Code, Data, and User code. The configuration word need to be programmed in the CFG window. Click the CFG button, the CFG window will be opened. After set the CFG bits, click on write button from that window. |
 |
|
Reply #2
spcmicro

USA
5 Posts |
Posted - 11/02/2007 : 15:01:32
|
Thanks ZLM. I was just playing around in that vicinity. It looks like the config data is in the HEX file but is just being ignored by the programming software.
|
 |
|
Reply #3
ZLM
    
2947 Posts |
Posted - 11/02/2007 : 18:59:40
|
This should be fixed. |
 |
|
Reply #4
spcmicro

USA
5 Posts |
Posted - 11/03/2007 : 02:35:07
|
I agree |
 |
|
Reply #5
spcmicro

USA
5 Posts |
Posted - 11/03/2007 : 08:16:45
|
If anyone from Willem is following this thread there is another problem with the PIC support. The read of the PIC doesn't include the User ID memory.
2 Bugs total:
1. When the hex file load is loaded the User ID memory should be loaded. This is for the PIC configuration data. 2. When a PIC is read using the programmer, the User ID memory should be read and displayed.
|
 |
|
Reply #6
spcmicro

USA
5 Posts |
Posted - 11/03/2007 : 09:19:39
|
In all fairness, the configuration data for the PIC can be set easily using the CFG icon. The problem is that this button and it's associated dialog are not documented.
It would be better to have the software read the configuration data from the HEX file. It's there, so why not use it. It still should be considered a bug and should be fixed at some point.
I can work around the problem though, so I'm still happy with the device programmer. It's now been able to program 3 different parts for 3 projects I'm working on. I recommended it to one of my clients who purchased one.
|
 |
|
Reply #7
ZLM
    
2947 Posts |
Posted - 11/03/2007 : 10:53:34
|
I tested the User ID, and it works fine. After read the chip, it displays the User ID in the User ID tab of software. |
 |
|
|
Topic  |
|