I have a Dataman-48pro that I'm trying to use in ISP mode to download to a dsPIC30F6014A controller. The program seems to download correctly, however, the configuration bits do not. I have the configuration bits set up properly, but it looks as if the Dataman programmer leaves the "unimplemented" configuration bits at "0". When I download the program via Microchip's ICD2, it leaves the "unimplemented" configuration bits at "1". For some reason, the controller will not run when the "unimplemented" bits are set at "0". As you can see below, the configuration bits, when read via Microchip's ICD2 are different than when downloaded via the Dataman-48pro vs. MPLAB.
DataMan 0xF80000: 1000011100010011 (0x8713)
MPLAB 0xF80000: 1111111111110011 (0xFFF3)
DataMan 0xF80002: 0000000000110010 (0x0032)
MPLAB 0xF80002: 0111111111110010 (0x7FF2)
DataMan 0xF80004: 1000011110000011 (0x8783)
MPLAB 0xF80004: 1111111111001111 (0xFFCF)
DataMan 0xF8000A: 0000000000000111 (0x0007)
MPLAB 0xF8000A: 1111111111111111 (0xFFFF)
DataMan 0xF8000C: 1100000000000011 (0xC003)
MPLAB 0xF8000C: 1100000000000011 (0xC003)
Topics related to the Dataman 48Pro
2 posts • Page 1 of 1
I think I figured out how the configuration bits seem to work with this processor. If you setup a project with a certain hex file, it loads the buffer correctly, but the configuration bits downloaded to the controller are the ones stored in the project configuration instead of the configuration bits contained in the hex file. However, if, after you load the project file, then reload the hex file after opening the project, it then uses the configuration bits contained in the hex file. So if one wants to use the configuration bits that are compiled into the hex file, they must always re-load the file after opening the project.
Who is online
Users browsing this forum: No registered users and 1 guest