| View previous topic :: View next topic |
| Author |
Message |
charliumi
Joined: 03 Nov 2016
Posts: 11
|
| to gaugeguy |
 Posted: Wed Dec 14, 2016 6:38 am |
 |
|
Could you share the Fuses configuration as you mentioned you successfully make it work ?
I found out today that there's a message on CCSLoad indicating that PCI25FJ256GB406 is not Yet supported.
Could someone from CCS shim in and give an official answer ? |
|
 |
newguy
Joined: 24 Jun 2004
Posts: 1909
|
|
| Posted: Wed Dec 14, 2016 7:08 am |
|
|
| No one from CCS monitors these forums. If you have a question for CCS, you have to ask them yourself. |
|
|
gaugeguy
Joined: 05 Apr 2011
Posts: 303
|
|
| Posted: Wed Dec 14, 2016 7:54 am |
|
|
I tested with the PIC24FJ256GA406-I/PT
I am not sure if there would be any difference in the programming of the 'B' USB version, but I wouldn't expect any. Below are the configuration fuses from the list file.
| Code: |
Configuration Fuses:
Word 1L: FCBF NOWRTB NOBSS NOBS NOWRT PROTECT WPCFG PROTECT_CFG NOAIVT
H: 0000
Word 2L: FFFF
H: 0000
Word 3L: FFFF
H: 0000
Word 4L: FFFF
H: 0000
Word 5L: FFFF
H: 0000
Word 6L: 7FFF
H: 0000
Word 7L: FFE3 PR_PLL PLL4X IESO
H: 0000
Word 8L: FF1D XT NOOSCIO SOSC_SEL PLL_FROM_PRIMARY NOIOL1WAY CKSFSM
H: 0000
Word 9L: F7FA WPOSTS11 WDT128 WDT WINDIS WDTWIN_25% NOWDTCMX WDTCLK_LPRC
H: 0000
Word 10L: FFFF BROWNOUT NOLVR
H: 0000
Word 11L: FFDF ICSP1 NOJTAG NODEBUG NOBTSWP
H: 0000
Word 12L: FFFF DSWDTCK_LPRC DSBOR DSWDT
H: 0000
Word 13L: FFFF NOALTCMPI NOTMPRPIN NOTMPRWIPE VREFNORM
H: 0000
|
[/code] |
|
|
Ttelmah
Joined: 11 Mar 2010
Posts: 19549
|
|
| Posted: Wed Dec 14, 2016 10:11 am |
|
|
| Just as a comment, the GA, and the GB chips use the same programming data sheet & algorithm. So the only difference will be the device ID probably not being supported... |
|
|
charliumi
Joined: 03 Nov 2016
Posts: 11
|
| Conclusion - PCHWHD is buggy |
| Posted: Fri Dec 23, 2016 12:51 pm |
|
|
The issue was linked to the version of the compiler I used, which were not generated the appropriate set of instructions. I upgraded to the latest version (5.066), with same configuration and same board and the problem is gone. It works fine with both ICD64 and ICD80.
I found others issues since but I will share this on a separate thread.
Thanks |
|
|
|
FAQ 
Search
Register
Profile 
Log in to check your private messages 
Log in
