| T O P I C R E V I E W |
| busterk |
Posted - 06/15/2009 : 12:43:43
Could you add this pic for next sw release for GQ-4X?
Or could i add this myself?
Here are the specs:
P.Memory (Kbytes) 7 Flash
P.Memory (KWords) 4
Self-Write Flash Yes
RAM (Bytes) 384
EEPROM (Bytes) 256
I/O Pins 16
Max CPU Speed 32 MHz (8 MIPS)
Internal OSC 32 MHz, 32 kHz
Code Guard™ Security
System Mgmt Features BOR, LVD, POR, WDT, nanoWatt-[Low Speed, Fast Wake, Active Ctrl]
Analog Peripherals 2-Comparators w/SR-Latch, OpAmp, ShuntReg; 1A/D, 12x10-bit @ 100ksps
Digital Comm. Peripherals 1-A/E/USART, 2-MSSP(SPI/I2C)
Connectivity
Capture/Compare PWM Peripherals 2-CCP, 2-ECCP, 10-bitPWM
Digital Timers 4x8-bit, 1x16-bit
Application Peripherals No, EBI-No
Debug/Development Features ICSP, Integrated ICDdebug
Package (Pins) (18)
Operating Voltage (1.8V-5.5V)
Temperature Ranges (-40 to +125
|
| 24 L A T E S T R E P L I E S (Newest First) |
| ZLM |
Posted - 05/01/2010 : 22:28:54
Download again and see if it fixed. |
| RidDleZis1337@gmail.com |
Posted - 05/01/2010 : 19:29:45
I've got a strange issue now.. My code in MPLAB is compiled with all the config bits configured the way I want them, but when I load the .hex file into the programmer it doesn't recognize my changes. I have to manually set them all from the config tab anyway... It worked fine with other pics used and MPLAB shows the right values from the Configure->Configuration Bits menu. It seems to be a problem with the programming software? |
| RidDleZis1337@gmail.com |
Posted - 05/01/2010 : 06:40:21
YES! It sure does sir. Config bits write fine, let you know if anything turns up but this seems to do the trick. Thank you! |
| ZLM |
Posted - 04/29/2010 : 10:24:36
Try:
http://www.mcumall.com/download/TrueUSBWillem/GQUSBPrgRe5.03Beta.exe
Let me know if this works. |
| RidDleZis1337@gmail.com |
Posted - 04/22/2010 : 20:13:51
I will be patiently waiting  |
| ZLM |
Posted - 04/17/2010 : 18:11:14
If you can wait, I will get a testing chips in 2 or 3 weeks. If you are in hurry, then you can send me a chip. |
| RidDleZis1337@gmail.com |
Posted - 04/16/2010 : 12:28:03
Alright, have tried both ways, ICSP and in programmer and still same result. Also, when I say it 'hangs' I do not mean it freezes. It just pauses for a few seconds and then continues to say verify failed.
If you need I wouldn't mind sending you a chip, but they're only like $2 a piece |
| ZLM |
Posted - 04/15/2010 : 16:04:07
If your testing hangs when write the CFG, then it is hard to do the test.
First thing is to find out why it hangs during the write CFG bit.
OR
You can try to use ICSP connection to see if it still hangs. ICSP is to only connect 5 pins from programmer socket to chip.
|
| RidDleZis1337@gmail.com |
Posted - 04/14/2010 : 23:59:12
Alright, but is there anything else I can do? I've got the chip right here :-/ It just seems so close with everything else verifying correctly.. |
| ZLM |
Posted - 04/14/2010 : 22:21:33
That was I mean.
I think I need to get a chip for testing. |
| RidDleZis1337@gmail.com |
Posted - 04/14/2010 : 19:16:30
Without the chip? I'm sorry, I don't know what you mean.
*edit*
Alright, I've removed the chip and went through the motions without loading a hex file. It successfully writes nothing and verifies it. Including the config bits which are all on. Also, when I change a config bit and attempt the same, the config bit verify fails as it should, correct?
and yes this is the DIP18 |
| ZLM |
Posted - 04/14/2010 : 15:57:42
I do not have this chip for testing. So, I tried it without the chip. But it seems working fine, no hangs.
Can you try to write without chip? uncheck the ID check box first.
What is your chip package? DIP 18 pin?
|
| ZLM |
Posted - 04/14/2010 : 13:34:28
The 16F1827 is a new PIC chip. It has different CFG address. I will try it later and let you know then. |
| RidDleZis1337@gmail.com |
Posted - 04/14/2010 : 08:53:22
I've tried both ways and still nothing. I usually use the 'Auto' button after setting the right cfg bits in the 'Configuration' tab.
I've been looking into this some more and it seems the 16F1xxx chips are of a different family than the previous 16F5xxx - 16F9xxx chips
Could it be because the 16F1xxx chips are part of the 16Exxx Family apposed to the 16XXXX family? I'm not sure if this helps, I've got limited knowledge in this area. So let me know if I'm searching in all the wrong places 
Also, the 16F1827 is supposed to be the upgrade from the 16F628A if I'm not mistaken, though setting the class to this chip still yields the same results..
|
| ZLM |
Posted - 04/13/2010 : 14:59:29
How do you write the CFG bit? There are two ways: CFG button and auto write after code write. |
| RidDleZis1337@gmail.com |
Posted - 04/13/2010 : 11:36:42
Thank you for your reply ZLM, I've tried adding the line to the devices.txt and now it just hangs when writing and reading to the cfg bits, but still fails. Could it be because there are two configuration bit words? one at 8007 and one at 8008? Also, I thought the DEV file would point the programmer to the correct cfg bits? |
| ZLM |
Posted - 04/13/2010 : 11:11:15
This chip has different configuration bit address to other 16FXXX chips. Add CFGAddress(Hex)="8007" in the device line see if it works.
Name="PIC16F1827",ID="2927A0",Class="PIC16FXXX",Category="MCU",MFG="Microchip",CFGAddress(Hex)="8007",CodeSize="4096",EepromSize="256",Package="DIP18",BEGPRG_COMMAND="18",ENDPRG_COMMAND="0A",BEGERASECHIP_COMMAND="9",ERASECHIP_COMMAND="",Adapter="ICSP/PIC adapter+, no adapter required on GQ-4X";
|
| RidDleZis1337@gmail.com |
Posted - 04/11/2010 : 23:29:03
BUMP! Hello, I've got a few of these pics and I see this fellows query has been forgotten. I now require support for this device, and Microchip now has the Programming Specs :) So, Was wondering if you could add support for it in the next release now? Or if not, how would one go about adding support for a device themselves?
*update*
I've been messing around with trying to add it myself and I've managed to get it to identify correctly and program the program memory successfully, however, the configuration bits will not program.
I've found the 16F1827.dev file in the MPLAB devices directory. I've edited the 'devices.txt' file to the best of my knowledge and here's what I've got:
Name="PIC16F1827",ID="2927A0",Class="PIC16FXXX",Category="MCU",MFG="Microchip",CodeSize="4096",EepromSize="256",Package="DIP18",BEGPRG_COMMAND="18",ENDPRG_COMMAND="0A",BEGERASECHIP_COMMAND="9",ERASECHIP_COMMAND="",Adapter="ICSP/PIC adapter+, no adapter required on GQ-4X";
Still.. no dice. I think its a 'class' problem. I don't think the PIC16Fxxx class uses the same configuration bit writing/erasing algorithms as this chip.. if anyone could help to point me in the right direction that would help lots :) I would really like to use this chip soon. |
| busterk |
Posted - 06/16/2009 : 10:54:11
quote:
Originally posted by Bad_Ad84
hxxp://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en538963
"Status: Future Product"
I used hxxp://www.microchip.com/maps/microcontroller.aspx for finding
a pic with my specs , but it seems to also show future pics.
I think 16F737 will work but it has 28pin and i only need 6 :)
|
| Bad_Ad84 |
Posted - 06/16/2009 : 03:05:06
hxxp://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en538963
"Status: Future Product" |
| ZLM |
Posted - 06/15/2009 : 22:40:49
I am unable to find the programming specification for this chip from Microchip.com.
|
| busterk |
Posted - 06/15/2009 : 20:34:15
quote:
Originally posted by ZLM
Is it DIP18 package?
yes it is |
| Bad_Ad84 |
Posted - 06/15/2009 : 15:09:05
id assume so, his post says "Package (Pins) (18) " |
| ZLM |
Posted - 06/15/2009 : 14:07:09
Is it DIP18 package? |
