Any one has experience with loading eeprom memory in different location (address) Any time I loaded hex say for pic16fxx pic16fxxx in Topwin the eeprom memory goes to 4200 instead to 4000 I know the MPLAB compiling the hex to :10025000F8302F210000980B28290800F930FF3EC4 :06026000031D2F29080018 :1042000000000100000000000000020000000000AB :104210000000030000000000000004000000000097
4200, but all rest of the software for different programmers setting eeprom to 4000 without adjustment. Any suggestion. Thanx
The TOPWin is right. Your data is located at address 4200. one way you can do is load the data to 4200, then save it as .bin file. Then use a binary editor to move those data to 4000 then save and open it by TOPWin.
Hi I know TopWin it is right, but for example PICALL/WIN or IC-PROG always burn the eeprom in 4000 and MPLAB from Microchip always compiling the EEPROM in 4200 it’s no problem to edit hex file by the self but why it is that Thanx
I think both are not wrong. This is totally defined by the programmer software. As long as the data is not overlaped with the code. And the programmer's software knows where to look at the code and data.
When the software to program the device, it will use data location they defined.
So, different programmer software may have different data start location. Of cause it will be nice if they all use same address for data.
Hi I know both are right but still the MPASMWIN (assembler) from Microchip producing HEX with address 4200 for some reason, but in micro the address is 4000 so why TopWin not adjust the address automatically. Jep you saying not all have same address but mostly for PIC family it is used MPASMWIN as compiler which locate the eeprom address about +200 so why?? Microchip or TopWin?? Thanx
Top 2004 and Topwin
Posted - 05/26/2005 : 07:57:39
Any one has experience with loading eeprom memory in different location (address)
