BP Microsystems: Difference between revisions

From Proghq
Jump to navigation Jump to search
VisualWikitext
No edit summary
 
(11 intermediate revisions by one other user not shown)
Line 1: Line 1:
[[Category:BPM]]
[[Category:BPM]]
[[Category:Vendor]]


Homepage: http://www.bpmmicro.com/
Homepage: http://www.bpmmicro.com/
Device search: http://www.bpmmicro.com/device-search/
Part numbering scheme: http://www3.bpmmicro.com/web/helpandsupport.nsf/WebKeys/BPM-6YEMRW!OpenDocument&Cat=Issue&Click=


[[:Category:BPM]]
[[:Category:BPM]]
Line 13: Line 18:
Secondary goal: explore options to make high quality legacy parallel port units (ex: BP-1600) usable on modern computers.  One good option might be to RE protocol and network them with a RPi
Secondary goal: explore options to make high quality legacy parallel port units (ex: BP-1600) usable on modern computers.  One good option might be to RE protocol and network them with a RPi


= Parallel port =
=Parallel port=
Silicon Sculptor
 
* "a standard IEEE 1284 parallel cable (EPP) must be used"
* "The Silicon Sculptor I communicates using bi-directional, ECP, or EPP. You must set the Silicon Sculptor II to EPP; otherwise, it does not communicate on most computers and the GUI is fixed in Demo Mode"
 
 
2020-04-10
 
*t61p + docking station
*bi-directional: unreliable. Detected S/N, but then BPWin starting throwing internal errors and was unusable
*ECP: didn't work at all
 


EOL notice: [[http:''www3.bpmmicro.com/web/helpandsupport.nsf/WebKeys/BPM-8NTSKL?openDocument|http:''www3.bpmmicro.com/web/helpandsupport.nsf/WebKeys/BPM-8NTSKL?openDocument]]
EOL notice: [[http:''www3.bpmmicro.com/web/helpandsupport.nsf/WebKeys/BPM-8NTSKL?openDocument|http:''www3.bpmmicro.com/web/helpandsupport.nsf/WebKeys/BPM-8NTSKL?openDocument'']]


  <nowiki>
  <nowiki>
LN: ftp:''ftp.bpmmicro.com/Dnload/bpw_v5330.exe
      LN: ftp:''ftp.bpmmicro.com/Dnload/bpw_v5330.exe
LN: is the last one which works with parport
      LN: is the last one which works with parport
LN: however i'm not sure that one runs on xp!
      LN: however i'm not sure that one runs on xp!
LN: that one does bitch at you that parport is EOLed
      LN: that one does bitch at you that parport is EOLed
LN: 5270 is the last one which doesn't bitch
      LN: 5270 is the last one which doesn't bitch
LN: if that bothers you
      LN: if that bothers you
</nowiki>
      </nowiki>


== VM operation ==
==VM operation==


Card: StarTech Parallel Card - SPP/EPP/ECP EC1PECPS
Card: StarTech Parallel Card - SPP/EPP/ECP EC1PECPS
Line 48: Line 65:
Hooked up EC1PECPS to native Windows XP t61 system and wokred fine.
Hooked up EC1PECPS to native Windows XP t61 system and wokred fine.


= JM inventory =
=User's Guide / The Engineer's Programmer=
 
[[File:Engineers programmer.jpg|300px]]
 
Dying to read it?  Well you probably don't want to:
<code>
LN: its not super exciting, documents some bpdos stuff and basic setup
</code>
 
But feel free to throw out a line if you *really* want it scanned for some bizarre reason
 
<br />
===Site===
Trying to understand relationship between models and site numbers
 
Note: early models didn't distinguish site vs serial. If both aren't indicated, its probably the same
{| class="wikitable"
|+
!Site
!DOM
!Vendor
!Model
!Note
|-
|1056
|
|BP
|PLD-1128
|
|-
|1631
|
|BP
|EP-1140
|
|-
|4653
|
|BP
|EP-1
|
|-
|5172
|
|BP
|EP-1
|
|-
|7998
|
|BP
|EP-1
|
|-
|11193
|
|BP
|1200
|
|-
|12716
|
|BP
|1200
|
|-
|15278
15281
|
|BP
|2200/240x4M4
|
|-
|17243
|
|BP
|1148
|
|-
|17598
17602
|
|Actel
|SS1-6
|
|-
|18679
|2001-10-05
|Actel
|SS1
|
|-
|18797
18800
|
|BP
|2200/240X4M4
|
|-
|19022
19026
|
|BP
|2100/84X4M4
|
|-
|19341
19341
|
|BP
|2200/240X2M4
|
|-
|22501
|1999-12-15
|Actel
|SS1
|
|-
|23007
|
|BP
|1400
|
|-
|25294
25297
|
|BP
|2200/240X4
|
|-
|26047
26050
|
|BP
|2000/84X4
|
|-
|28781
|2001-10-12
|BP
|1600
|
|-
|30251
|
|Actel
|SS2
|
|-
|31196
|2003-07-07
|Actel
|SS2
|
|-
|34346
|2005-09-30
|BP
|1410
|
|-
|34681
|
|Actel
|SS2
|
|-
|38211
|2009-09-25
|Actel
|SS3
|
|-
|39901
|
|BP
|1610
|
|-
|
|
|
|
|
|-
|
|
|
|
|
|}
SS: Silicon Sculptor. SS1 => FP-ACTEL, SS2 => FP-ACTEL-II
 
=Device Programming Language (DPL)=
 
BP-3600 doc indicates this is the name of a high level language used for programming algorithms, introduced in 1987
 
 
<nowiki>http://www3.bpmmicro.com/web/helpandsupport.nsf/69f301ee4e15195486256fcf0062c2eb/bb22d83a95b7f1688625703e0062ae67!OpenDocument</nowiki>
 
very empty...
 
 
<nowiki>http://www3.bpmmicro.com/web/home.nsf/(web.news)/9A6F2919E23DEF85862571420052C045</nowiki>
 
March 31, 2006 — BP Microsystems, a leading supplier of device programming systems worldwide, announces it has revamped its Device Programming Language (DPL) algorithm development environment in BPWin to allow its over 100 semi-house partners to co-develop and test algorithms for new devices


Programmers


''' BP-1410 (in the mail)
<nowiki>http://www3.bpmmicro.com/web/home.nsf/(web.news)/A80A7F8654FDF5CD86256FC80081C28C</nowiki>
''' BP-1600


Socket modules
Unlike other companies that have rewritten programming algorithms for each new programmer model, BP’s newest generation of programmers runs the same device independent programming algorithm used by all BP’s programmers. Having invented Device Programming Language (DPL) in 1987, BP has been able to introduce generation after generation of improved products without the delays and bugs associated with algorithm rewrites. For compatibility, the new programmers incorporate the same proven pin drivers and socket modules used by the full range of BP programmers.


''' SM48D (DIP)
'''* And one more coming with the BP-1410 I think
''' SM-84UP
''' SM32TC
''' Custom BGA module
''' SM44QC
''' SM100TQ


BPM Overview, March 2010


= User's Guide / The Engineer's Programmer =
All algorithms written in proprietary Device Programming Language (DPL)


[[File:Engineers programmer.jpg|300px]]
Because all of our programmers use DPL we are able to instantly support existing algorithms on new products (unlike other 3rd party programmers who must start over writing new algorithms whenever they introduce new products)


Dying to read it?  Well you probably don't want to:
<br />
<code>
LN: its not super exciting, documents some bpdos stuff and basic setup
</code>


But feel free to throw out a line if you *really* want it scanned for some bizarre reason
==API==
Looks like it might be COM component. Not familiar with these to quickly play with it
<br />

Latest revision as of 18:51, 19 April 2020


Homepage: http://www.bpmmicro.com/

Device search: http://www.bpmmicro.com/device-search/

Part numbering scheme: http://www3.bpmmicro.com/web/helpandsupport.nsf/WebKeys/BPM-6YEMRW!OpenDocument&Cat=Issue&Click=

Category:BPM

Socket main page

Programmer main page

Project goal: open source tools to drive BP programmers to enable more advanced R&D (ex: raster scan laser to find fuses)

Secondary goal: explore options to make high quality legacy parallel port units (ex: BP-1600) usable on modern computers. One good option might be to RE protocol and network them with a RPi

Parallel port

Silicon Sculptor

  • "a standard IEEE 1284 parallel cable (EPP) must be used"
  • "The Silicon Sculptor I communicates using bi-directional, ECP, or EPP. You must set the Silicon Sculptor II to EPP; otherwise, it does not communicate on most computers and the GUI is fixed in Demo Mode"


2020-04-10

  • t61p + docking station
  • bi-directional: unreliable. Detected S/N, but then BPWin starting throwing internal errors and was unusable
  • ECP: didn't work at all


EOL notice: http:www3.bpmmicro.com/web/helpandsupport.nsf/WebKeys/BPM-8NTSKL?openDocument 

       LN: ftp:''ftp.bpmmicro.com/Dnload/bpw_v5330.exe
       LN: is the last one which works with parport
       LN: however i'm not sure that one runs on xp!
       LN: that one does bitch at you that parport is EOLed
       LN: 5270 is the last one which doesn't bitch
       LN: if that bothers you

VM operation

Card: StarTech Parallel Card - SPP/EPP/ECP EC1PECPS

Without any programmer you get this:

Since there is no programmer attached to any LPT or USB port, the software will operate in the demo mode. If you are trying to use a programmer, make sure it is powered up and plugged into a parallel printer port (LPT models) or a USB 2.0 port (USB models). Use the File/Configure command to establish communications with the programmer.

Tried to use PCI express parallel port with VMWare. Got this (BIOS: bidirectional):

"programmer site 1 did not respond to reset"

VM performance very poor even before launching BP software. Gave up and went to real windows system

Hooked up EC1PECPS to native Windows XP t61 system and wokred fine.

User's Guide / The Engineer's Programmer

Dying to read it? Well you probably don't want to: LN: its not super exciting, documents some bpdos stuff and basic setup

But feel free to throw out a line if you *really* want it scanned for some bizarre reason


Site

Trying to understand relationship between models and site numbers

Note: early models didn't distinguish site vs serial. If both aren't indicated, its probably the same

Site DOM Vendor Model Note
1056 BP PLD-1128
1631 BP EP-1140
4653 BP EP-1
5172 BP EP-1
7998 BP EP-1
11193 BP 1200
12716 BP 1200
15278

15281

BP 2200/240x4M4
17243 BP 1148
17598

17602

Actel SS1-6
18679 2001-10-05 Actel SS1
18797

18800

BP 2200/240X4M4
19022

19026

BP 2100/84X4M4
19341

19341

BP 2200/240X2M4
22501 1999-12-15 Actel SS1
23007 BP 1400
25294

25297

BP 2200/240X4
26047

26050

BP 2000/84X4
28781 2001-10-12 BP 1600
30251 Actel SS2
31196 2003-07-07 Actel SS2
34346 2005-09-30 BP 1410
34681 Actel SS2
38211 2009-09-25 Actel SS3
39901 BP 1610

SS: Silicon Sculptor. SS1 => FP-ACTEL, SS2 => FP-ACTEL-II

Device Programming Language (DPL)

BP-3600 doc indicates this is the name of a high level language used for programming algorithms, introduced in 1987


http://www3.bpmmicro.com/web/helpandsupport.nsf/69f301ee4e15195486256fcf0062c2eb/bb22d83a95b7f1688625703e0062ae67!OpenDocument

very empty...


http://www3.bpmmicro.com/web/home.nsf/(web.news)/9A6F2919E23DEF85862571420052C045

March 31, 2006 — BP Microsystems, a leading supplier of device programming systems worldwide, announces it has revamped its Device Programming Language (DPL) algorithm development environment in BPWin to allow its over 100 semi-house partners to co-develop and test algorithms for new devices


http://www3.bpmmicro.com/web/home.nsf/(web.news)/A80A7F8654FDF5CD86256FC80081C28C

Unlike other companies that have rewritten programming algorithms for each new programmer model, BP’s newest generation of programmers runs the same device independent programming algorithm used by all BP’s programmers. Having invented Device Programming Language (DPL) in 1987, BP has been able to introduce generation after generation of improved products without the delays and bugs associated with algorithm rewrites. For compatibility, the new programmers incorporate the same proven pin drivers and socket modules used by the full range of BP programmers.


BPM Overview, March 2010

All algorithms written in proprietary Device Programming Language (DPL)

Because all of our programmers use DPL we are able to instantly support existing algorithms on new products (unlike other 3rd party programmers who must start over writing new algorithms whenever they introduce new products)


API

Looks like it might be COM component. Not familiar with these to quickly play with it

Retrieved from "https://proghq.org/w/index.php?title=BP_Microsystems&oldid=704"