BPM WWAVUSBEPP - Revision history

Mcmaster at 03:26, 5 July 2019

2019-07-05T03:26:16Z

← Older revision		Revision as of 03:26, 5 July 2019
Line 79:		Line 79:

	2019-07-01: new PCB in KiCAD: https://github.com/ProgHQ/bpm-usb/pull/2		2019-07-01: new PCB in KiCAD: https://github.com/ProgHQ/bpm-usb/pull/2

			Failed mcmaster adapter: https://twitter.com/johndmcmaster/status/1046057604085157889

			I have a report of someone getting this to work using shorter cables (and even have a pic of their setup). Are they using the same pinout as me?

	[[File:mcmaster_bpm_wwavusbepp_top.jpg\|frameless]]		[[File:mcmaster_bpm_wwavusbepp_top.jpg\|frameless]]

Mcmaster at 03:12, 5 July 2019

2019-07-05T03:12:33Z

← Older revision		Revision as of 03:12, 5 July 2019
Line 77:		Line 77:

	= PCB overview =		= PCB overview =

			2019-07-01: new PCB in KiCAD: https://github.com/ProgHQ/bpm-usb/pull/2

	[[File:mcmaster_bpm_wwavusbepp_top.jpg\|frameless]]		[[File:mcmaster_bpm_wwavusbepp_top.jpg\|frameless]]

Mcmaster at 02:23, 5 July 2019

2019-07-05T02:23:34Z

← Older revision		Revision as of 02:23, 5 July 2019
Line 19:		Line 19:
	[http://www3.bpmmicro.com/web/helpandsupport.nsf/69f301ee4e15195486256fcf0062c2eb/c4c2dac08101795c8625703e0062bde8/$FILE/Programmer Site USB 2.0 Adapter FAQ.doc]		[http://www3.bpmmicro.com/web/helpandsupport.nsf/69f301ee4e15195486256fcf0062c2eb/c4c2dac08101795c8625703e0062bde8/$FILE/Programmer Site USB 2.0 Adapter FAQ.doc]

	* 2.4 Mb/s to 9.0 Mb/s potential speed ~~upgrade~~		* 2.4 Mb/s to 9.0 Mb/s potential speed upgradef
	* 14. What programming site models will this work with?		* 14. What programming site models will this work with?
	** All EPP programmers. This encompasses 6th-gen and 7th-gen.		** All EPP programmers. This encompasses 6th-gen and 7th-gen.
Line 34:		Line 34:
	[https://www.febo.com/pipermail/time-nuts/2013-January/073818.html]		[https://www.febo.com/pipermail/time-nuts/2013-January/073818.html]

	>> All I have is an Actel Silicon Sculptor 3, also made by BP Micro,>> that looks like the BP-1710 (with the 'START' button) but connects>> via a USB port. On the main PCB of the BP-1600 and the SS3 are two,>> 2 row, 26 pin, connectors, one toward the back edge of the PCB toward>> the back panel and the other just inside the first connector. The>> inside connector directly connects to the parallel port on the back>> of the BP-1600. On the SS3, there is a small PCB that plugs into the>> same connector, takes a power input, and also has 6 pin connections>> to the other 26 pin connector. This small PCB has a USB connector>> that is> connected to the back of the SS3 as the USB connection.>>		>> All I have is an Actel Silicon Sculptor 3, also made by BP Micro,
			>> that looks like the BP-1710 (with the 'START' button) but connects
			>> via a USB port. On the main PCB of the BP-1600 and the SS3 are two,
			>> 2 row, 26 pin, connectors, one toward the back edge of the PCB toward
			>> the back panel and the other just inside the first connector. The
			>> inside connector directly connects to the parallel port on the back
			>> of the BP-1600. On the SS3, there is a small PCB that plugs into the
			>> same connector, takes a power input, and also has 6 pin connections
			>> to the other 26 pin connector. This small PCB has a USB connector
			>> that is> connected to the back of the SS3 as the USB connection.

	Other:		Other:

Mcmaster at 02:22, 5 July 2019

2019-07-05T02:22:03Z

← Older revision		Revision as of 02:22, 5 July 2019
Line 1:		Line 1:
	[[Category_BPM]]		[[Category_BPM]]

			[[File:mcmaster_bpm_wwavusbepp_top.jpg\|frameless]]


	= Background =		= Background =
Line 42:		Line 45:

	= Programmer compatibility =		= Programmer compatibility =

			[[File:mcmaster_bpm_bp-1410_mb_usb_off.jpg\|frameless]]
			[[File:mcmaster_bpm_bp-1410_mb_usb_on.jpg\|frameless]]

	Trying a 1600 with the adapter under 5.33.0 (last version to support parallel) worked fine. However, under 5.47.0 (newest release version as of today):		Trying a 1600 with the adapter under 5.33.0 (last version to support parallel) worked fine. However, under 5.47.0 (newest release version as of today):
Line 63:		Line 69:
	= PCB overview =		= PCB overview =

	[[~~File_mcmaster_bpm_wwavusbepp_top~~.jpg\|frameless]]		[[File:mcmaster_bpm_wwavusbepp_top.jpg\|frameless]]
	[[~~File_mcmaster_bpm_wwavusbepp_btm~~.jpg\|frameless]]		[[File:mcmaster_bpm_wwavusbepp_btm.jpg\|frameless]]

	Above:		Above:

Mcmaster at 02:16, 5 July 2019

2019-07-05T02:16:56Z

Show changes

Mcmaster at 02:12, 5 July 2019

2019-07-05T02:12:40Z

Show changes

Mcmaster at 18:02, 13 September 2018

2018-09-13T18:02:26Z

← Older revision		Revision as of 18:02, 13 September 2018
Line 180:		Line 180:

	17 signal pins, 16 LA channels. Arbitrarily drop pin 8 in favor of hooking everything up linearly.		17 signal pins, 16 LA channels. Arbitrarily drop pin 8 in favor of hooking everything up linearly.

	~~= USB protocol =~~

	~~As of 2015-10-04 I have PoC serial number readout working. If the script isn't started from cold boot it gets a different response, but usually works~~

	~~== Bulk EP 2 ==~~

	~~Transactions look like this~~

	~~<code>~~
	~~bulkWrite(0x02, cmd)~~
	~~reply = bulkRead(0x86, 0x0200)~~
	~~</code>~~

	~~Sample replies below~~

	~~=== ''%%\%%''x00 ===~~

	~~Repeatable. TODO: is this issued anywhere?~~

	~~<code>~~
	~~00000000 08 A4 06 02 00 \|..... \|~~
	~~</code>~~

	~~=== ''%%\%%''x01 ===~~

	~~Repeatable. Code issues this and get 132-136 bytes back depending on where it is~~

	~~<code>~~
	~~00000000 08 80 A4 06 02 00 22 00 43 00 C0 03 00 08 F8 19 \|......".C.......\|~~
	~~00000010 00 00 30 00 80 00 00 00 00 00 C0 00 00 00 09 00 \|..0.............\|~~
	~~00000020 08 00 FF 00 E0 14 00 00 E8 14 00 00 84 1C 00 00 \|................\|~~
	~~00000030 EC 14 00 00 D0 19 FF FF C0 19 FF FF 00 00 F0 3C \|...............<\|~~
	~~00000040 FF FF 00 00 00 00 02 00 80 01 D0 01 02 00 01 00 \|................\|~~
	~~00000050 00 00 56 10 00 00 88 1B 00 00 6C 1B 00 00 00 00 \|..V.......l.....\|~~
	~~00000060 00 00 64 1B 00 00 66 1B 00 00 68 1B 00 00 44 1C \|..d...f...h...D.\|~~
	~~00000070 00 00 70 1B 00 00 30 11 00 00 34 11 00 00 74 1B \|..p...0...4...t.\|~~
	~~00000080 00 00 81 00 \|.... \|~~
	~~</code>~~

	~~<code>~~
	~~validate_read("\x08\x84\xA4\x06\x02\x00\x26\x00\x43\x00\xC0\x03\x00\x08\x10\x24"~~
	~~"\x00\x00\x30\x00\x80\x00\x00\x00\x00\x00\xC0\x00\x00\x00\x09\x00"~~
	~~"\x08\x00\xFF\x00\xC4\x1E\x00\x00\xCC\x1E\x00\x00\xB4\x46\x00\x00"~~
	~~"\xD0\x1E\x00\x00\xC0\x1E\x01\x00\xB0\x1E\x01\x00\x00\x00\x30\x55"~~
	~~"\x01\x00\x00\x00\x00\x00\x02\x00\x80\x01\xD0\x01\x02\x00\x01\x00"~~
	~~"\x00\x00\x56\x10\x00\x00\xA0\x25\x00\x00\x84\x25\x00\x00\x00\x00"~~
	~~"\x01\x00\x7C\x25\x00\x00\x7E\x25\x00\x00\x80\x25\x00\x00\x74\x46"~~
	~~"\x00\x00\x38\x11\x00\x00\x3C\x11\x00\x00\x40\x11\x00\x00\x44\x11"~~
	~~"\x00\x00\xC0\x1E\x00\x00\x85\x00", buff, "packet 259/260")~~
	~~</code>~~

	~~=== ''%%\%%''x02 ===~~

	~~Tried this to see what it would do. Caused unexpected responses to come back all the time and I had to power cycle the programmer~~

	~~=== ''%%\%%''x0E''%%\%%''x00 ===~~

	~~<code>~~
	~~validate_read("\x08\x3A\x00\x90\x32\xA7\x02\x2A\x86\x01\x95\x3C\x36\x90\x00\x1F"~~
	~~"\x00\x01\x00\xD6\x05\x01\x00\x72\x24\x22\x39\x00\x00\x00\x00\x27"~~
	~~"\x1F\x20\x00", buff, "packet 263/264")~~
	~~</code>~~

	~~Above: serial number readout. This may be some sort of EEPROM/flash read. This packet is dissected in some more detail in the S/N section with some correlations to bus traffic.~~

	~~=== ''%%\%%''x11''%%\%%''x10''%%\%%''x00 ===~~

	~~Not followed by read~~

	~~=== ''%%\%%''x11''%%\%%''x4E''%%\%%''x00 ===~~

	~~Not followed by read~~

	~~=== ''%%\%%''x43... ===~~

	~~<code>~~
	~~# Generated from packet 213/214~~
	~~bulkWrite(0x02, "\x43\x19\x00\x00\x00\x3B\x66\x1B\x00\x00\xFE\xFF\x3B\x64\x1B\x00"~~
	~~"\x00\xFE\xFF\x00")~~
	~~validate_read("\x08\xA4\x06\x02\x00", buff, "packet 215/216")~~
	~~</code>~~

	~~=== ''%%\%%''x43... ===~~

	~~<code>~~
	~~bulkWrite(0x02, "\x43\x19\x00\x00\x00\x11\xF0\xFF")~~
	~~big firmware load~~
	~~</code>~~

	~~=== ''%%\%%''x5A ===~~

	~~<code>~~
	~~validate_read("\x08\x80\x01\x00", buff, "packet 235/236")~~
	~~</code>~~

	~~=== ''%%\%%''x82 ===~~

	~~<code>~~
	~~validate_read("\x08\x16\x01\x00", buff, "packet 255/256")~~
	~~</code>~~

	~~=== ''%%\%%''xA6 ===~~

	~~<code>~~
	~~validate_read("\x08\x81\x01\x00", buff, "packet 243/244")~~
	~~</code>~~

	~~=== ''%%\%%''xDB ===~~

	~~<code>~~
	~~validate_read("\x08\x82\x01\x00", buff, "packet 251/252")~~
	~~</code>~~

	~~=== ''%%\%%''xE8... ===~~

	~~<code>~~
	~~bulkWrite(0x02, "\xE8\x00\x00\x00\x00\xFA\x5A\x83\xEA\x05\x81\xEA\x00\x00\x01\x00"~~
	~~"\x81\xFA\x00\x00\x01\x00\x74\x1F\xBB\x00\x00\x00\x00\xB9\x00\x00"~~
	~~"\x01\x00\x66\x8B\x02\x66\x89\x83\x00\x00\x01\x00\x83\xC2\x02\x83"~~
	~~"\xC3\x02\x83\xE9\x02\x75\xEB\x8C\xC8\x50\xB8\xF0\xFF\x01\x00\x50"~~
	~~"\x0F\x20\xC0\x0D\x00\x00\x00\x60\x0F\x22\xC0\x0F\x09\xC3")~~
	~~</code>~~

	~~No read~~

	~~=== ''%%\%%''xEA ===~~

	~~<code>~~
	~~bulkWrite(0x02, "\xEA\xCC\x64\x01\x00\x08\x00\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\x3F")~~
	~~</code>~~

	~~Not followed by read~~

	= 2015-09-27 =		= 2015-09-27 =

Mcmaster at 06:36, 13 September 2018

2018-09-13T06:36:57Z

← Older revision		Revision as of 06:36, 13 September 2018
Line 60:		Line 60:
	== CPCB12A Rev C motherboard (BP-1600, SS2) ==		== CPCB12A Rev C motherboard (BP-1600, SS2) ==

	Connect to TERM 1 (TERM 2 will not work)		Connect to TERM 1 (J11). TERM 2 (J12) will not work)

Mcmaster at 06:36, 13 September 2018

2018-09-13T06:36:24Z

← Older revision		Revision as of 06:36, 13 September 2018
Line 59:		Line 59:

	== CPCB12A Rev C motherboard (BP-1600, SS2) ==		== CPCB12A Rev C motherboard (BP-1600, SS2) ==

			Connect to TERM 1 (TERM 2 will not work)

Mcmaster at 06:31, 13 September 2018

2018-09-13T06:31:03Z

← Older revision		Revision as of 06:31, 13 September 2018
Line 50:		Line 50:

	I analyzed the USB packet traces for kicks to see what was happening. There are some minor differences (ex: later software chunks firmware load up smaller) but otherwise they are identical in purpose. However, the newer software seems to just give up at one point. My guess is that they removed the 1600 handling code, not just the parallel interface to it.		I analyzed the USB packet traces for kicks to see what was happening. There are some minor differences (ex: later software chunks firmware load up smaller) but otherwise they are identical in purpose. However, the newer software seems to just give up at one point. My guess is that they removed the 1600 handling code, not just the parallel interface to it.

			== CPCBD03223 Rev F (BP-1410) ==

			Original unit was from

			Power to J4


			== CPCB12A Rev C motherboard (BP-1600, SS2) ==


	= PCB overview =		= PCB overview =