BPM Socket: Difference between revisions
No edit summary |
No edit summary |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 12: | Line 12: | ||
Device list: http://web.archive.org/web/20120925022829im_/http://www.bpmicro.com/pdf/engineering-device-list.pdf | Device list: http://web.archive.org/web/20120925022829im_/http://www.bpmicro.com/pdf/engineering-device-list.pdf | ||
More info here: https://www.adaptsys.com/support-services/bpm-support/faq | |||
= Standard = | = Standard = | ||
Used on older programmers like BP series | Used on older programmers like BP series | ||
== Firmware analysis == | |||
Case study on SM48D EEPROM | |||
* samples | |||
** 4 good | |||
** 1 with corrupt EEPROM, mostly ignored | |||
* unk00: always 17 | |||
* name: always SM48D | |||
* namei | |||
** no generally noticeable pattern | |||
** 0xF0000000 always set | |||
* unk1E: Relatively small number that varies, possibly serial number | |||
* pad22: always 0 | |||
* unk26: always 0 | |||
* unk44: always 0x55aa | |||
* unk46: always 0xa233 | |||
* unk48: always 1 | |||
* pad4A: always 0 | |||
Generally seems that there is a structure being used which is initialized to 0. Some fields are unused, keeping them at 0. Anything beyond the structure is 0xFF | |||
== SM32TC == | == SM32TC == | ||
| Line 37: | Line 60: | ||
https://x.com/johndmcmaster/status/1171332341244940288 | |||
https://github.com/JohnDMcMaster/prog-cad/tree/master/bpm-socket/sm48d | |||
== SM56TB == | == SM56TB == | ||
| Line 87: | Line 113: | ||
= FX2, FX4 = | = FX2, FX4 = | ||
= Purchasing = | |||
https://www.artisantg.com | |||
* Has a large inventory, but they want $350 per socket | |||
Latest revision as of 21:33, 5 July 2024
Look them up here: http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/
Ex: http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/SM56TB
This is also interesting: http://www3.bpmicro.com/DeviceList.nsf/128c573fb6a3a6d9862579b4006de31f!OpenView
Info: http:www.bpmmicro.com/your-socket-solution/
Device list: http://web.archive.org/web/20120925022829im_/http://www.bpmicro.com/pdf/engineering-device-list.pdf
More info here: https://www.adaptsys.com/support-services/bpm-support/faq
Standard
Used on older programmers like BP series
Firmware analysis
Case study on SM48D EEPROM
- samples
- 4 good
- 1 with corrupt EEPROM, mostly ignored
- unk00: always 17
- name: always SM48D
- namei
- no generally noticeable pattern
- 0xF0000000 always set
- unk1E: Relatively small number that varies, possibly serial number
- pad22: always 0
- unk26: always 0
- unk44: always 0x55aa
- unk46: always 0xa233
- unk48: always 1
- pad4A: always 0
Generally seems that there is a structure being used which is initialized to 0. Some fields are unused, keeping them at 0. Anything beyond the structure is 0xFF
SM32TC
SM44QC
SM48D
https://x.com/johndmcmaster/status/1171332341244940288
https://github.com/JohnDMcMaster/prog-cad/tree/master/bpm-socket/sm48d
SM56TB
http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/SM56TB
SM100TQ
SM-84UP
SM-208CQSX-Actel
ASM100FBG
Found at HSC. ASM100FBG is found in the EEPROM
http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/ASM100FBG
"BGA(100), 1.0 mm pitch"
Only supports 2 devices
SMAH48DL1
Closest I could find: SMAH20P (http://www3.bpmicro.com/DeviceList.nsf/SocketSolutions/SMAH20P)
Which is for a "PLCC(20...80)". Weird
FX
FX2, FX4
Purchasing
- Has a large inventory, but they want $350 per socket