chris_ua
03-29-2003, 02:34
Hi!
Finally I made my Griffin to work with most DCT3 phones.
As for hardware, there are two mistakes in all three cable schemes found
on support page (two PDF documents): connection for pin 3 of RJ-45 connector
should be swapped with pin 7, and pin 4 with pin 6 as well. For correct wiring
consult this pinout of Griffin box (numbered from left to right, looking from
the front of the cable, and the locking latch is up):
1 - Vcc
2 - nc
3 - BSI (AFAIK for DCT3 it used as BTEMP to power up the phone)
4 - TX
5 - RX
6 - MBUS
7 - GND
8 - Vpp (not used in DCT3 cables)
(thanx gsm-tech for this info)
As for software part, in each folder with flashes for DCT3 models you should
have an INI file. For those of us, who allready have a relatively large archive
with DCT3 flashes in different format and don't willing to download them again
in original Nokia packages just to get those INIs, I'll tell how to create
them manually.
But first a few words about flash files. You'll need them in WinTesla format,
so to convert from Dejan 1.05 you will need to cut off first 16 (decimal) bytes
of PPM to get plain binary and then convert by dejan2wt tool by Lead.
In the INI file itself the Griffin seems to look only for three lines which are
as follows:
[NSM-1_RESTOREFILES]
LowEraseLimit=200000
HighEraseLimit=3FFFFF
The first one is the model definition (don't know if the INI file name should be
same as model type, but the line 1 should match exactly.
The second is the flash start address and it should be 200000 for all DCT3.
The last one is a bit tricky. You can count this as 200000h+MCU_size+PPM_size or
as 200000h+Flash_chip_size-EEPROM_area_size.
In most cases you'll get equal results, but if not, make sure Griffin won't
overwrite any vital data (it WILL erase the whole area specified regardless of
real MCU and PPM size). For old models with external EEPROM you should specify
the whole flash chip. Models with JAVA contents (e.g. 3410) are still under
question: should it overwrite JAVA or not?
Here are addresses I calculated:
3210 NSE-8 3FFFFF
NSE-9 3FFFFF
3310 NHM-5 3CFFFF
3330 NHM-6 54FFFF
5110 NSE-1 2FFFFF
5130 NSK-1 2FFFFF
5510 NPM-5 54FFFF
6110 NSE-3 2FFFFF
6130 NSK-3 2FFFFF
6150 NSM-1 3FFFFF
6210 NPE-3 59FFFF
6250 NHM-3 59FFFF
7110 NSE-5 58FFFF
8210 NSM-3 3CFFFF
8250 NSM-3D 3CFFFF
8810 NSE-6 3FFFFF
8850 NSM-2 3CFFFF
8890 NSB-6 3CFFFF
3410 NHM-2 56FFFF
5210 NSM-5 57FFFF
3610 NAM-1 54FFFF
2100 NAM-2 3FBFFF
Please, correct me if I'm wrong.
So, for example for 3310 you should make a folder NHM-5 inside PRODUCTS folder,
copy your WinTesla flashes there, then make a text file NHM-5.ini with following
text inside:
[NHM-5_RESTOREFILES]
LowEraseLimit=200000
HighEraseLimit=3CFFFF
Questions, that are still open, are:
1. There are no cable scheme for 3210 and 8810, and since the first one uses
2.4v battery and uses VPP for flashing, don't know how to make cable for it.
2. What End address should be specified for Java enabled phones.
Finally I made my Griffin to work with most DCT3 phones.
As for hardware, there are two mistakes in all three cable schemes found
on support page (two PDF documents): connection for pin 3 of RJ-45 connector
should be swapped with pin 7, and pin 4 with pin 6 as well. For correct wiring
consult this pinout of Griffin box (numbered from left to right, looking from
the front of the cable, and the locking latch is up):
1 - Vcc
2 - nc
3 - BSI (AFAIK for DCT3 it used as BTEMP to power up the phone)
4 - TX
5 - RX
6 - MBUS
7 - GND
8 - Vpp (not used in DCT3 cables)
(thanx gsm-tech for this info)
As for software part, in each folder with flashes for DCT3 models you should
have an INI file. For those of us, who allready have a relatively large archive
with DCT3 flashes in different format and don't willing to download them again
in original Nokia packages just to get those INIs, I'll tell how to create
them manually.
But first a few words about flash files. You'll need them in WinTesla format,
so to convert from Dejan 1.05 you will need to cut off first 16 (decimal) bytes
of PPM to get plain binary and then convert by dejan2wt tool by Lead.
In the INI file itself the Griffin seems to look only for three lines which are
as follows:
[NSM-1_RESTOREFILES]
LowEraseLimit=200000
HighEraseLimit=3FFFFF
The first one is the model definition (don't know if the INI file name should be
same as model type, but the line 1 should match exactly.
The second is the flash start address and it should be 200000 for all DCT3.
The last one is a bit tricky. You can count this as 200000h+MCU_size+PPM_size or
as 200000h+Flash_chip_size-EEPROM_area_size.
In most cases you'll get equal results, but if not, make sure Griffin won't
overwrite any vital data (it WILL erase the whole area specified regardless of
real MCU and PPM size). For old models with external EEPROM you should specify
the whole flash chip. Models with JAVA contents (e.g. 3410) are still under
question: should it overwrite JAVA or not?
Here are addresses I calculated:
3210 NSE-8 3FFFFF
NSE-9 3FFFFF
3310 NHM-5 3CFFFF
3330 NHM-6 54FFFF
5110 NSE-1 2FFFFF
5130 NSK-1 2FFFFF
5510 NPM-5 54FFFF
6110 NSE-3 2FFFFF
6130 NSK-3 2FFFFF
6150 NSM-1 3FFFFF
6210 NPE-3 59FFFF
6250 NHM-3 59FFFF
7110 NSE-5 58FFFF
8210 NSM-3 3CFFFF
8250 NSM-3D 3CFFFF
8810 NSE-6 3FFFFF
8850 NSM-2 3CFFFF
8890 NSB-6 3CFFFF
3410 NHM-2 56FFFF
5210 NSM-5 57FFFF
3610 NAM-1 54FFFF
2100 NAM-2 3FBFFF
Please, correct me if I'm wrong.
So, for example for 3310 you should make a folder NHM-5 inside PRODUCTS folder,
copy your WinTesla flashes there, then make a text file NHM-5.ini with following
text inside:
[NHM-5_RESTOREFILES]
LowEraseLimit=200000
HighEraseLimit=3CFFFF
Questions, that are still open, are:
1. There are no cable scheme for 3210 and 8810, and since the first one uses
2.4v battery and uses VPP for flashing, don't know how to make cable for it.
2. What End address should be specified for Java enabled phones.