1) On the PIC Programmer - I have finally got the ancient PICStart Plus PIC programmer, and it's MPLab IDE, working, and have used it to burn (and then read) a PIC17C44 in order to do a firmware update of the PICStart Plus programmer itself. If anyone else decides to get one of these working this will save you hours of time - it (MPLab IDE v5.7.4, no newer version, no MPLab X IDE) requires either actual Win95 or a true Win95 emulation in Win10-x32 (but not x64) via NTVDM, directly on a PC with at least one of each - a real Com port (as Com1, 2, 3, or 4) and a real LPT port (as LPT1). The Win install cannot be in a VM (I tried VirtualBox) - as MPLab must have direct hardware access - no virtualization will work. Win98 is too new!!!, a true Win95 install, or true Win95 emulation must be achieved for the MPLab IDE to operate. Since I have largely avoided using Win for the last 25 years I had to really dig into old memories of using Win95 to get things working correctly...if you decide to try to get one of these old PIC IDE and programing platforms working - feel free to ask me Q's - especially which hardware version of PICStart Plus you would want...
.
The K150 PIC programmer was much easier to get working but doesn't have nearly the features the old MPLab does...
Turns out my MXT is an older version - has control board p/n 505-0224-C with an actual socketed PDIP PIC16C76 with marking 1.0 in pen (v1.0 of firmware) - I am under the impression 1.0 marking is MXT firmware and 1.1 marking is GMT firmware, both plugged into the same control board part number. In other words a GMT also has a control board of the same p/n but a different firmware. I believe Carl at some point also as made this point - relying on memory. Observing the schematic - the PIC firmware determines the TX frequency - I find it curious how the same board tunes either the 14khz MXT coil or the GMT 48khz coil...especially doing it so well...
I will apply my MPLab environment to my MXT PIC soon...
2) On the STM32 selection - the criteria I came up with:
a) Only LQFP packages - to make hand soldering realistic, preferrably LQFP32
b) There is a Nucleo board with the selected processor - so that breadboarding can be done on sections of the MXT instead of having to build the whole control board first, and then chunks of the firmware developed.
c) Select the highest end version of each of these
With these criteria there are two choices:
STM32F303K8T6 as LQFP32 - and it's NUCLEO-F303K8 dev board - in the NUCLEO-32 family.
STM32H503RBT6 as LQFP64 - and it's NUCLEO-H503RB dev board - in the NUCLEO-64 family.
Since the STM32F303K8T6 / LQFP32 will be much easier to hand solder I'm trying this first. My NUCLEO-F303K8 arrived today, and I rummaged around and found I have a LCD 4x80 I2C display, and a color touch screen I2C TFT display, so will begin with these (the LCD 4x80 first) as I breadboard bits of the circuit.
Processor comparison:
Current active component list:
MXT Active Components List v1b
U1 LP2951-50 SOIC8 100ma 5v LDO Voltage Regulator
U2 TLE2426 SOIC8 Voltage Reference
U3 LQFP-32 STM32F303K8T6 Microprocessor
U4 74HCT4053 SOIC16 MUX
U5 ADS8320 VSSOP8 ADC
U6 74HC4351 SOIC20 MUX
U7 TLV9362 SOIC8 Dual Op Amp
U8 LTC1446 SOIC8 DAC
U9 TLC555 SOIC8 Timer
U10 TLV1842 TSSOP8 Dual Comparator
U11 TLV9362 SOIC8 Dual Op Amp
U12 TLV9362 SOIC8 Dual Op Amp
U13 TLV9362 SOIC8 Dual Op Amp
U14 TLV9362 SOIC8 Dual Op Amp
U15 LP2951-33 SOIC8 100ma 3.3v LDO Voltage Regulator - added - to power STM32
Q1 MMBT3906 SMT PNP BJT
Q2 MMBT3906 SMT PNP BJT
Q3 MMBT3906 SMT PNP BJT
Q4 MMBT3906 SMT PNP BJT
Q5 MMBT3904 SMT NPN BJT
Q6 MMBT3906 SMT PNP BJT
Q7 MMBT3904 SMT NPN BJT
D1 IN4148
D2 IN4148
D3 IN4148
D4 N/A
D5 IN4148
D6 N/A
D7 IN4148
TH1 10K NTC Thermistor
X1 WAS 8mhz
X1 NOW 16mhz? 24mhz? 32mhz?

Leave a comment: