| View previous topic :: View next topic |
| Author |
Message |
FvM
Joined: 27 Aug 2008
Posts: 2337
Location: Germany
|
| Current ICD-Software doesn't support newer PIC24F devices |
 Posted: Sun Sep 14, 2008 6:11 am |
 |
|
Hello,
more than two weeks, after I reported non-operation of ICD-U40 with a PIC24F192GA106 to support, but got no substantial response (exept for a suggestion to try previous firmware 2.25), I felt a need to clarify the issue by myself and found this:
All newer PIC24Fxxx devices have an erroneous DEVICE ID entry of 0407 in devices4.dat, which is valid for PIC24FJ128GA006 only. The new DEVICE IDs have been published by Microchip in Dec 07 (latest) in a separate programming specification.
I patched the table with the correct PIC24F192GA106 DEVICE ID of 1010 and the Target Test passed immediately.
Best regards,
Frank |
|
 |
FvM
Joined: 27 Aug 2008
Posts: 2337
Location: Germany
|
|
| Posted: Sun Sep 14, 2008 7:03 am |
|
|
| As an additional remark, the PIC24FxxxGB devices have correct DEVICE IDs in devices4.dat, which corresponds to the fact, that they have also correct resource entries related to PCD operation (e. g. interrupts), while the GA devices haven't. |
|
|
kam
Joined: 15 Jul 2005
Posts: 59
|
|
| Posted: Tue Sep 23, 2008 1:22 pm |
|
|
Thanks for the info!
At least you got a response from your email...I'm still waiting for mine (other then the automated response!)...
~Kam (^8* |
|
|
FvM
Joined: 27 Aug 2008
Posts: 2337
Location: Germany
|
|
| Posted: Wed Sep 24, 2008 11:16 pm |
|
|
| I got a response shortly after I sent a qualified bug report (together with the above posting). I received an updated devices4.dat file. Because I was busy with concurrent projects in the meantime, I didn't yet test it, but I'm basically trustful, that the issue will be fixed. CCS also told, that someone will have a look on some missing features in 24FxxxGA device support, e. g. with UART interrupts. |
|
|
FvM
Joined: 27 Aug 2008
Posts: 2337
Location: Germany
|
|
| Posted: Thu Sep 25, 2008 3:31 am |
|
|
| As a supplement: The updated devices4.dat makes ICD-U40 recognize the PIC24F192GA106, but gives verification errors with configuration fuses. Furthermore, the fuses data, that has been understandable to MPLAB8.10 before, is now shifted to an apparently wrong address and can't be used by MPLAB anymore. I stay with previous devices4.dat and MPLAB/ICD2 for the time being. |
|
|
FvM
Joined: 27 Aug 2008
Posts: 2337
Location: Germany
|
|
| Posted: Fri Oct 03, 2008 2:56 am |
|
|
Hello,
I checked most recent ICD windows software V299.25.16 with PIC24FJ192GA106 for possible bug fixes and found this
- the GA106 chip is now recognized
- a small application image (bootloader only) showed verification errors
| Quote: | Address Actual Expected
020C00 F2 58
020C01 72 33
020C02 FF 00 |
Although these addresses are actual config memory related, the error is reported for program memory
- the application doesn't run
Read back of the image with ICD 2 revealed reserved bit 10 in Configuration Word 1 programmed different than required by Microchip. The difference is also ignored in MPLAB verify, by the way.
| Code: | Config memory readback ICD-U40 programmed
:020000040004F6
:1017F400 011E0000 FA720000 783B0000
Config memory readback ICD 2 programmed
:1017F400 011E0000 FA720000 783F0000 |
- a more complex image reported "Bad file format or checksum, although it's an original CCS C generated hex-file and also accepted by MPLAB.
- the respective cof file was accepted for programming but resulted in a shower of verification errors. The problem may be related to the non-continuous arrangement of the application image file, as generated by CCS C when importing binary (hex) data to the project.
As a result: PIC24FJ192GA106 is still unsupported by current ICD-U40 software. It obviously never has been tested with this device family.
Regards,
Frank |
|
|
FvM
Joined: 27 Aug 2008
Posts: 2337
Location: Germany
|
|
| Posted: Wed Oct 22, 2008 12:01 am |
|
|
Hello,
| Quote: | | As a result: PIC24FJ192GA106 is still unsupported by current ICD-U40 software. It obviously never has been tested with this device family. |
The statement also applies to most recent Software version 2.100.16.11 with Firmware 02-50. New errors appear, still not operational, also with PIC24FJ128GA106.
CCS support has been informed.
Best regards |
|
|
FvM
Joined: 27 Aug 2008
Posts: 2337
Location: Germany
|
|
| Posted: Sat Dec 06, 2008 5:52 am |
|
|
Hello,
I find, that ICD software V2.102 is now basically operational with PIC24FJ128GA106 and PIC24FJ192GA106, which is an important improvement.
There is however still a problem with non-continuous hex files. They are generated by PCD, if an #import(FILE= ) is used in the project. The imported code is inserted into the binary output as is, without merging it into a new image. I use the #import directive to include a bootloader application image into the production binary.
MPLAB and PICkit2 tools can work with these kind of hex files, ICD-U40 gives verification errors and the application doesn't run. If the application code is re-exported by MPLAB to a continuous image file, it programs succesfully with ICD-U40.
Best regards,
Frank |
|
|
|
FAQ 
Search
Register
Profile 
Log in to check your private messages 
Log in
