The LNR versions (and maybe others) of the MTR 4B and MTR 5B have a bug that can lead to emissions on unwanted frequencies, which may be illegal and can harm your finals. This may happen only if the RTC is in use. I am not sure about this, though.
See the post by Steve Webber at
"I need to warn of a potential problem with the LNR 5B with the 2x16 LCD display. With the clock enabled, it is possible for the DDS chip to get the wrong data and transmit out of band. This happens because the data clocking bit for the LCD and DDS have opposite sense. The DDS clocks in data when the bit goes low, the LCD clocks in data when the bit goes high. Unfortunately, I failed to ensure the clock bit was in the proper state at the beginning of a data transfer to each device. This problem was not initially apparent because when the RTC is not on, the sequence used to write to the DDS and LCD is such that the clock sense is corrected. However, when the RTC is turned on, a write to the display to update the time leaves the data clock bit in the wrong state for the next write to the DDS, which could occur when you go to transmit. This might also be the cause of lock up problems some users have experienced when the RTC is displayed. Firmware rev 1.8 and later fixes this problem. To find out what firmware rev you have, turn power on while holding down the Function button. Otherwise, it would be a good idea to keep a SWR meter in line and if you see the SWR suddenly go high when transmitting, you know your out of band. Tuning up and back down one step will correct the problem."
As far as I know, the bug has been spotted by Chris, GU3TUX.
As for the head type, “E2” works best for solder pads with a hole.
I cut four tiny pieces of perfboard and glued them together with superglue; make sure the holes are perfectly aligned and the super-glue does not run into the holes. The two outer pieces should have the copper layer to the outside. This stabilizes the pogopins.
I then added three jumper wires for connection with the LaunchPad.
The (likely) pinout of the PRGM solder pads on the MTR-5B LNR revision is as shown on the attached picture.
This is untested; use it at your own risk, but I think this is correct, since the rightmost pin is connected to the ground layer, and the leftmost runs via R28 to 3.3V and should hence be “RST”, which leaves the middle pin for “TEST”.
Will share experiences once I will have been successful.
I still have my MTR5B on the bench for the update and started a new attempt tonight. In short: With OSX, flashing an updated firmware using the TI toolchain for the cheap TI Launchpad does not seem to work. While there is a version of the TI flasher tool for OSX,
there is no USB driver for the MSP-EXP430G2 Launchpad for OSX. It seems one can use Windows in a virtualization environment, but that was non-trivial to set up for me.
If anybody was successful flashing the MTR5B with the new firmware on OSX, I would be very interested to learn of the toolchain being used. I would now try to find a Windows machine to do the update.
I think you are over complicating things. There is plenty of info on the ATS Yahoo group regarding reflashing the MTR firmware. There’s no need to use the TI software suite, just use the simple MSPFet application bundled with the MTR-5B firmware .ZIP file. It was a while ago and I can’t remember the exact details, but I successfully got the MSPfet application to burn new MTR-4B firmware with a few tweaks to a .bat file, it was very logical.
This is an extract of an email I sent to another ham thinking about uploading new firmware to a 4B -
*I have simply modified the MTR-5B firmware folder with the new file provided by Steve. I obviously do not have an MTR4B to experiment on, but I did find an MSP430 chip and the firmware uploaded first time with no problems.
All you should have to do is extract the files in the zipped folder, remove the chip that comes shipped in the launchpad socket, and connect up the launchpad to the MTR. With power applied to the MTR, double click on MTR4B_60Burn.bat and then the firmware should upload into the MTR*
(Filenames probably not the same in your case, but procedure would be same)
BTW, it’s sufficient to just push Dupont style cable pins into the MTR programming holes during reflash, soldering is not needed.
Carefully push the pogo-pin adapter from above to the PROG connector on the MTR. Make sure you don’t touch any other pins or discharge static electricity.
Then hit Enter and wait for the upload to complete. A GUI window of the programmer will open and indicate the progress.
When done, power down the LaunchPad and the MTR.
You are all set. Press and keep pressed Fn while turning on the MTR, and the message “Revision 1.9” will confirm that you are done.
There are TWO caveats:
In one of the PDFs in the Yahoo forum they say the pinout of the PROG header was “Ground**/Rest/Test**”, while in fact on the MTR-5B it is “Ground**/TEST/Rest**”. The former order might be correct for the MTR3-B or earlier boards, I did not check that.
The batch file MTR4B_5B_2X16LCD_REV1.9.bat has a spelling mistake with regard to the firmware binary: CORRECT: MTR4B_5B_2X16LCD_REV1.9.bin WRONG: MTR_4B_5B_2X16LCD_REV1.9.bin
Warning! Before you apply that update, wait for my analysis of a major problem: With the new firmware, my MTR sends strange signals (while the signal in the earphone is correct). It almost ruined my last activation :-(.