Franc Zabkar wrote in message
...
On Wed, 5 May 2010 08:56:58 +0100, "N_Cook" put
finger to keyboard and composed:

that 1K5 will have to go back in , It is the first point of recognition
for
USB linking. Next to find why DISCON is permanently H.

My understanding is that the pullup resistor on D+ signals to the host
(your PC) that a USB device has been plugged in. The host then
attempts to enumerate (ie identify) the device.

If the device takes too long to go through its POST and initialisation
routines, then the host may time out. In such cases the device may
implement an active pullup which is disabled during its POST. When the
device is ready, the pullup resistor is enabled, allowing enumeration
to begin.

AIUI, the normal state of DISCON# is high.

See this EZ-USB Development Board (circuit on pages 5 & 6):
http://www.minford.ca/MF3001EZUSBManual.pdf

I found this detailed document:

The EZ-USB USB Integrated Circuit Technical Reference:
http://www.digchip.com/data/115/115-00027-0-AN2121S.pdf

It states that EZ-USB devices can power up in RAM-only mode, in which
case the host downloads runtime code into the 8051 CPU's internal 8K
RAM. During this time the device identifies itself as a "Default USB
Device". After the code has been downloaded, the device disconnects
and then reconnects, this time renumerating as the device defined
within the downloaded code.

Page 41 describes the EA (external access) pin. I think this may be
the key to how the device behaves. The tech ref also talks about mask
ROMed versions. Perhaps there is a way to force the EZ-USB chip into
RAM-only mode??? If so, then this will remove any corrupt firmware
from the equation. You could then use UVCView to see how the device
enumerates under these circumstances.

You could also disconnect the serial EEPROM, if any. The EEPROM would
contain Product and Vendor IDs for the manufacturer of the mixer. If
the EEPROM is absent, then the EZ-USB chip will ID with the PID and
VID of 0x0547 (Cypress Semiconductor) and 0x2131 (EZ-USB),
respectively.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

I got back to this today. Saved to disc the existing (corrupted ?) data in
the serial EEPROM and cut the SDA line to the Ez-usb chip.
The EZbus mixer is no longer "Becoming Ezbus" and a blank screen.
But windows recognises a USB device connected and by UVCView/USB view the
USB is working up to the USB chip , reading

---===Device Information===---

ConnectionStatus:
Current Config Value: 0x00 - Device Bus Speed: Full
Device Address: 0x00
Open Pipes: 0
*!*ERROR: No open pipes!

===Device Descriptor===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0100
bDeviceClass: 0xFF - This is a Vendor Specific Device
bDeviceSubClass: 0xFF
bDeviceProtocol: 0xFF
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor: 0x0547idProduct:
0x2131
bcdDevice: 0x0004
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x01

ie Cypress VID/PID

Where to now? presumably forcing a pipe somehow

I'm thinking out in wwwland must be some general Cypress utility for
transfering minimal data into their chippery to redesignate VID/PID
pipe/endpoints etc.
Put a switch in the SDA line , leave open at power up , so USB designated
Cypress, then after 3 seconds when clock line is high close the switch. Then
upload something to the memory, enough to redisignate the USB identity. Then
power down and power up and transfer the mixer firmware.

Anyone familiar with this sort of utility
EZ Loader Custom USB Firmware Loader Driver
http://www.cypress.com/?docID=4503
just to rejig USB ident to then use the firmware transfer for the particular
application ? here a digital mixer that is otherwise dead from corrupted
firmware transfer.

eg p4
" 8. Before you can use your new firmware driver you will need
to bind it with your device. This is done by loading the
serial EEPROM with the VID/PID combination defined in
the INF file you create for your custom USB device. This
is the first of two VID/PID combinations your device will
use. When the VID/PID in the EEPROM is reported to the
host, the host will invoke the wdgtldr.sys which loads your
firmware. To load your VID/PID combination in the serial
EEPROM open the EZ-USB Control Panel, ensure the
Target Field matches your target device, and download
the Vend_ax.hex example. "

On Thu, 20 May 2010 14:17:20 +0100, "N_Cook" put
finger to keyboard and composed:

I got back to this today. Saved to disc the existing (corrupted ?) data in
the serial EEPROM and cut the SDA line to the Ez-usb chip.
The EZbus mixer is no longer "Becoming Ezbus" and a blank screen.
But windows recognises a USB device connected and by UVCView/USB view the
USB is working up to the USB chip , reading

---===Device Information===---

ConnectionStatus:
Current Config Value: 0x00 - Device Bus Speed: Full
Device Address: 0x00
Open Pipes: 0
*!*ERROR: No open pipes!

===Device Descriptor===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0100
bDeviceClass: 0xFF - This is a Vendor Specific Device
bDeviceSubClass: 0xFF
bDeviceProtocol: 0xFF
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor: 0x0547idProduct:
0x2131
bcdDevice: 0x0004
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x01

ie Cypress VID/PID

Where to now? presumably forcing a pipe somehow

You already know more about USB than I do. :-)

However, I wonder if the data in the serial EEPROM are checksummed, in
which case it may be possible to confirm its integrity.

ISTM that you've at least confirmed that the EZ-USB chip has sanity,
if you weren't already convinced by your scope tests.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Franc Zabkar wrote in message
...
On Thu, 20 May 2010 14:17:20 +0100, "N_Cook" put
finger to keyboard and composed:

I got back to this today. Saved to disc the existing (corrupted ?) data
in
the serial EEPROM and cut the SDA line to the Ez-usb chip.
The EZbus mixer is no longer "Becoming Ezbus" and a blank screen.
But windows recognises a USB device connected and by UVCView/USB view the
USB is working up to the USB chip , reading

---===Device Information===---

ConnectionStatus:
Current Config Value: 0x00 - Device Bus Speed: Full
Device Address: 0x00
Open Pipes: 0
*!*ERROR: No open pipes!

===Device Descriptor===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0100
bDeviceClass: 0xFF - This is a Vendor Specific
Device
bDeviceSubClass: 0xFF
bDeviceProtocol: 0xFF
bMaxPacketSize0: 0x40 = (64) Bytes
idVendor: 0x0547idProduct:
0x2131
bcdDevice: 0x0004
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x01

ie Cypress VID/PID

Where to now? presumably forcing a pipe somehow

You already know more about USB than I do. :-)

However, I wonder if the data in the serial EEPROM are checksummed, in
which case it may be possible to confirm its integrity.

ISTM that you've at least confirmed that the EZ-USB chip has sanity,
if you weren't already convinced by your scope tests.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.


Switching SDA line after 3 seconds still keeps the USB open but wrong
identity for the mixer firmware installer. Not had a chance to connect it up
to a pc but I'm assuming it will not software connect if expecting the mixer
VID/VID/endpoint. When next I have some time I will load the installer.exe
into hex_reader_XVI32 and see if I can swap VID / PID hex-codes to fool it
into thinking it is an EZbus rather than EZusb it is hooked to. Probably
checksummed there but simple enough to try.

On Sat, 22 May 2010 07:49:28 +0100, "N_Cook" put
finger to keyboard and composed:

Switching SDA line after 3 seconds still keeps the USB open but wrong
identity for the mixer firmware installer. Not had a chance to connect it up
to a pc but I'm assuming it will not software connect if expecting the mixer
VID/VID/endpoint. When next I have some time I will load the installer.exe
into hex_reader_XVI32 and see if I can swap VID / PID hex-codes to fool it
into thinking it is an EZbus rather than EZusb it is hooked to. Probably
checksummed there but simple enough to try.

You may be interested in IICUNI. It is a utility that controls I2C
devices from a PC parallel port. I suspect that you could program the
serial EEPROM in-circuit if you keep the EZ-USB chip quiet by holding
down its reset pin.

http://web.archive.org/web/200605110...ogs/iicuni.rar

I believe the EZ-USB datasheet should tell you how to compute the
checksum.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Franc Zabkar wrote in message
...
On Sat, 22 May 2010 07:49:28 +0100, "N_Cook" put
finger to keyboard and composed:

Switching SDA line after 3 seconds still keeps the USB open but wrong
identity for the mixer firmware installer. Not had a chance to connect it
up
to a pc but I'm assuming it will not software connect if expecting the
mixer
VID/VID/endpoint. When next I have some time I will load the
installer.exe
into hex_reader_XVI32 and see if I can swap VID / PID hex-codes to fool
it
into thinking it is an EZbus rather than EZusb it is hooked to. Probably
checksummed there but simple enough to try.

You may be interested in IICUNI. It is a utility that controls I2C
devices from a PC parallel port. I suspect that you could program the
serial EEPROM in-circuit if you keep the EZ-USB chip quiet by holding
down its reset pin.

http://web.archive.org/web/200605110...ogs/iicuni.rar

I believe the EZ-USB datasheet should tell you how to compute the
checksum.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

I deRARified it and m/c translated the German readme.
3.1 and 95 , not NT, any idea if it would work under windows 98 ?

So perhaps dig out win95 disc , make up the 7405 bridge, fire up iicuni and
from the Ezusb pdf ,fro

5.7 Serial EEPROM Present,FirstByte is 0xB0
Table 5-7. EEPROM Data Format for"B0"Load

0 0xB0
1 VendorID(VID)L
2 VendorID(VID)H
3 ProductID(PID)L
4 ProductID(PID)H
5 DeviceID(DID)L
6 DeviceID(DID)H
7 Notused

and
digital mixer VID 0B45 , PID_0001&MI_00
perhaps just loading hex version of
B0450B01000000 into the first 7 bytes instead of the current corrupted
087910B004BCC0.....

(I'm unsure about device ID at the moment)
is enough to start the ball rolling to do a firmware upload for the mixer

On Sun, 23 May 2010 15:11:35 +0100, "N_Cook" put
finger to keyboard and composed:

Franc Zabkar wrote in message
.. .

You may be interested in IICUNI.

http://web.archive.org/web/200605110...ogs/iicuni.rar

I deRARified it and m/c translated the German readme.
3.1 and 95 , not NT, any idea if it would work under windows 98 ?

I'm using Win98SE. I haven't constructed the interface circuit, so I
can't test IICUNI with any I2C devices, but FWIW it appears to run OK
in all other respects.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

On Mon, 24 May 2010 08:35:10 +0100, "N_Cook" put
finger to keyboard and composed:

So perhaps dig out win95 disc , make up the 7405 bridge, fire up iicuni and
from the Ezusb pdf ,fro

5.7 Serial EEPROM Present,FirstByte is 0xB0
Table 5-7. EEPROM Data Format for"B0"Load

0 0xB0
1 VendorID(VID)L
2 VendorID(VID)H
3 ProductID(PID)L
4 ProductID(PID)H
5 DeviceID(DID)L
6 DeviceID(DID)H
7 Notused

and
digital mixer VID 0B45 , PID_0001&MI_00
perhaps just loading hex version of
B0450B01000000 into the first 7 bytes instead of the current corrupted
087910B004BCC0.....

(I'm unsure about device ID at the moment)
is enough to start the ball rolling to do a firmware upload for the mixer

If all you want to do is to verify that the EEPROM data are intact,
then wouldn't it be simpler to just compute a checksum over the
contents?

Could you upload the PROM dump so that we could have a look at it?

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Franc Zabkar wrote in message
...
On Mon, 24 May 2010 08:35:10 +0100, "N_Cook" put
finger to keyboard and composed:

So perhaps dig out win95 disc , make up the 7405 bridge, fire up iicuni
and
from the Ezusb pdf ,fro

5.7 Serial EEPROM Present,FirstByte is 0xB0
Table 5-7. EEPROM Data Format for"B0"Load

0 0xB0
1 VendorID(VID)L
2 VendorID(VID)H
3 ProductID(PID)L
4 ProductID(PID)H
5 DeviceID(DID)L
6 DeviceID(DID)H
7 Notused

and
digital mixer VID 0B45 , PID_0001&MI_00
perhaps just loading hex version of
B0450B01000000 into the first 7 bytes instead of the current corrupted
087910B004BCC0.....

(I'm unsure about device ID at the moment)
is enough to start the ball rolling to do a firmware upload for the mixer

If all you want to do is to verify that the EEPROM data are intact,
then wouldn't it be simpler to just compute a checksum over the
contents?

Could you upload the PROM dump so that we could have a look at it?

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

The first block of the corrupted EEPROM is
(Maybe decoded erroneously as serial converted to parallel via 2x 4015 and
clock divided by 16 by 4 stages of a 4020 and loaded into Logic analyser on
negative going transitions). It is consistent thats all I can say

S0000 087910B004BCC04B070420001828C000F0B20401604111AEF5 81030420009615
S0010 C000D0B1AD01101000BC73400464889710084002B051000105 803CB5254284CA
S0020 A81C6CE1823C0B08290280542CE0554003A40FC5FE151F0111 480548848751F0
S0030 200105200F06040004000208BF06707309BE20C10DA42100A2 05CB010A5B8A05
S0040 906006122000140440020640810431103D6C04074853B50AD4 E40C80C04102B3
S0050 436B386004064283542878DE4F001215980429902F04943044 A9028DD0040B1C
S0060 80C90C21E1793A04440519E08208EF2281CE00081A34E1012B 3C1D0771C55262
S0070 E0804E500215DA050BA02E0380D340B8B02B0102200AF0B80C 908AC801489037
S0080 49E9970078E46F005811C02E02C0AE00111101022442F0EA0E C004C01EBCB888
S0090 AD3C21005B795703E946060246C10124C1432278451778E9F1 C2050487D70608
S00A0 4080C33B8001C81501024020B106604074F981800ACA0C0418 403C403340F48A
S00B0 441CF0F08008F93B9B022D200502000072E06C800C04800008 D8004081570102
S00C0 1060040260D7FE405E0108B0805D08405BE700C90304E00A72 B9021453183C78
S00D0 08004406070225E007011008110220429E58A5227422100E78 08808820891EB9
S00E0 C31A2E0CE85501BE00E005022DC0020C071DB91AB80A60203C FE41C7DA102F00
S00F0 FA210E0180818F7281570260204184AA075EC88914BCCA2988 00B52079F2274F
S0100 F4E44F9EE2C99E3CC9933A79952779F2274FF4E44F9EE2C99E 3CC9933A799527
S0110 79F2274FF4E44F9EE2C99E3CC9933A79952779F2274FF4E44F 9EE2C99E3CC993
S0120 3A79952779F2274FF4E44F9EE2C99E3CC9933A79952779F227 4FF4E44F9EE2C9
S0130 9E3CC9933A79952779F2274FF4E44F9EE2C99E3CC9933A7995 2779F2274FF4E4
S0140 4F9EE2C99E3CC9933A799027010023C250006100E0D500BC19 00087880070390
S0150 20600C044381640D8CB8899038100D87790221E41206400080 948F8210118F3A
S0160 802478E4136BBD30A05706F801800A08AE0010301B74E26AE0 2806927E949A28
S0170 780818711154031227A8E4E60E9F20610A9E89133871152771 E2274EE4C44E9C
S0180 C2899A3889133871152771E2274EE4C44E9CC2899A38891338 71152771E2274E
S0190 E4C44E9CC2899A3889133871152771E2274EE4C44E9CC2899A 38891338711527
S01A0 71E2274EE4C44E9CC2899A3889133871152771E2274EE4C44E 9CC2899A388913
S01B0 3871152771E2274EE4C44E9CC2899A3889133871152771E227 4EE4C44E9CC289
S01C0 9A38881004010020000000000000240002E081043190373C4D 4071DE258F42C4
S01D0 4082184801240BA8BA7E7D400674476EA5E0041EC2210E87E1 41B86418C07A06
S01E0 B683D0EA2F194278519F20000A06F11737CE3080FB6CE4DF02 D5DE02E903A87D
S01F0 1DC50690E06CEF10A81E16D09EBAC15B28781001110831418B 18C8034E0006A0
S0200 00C2A0153C0111800068803A0001184899258840821990F04D 122002146640C2
S0210 2A4906033AB308001087610A518C780647840200401D311008 00380048043127
S0220 881A0051022081003310A406A0D3016A20E00B04A381F43440 9E08C005016920
S0230 2A0D80A504AE40001C084F03C02B807A18320612110004E887 511C080001D061
S0240 A50610600574C7A8C2E080110C0981843A03AB1E00A11BE540 85907A051CCC21
S0250 9E8EDA6B1F4828072C0CD2A3E0700E4172D45E03F2A88F62AC 073F83030FF002
S0260 4F400694C23FD2310872CD250702402E3B1C6040741981809A CB2707100020BE
S0270 A0E07D2CC381228481B402A12F57F835107A2001CC24609942 2C808013C3385A
S0280 E1377CE2E26EEFF8000AC8C180AB00F3240905E0690000CF0D 00810EACE1823C
S0290 08203A5F00F01000040014D8AF4E42E5040080211B6AC52379 006084BE5CE097
S02A0 00F4000840BA2B7064977840206DCD24C3810214800810480A 19B0511A38D442
S02B0 468A250668B4C70D0809B1222963242035A66EDE62DEEC888A 9680981B3760F3
S02C0 397535266E8ACE4D200400002A2800010830540210A0090000 00000400090209
S02D0 8000104000010060221A2080000000000A2080016030010420 00050660000004
S02E0 40820000000008400101710001026401020448002200B80000 10002500400108
S02F0 20400E0040802A00840008C000180080011220404C1C800010 48000000000002
S0300 2020220E20C0482C8080110981040017000010A00000400002 04C20102388905
S0310 10102401900050020040049400000A20800038300000610004 02804404040080
S0320 02108904282000012080090040C00428408100000100181005 0A204022128040
S0330 0004800022008400087001240060010660410C240010000080 0060800004F7EF
S0340 0100018000060000FF12E01F91400100000000000000000000 00000000001842
S0350 0108D594CA582902344035A505060000060CC6800A18800104 04408000080000
S0360 000000000058000000000000B0F20000C0879A38020D2E5000 00000000000000
S0370 0000000000002040040010200102001C00053B7AB067000000 0000000A000000
S0380 00441840007A0340000067CF00000000000000000000000000 00000000000000
S0390 4B9982911210A9430020302E00000000000000008540004B58 C250600A4AA041
S03A0 0618D280121B96723A008707F0F00416E0E17FFFFD073F58C1 C2961630F9C9BF
S03B0 FEFDEF1FFF60070B581AC4EA56FFFDF7BF7FFB831F2C60691F 82FA433F1DFCF7
S03C0 52FF87EC58D07081023220000A60A1C00011078318300D8760 01162DDA61813C
S03D0 0880055828704004C220060CC3A1B8004317D718201B046000 160CDC10813108
S03E0 C03F0000030000F80B00A9011300B0022A55A003007685A500 9400C07FB00080
S03F0 0000F00F00000B0000FE0F00EC0101002260C5840090060C00 803F00C0000718
S0400 E000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0410 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0420 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0430 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0440 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0450 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0460 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0470 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0480 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0490 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S04A0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S04B0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S04C0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S04D0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S04E0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S04F0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0500 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0510 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0520 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0530 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0540 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0550 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0560 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0570 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0580 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0590 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S05A0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S05B0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S05C0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S05D0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S05E0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S05F0 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0600 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0610 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0620 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0630 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0640 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0650 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF
S0660 FFFFFFFFFFFFFFFFFFFFFEFFFFFFFEFFFFFFFEFFFFFFFFFFFF FF418C0B000D8A
S0670 000000FC0B00000000000020000020000000000000000000EA A2000050240000
S0680 20000000000000140000001800000020000020000000000000 0000000100394D
S0690 AC477CE817A9F8EAA81EEC215EA202AABB7FACD349750340EF 0041C322FC9404
S06A0 EA933D619895098733A40624079F8200CE1301903E78AD7611 004007FBC00E1A
S06B0 04800E3881AB320005574978250F87E8C712F0C81E0391EBB9 4BA9843AF20782
S06C0 7230098FCA89011D69980024798569F20282F0000700F0C09E 23D0992D3C94A7
S06D0 7800800540F00112E0915F3600F80000000000000000000000 00000000000000
S06E0 000005007FBE3102052A4DCB020C09ADDA1300156D7548E406 CF2B60240106C0
S06F0 DF0300A2820795107D12054305A0CE1FE8C0DE800000000000 00000000000000
S0700 00000000000000000000FD077FFFF7EFFFFEEFDFFEFDDFBF00 F8000000000066
S0710 0000001E0000000000000000800025407F000260000000C000 00008080020000
S0720 000000000000000000000601D1A0301A000000000000010078 F0070FF0E00F1E
S0730 E0C10000FD177FFFF7EFFFFEEFDFFEFDC0BF00000000000000 00000000000000
S0740 00000000000000000000000000000000000000009001191000 191000010000A0
S0750 00000B0FF6518E3CABC2BA5491A711EF9761130A000CFED18F BCE191A229B586
S0760 24F7244278FCEF1FC2BD8FBC19A01B571C226375B7AC209822 5A8610D190B1C2
S0770 2D3CE9863AF28647E4F0471E00D04E3C4B91BC215D2059F824 8E24E4880AA820
S0780 5A09E0A3137C1D41220724EF24E44FDCFA89453F61E0380C15 877AE200071908
S0790 4D022218DF800868105A702009042001B2F04F001CE49B0B40 4A803910100402
S07A0 46404A088009027C800012109A0258543CAC334005000D0D02 0C102E11100011
S07B0 C0E37901258F04E8008F10C84E2D8890027111870078470E72 6A4D8472258E88
S07C0 0B108100104001B8A70EEA140ED702B0029DB81A0001108002 003340F4020005
S07D0 E8B8D3000A082E7E103001BB50400544474C06080E35E1913A 28A1863AF22786
S07E0 14D40B4FE20D50B9C0113B0780444212A521A5C06A5094099E 83C123A0621D54
S07F0 78E6038FC504011246C114BC8800000101803AF21780BA4400 0A0640009ED2C2

Franc Zabkar wrote in message
...
On Sun, 23 May 2010 15:11:35 +0100, "N_Cook" put
finger to keyboard and composed:

Franc Zabkar wrote in message
.. .

You may be interested in IICUNI.


http://web.archive.org/web/200605110...ogs/iicuni.rar

I deRARified it and m/c translated the German readme.
3.1 and 95 , not NT, any idea if it would work under windows 98 ?

I'm using Win98SE. I haven't constructed the interface circuit, so I
can't test IICUNI with any I2C devices, but FWIW it appears to run OK
in all other respects.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.


Agreed seems to work under 98SE , putting a basic tester on the printer port
showed no flickering LEDs but then nothing on the other end

Putting wrong string format in the form and returning error box saying
ist kein gültiger integerwert
probably means
is not of integer value

On Wed, 26 May 2010 17:14:34 +0100, "N_Cook" put
finger to keyboard and composed:

Franc Zabkar wrote in message
.. .
On Mon, 24 May 2010 08:35:10 +0100, "N_Cook" put
finger to keyboard and composed:

So perhaps dig out win95 disc , make up the 7405 bridge, fire up iicuni
and
from the Ezusb pdf ,fro

5.7 Serial EEPROM Present,FirstByte is 0xB0
Table 5-7. EEPROM Data Format for"B0"Load

0 0xB0
1 VendorID(VID)L
2 VendorID(VID)H
3 ProductID(PID)L
4 ProductID(PID)H
5 DeviceID(DID)L
6 DeviceID(DID)H
7 Notused

and
digital mixer VID 0B45 , PID_0001&MI_00
perhaps just loading hex version of
B0450B01000000 into the first 7 bytes instead of the current corrupted
087910B004BCC0.....

(I'm unsure about device ID at the moment)
is enough to start the ball rolling to do a firmware upload for the mixer

If all you want to do is to verify that the EEPROM data are intact,
then wouldn't it be simpler to just compute a checksum over the
contents?

Could you upload the PROM dump so that we could have a look at it?


The first block of the corrupted EEPROM is
(Maybe decoded erroneously as serial converted to parallel via 2x 4015 and
clock divided by 16 by 4 stages of a 4020 and loaded into Logic analyser on
negative going transitions). It is consistent thats all I can say

S0000 087910B004BCC04B070420001828C000F0B20401604111AEF5 81030420009615

ISTM that your EEPROM dump must be in error.

According to section 5.6 (page 83) of the technical reference, the
first byte of the serial EEPROM can either be 0xB0 or 0xB2. If it is
anything other than these, or if an EEPROM is not present, then the
EZ-USB chip identifies itself with a VID of 0x0547 (Cypress
Semiconductor) and a PID of 0x2131 (EZ-USB).

Otherwise, if byte 0 is 0xB0, then the chip enumerates with the
VID/PID stored in the EEPROM. The host (ie your PC) then downloads
code into the EZ-USB's RAM and starts the 8051 CPU. The serial EEPROM
in this case would only need to store 7 bytes, so chips such as the
24LC00 would be used.

If byte 0 is 0xB2, then the EZ-USB core loads the EEPROM data into
EZ-USB RAM.

The datasheet states that ...

Serial EEPROM data can be loaded into two EZ-USB RAM spaces only.
• 8051 program/data RAM at 0x0000-0x1B40.
• The CPUCS register at 0x7F92

This suggests to me that the maximum ROM size need only be 6976 bytes
(= 0x1B40).

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Franc Zabkar wrote in message
...
On Wed, 26 May 2010 17:14:34 +0100, "N_Cook" put
finger to keyboard and composed:

Franc Zabkar wrote in message
.. .
On Mon, 24 May 2010 08:35:10 +0100, "N_Cook" put
finger to keyboard and composed:

So perhaps dig out win95 disc , make up the 7405 bridge, fire up
iicuni
and
from the Ezusb pdf ,fro


The datasheet states that ...

Serial EEPROM data can be loaded into two EZ-USB RAM spaces only.
. 8051 program/data RAM at 0x0000-0x1B40.
. The CPUCS register at 0x7F92

This suggests to me that the maximum ROM size need only be 6976 bytes
(= 0x1B40).

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Could well be in error. Old bit of homebrew and have not used the logic
analyser for 10 years. Until I find time to cobble together the 7405 cct and
check with a X24C04 (plenty to hand) writing and reading known code via pc
and logic analyser I cannot be certain. Its a back-burner job

Found time to build the 7405 interface today.
Googling around the subject beforehand, came across this
http://oocities.com/microappnotes/UARTAVR.htm

It was mirrored from Geocities in october 2009.

text only
http://web.archive.org/web/200806240....com/microappn
otes/UARTAVR.htm
note
www.nutsvolts.com not www.ntsvolts.com

other ref maybe (not read yet)
Programming The 54¢ Micro
by G. Y. Xu
Microcontroller/PIC 2006-02 (Program files and code listing)
http://www.nutsvolts.com/media-files...A2%20MICRO.zip

On Sun, 6 Jun 2010 09:29:37 +0100, "N_Cook" put
finger to keyboard and composed:

Found time to build the 7405 interface today.
Googling around the subject beforehand, came across this
http://oocities.com/microappnotes/UARTAVR.htm

That article talks about bit-banging an RS232 software UART for a
UART-less uC.

The I2C bus and protocol is completely different. It doesn't frame its
bytes with start and stop bits. AIUI, each byte is acknowledged by the
recipient with an ACK bit. Furthermore, traffic is bidirectional,
along a single wire, ie no separate Tx/Rx wires. Commands and data are
both sent down the same wire.

ISTM, that you are monitoring all I2C traffic, not just the EEPROM
data. You may like to read a datasheet for a common I2C serial EEPROM
chip.

24AA00/24LC00/24C00:
http://ww1.microchip.com/downloads/e...Doc/21178E.pdf

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Franc Zabkar wrote in message
...
On Sun, 6 Jun 2010 09:29:37 +0100, "N_Cook" put
finger to keyboard and composed:

Found time to build the 7405 interface today.
Googling around the subject beforehand, came across this
http://oocities.com/microappnotes/UARTAVR.htm

That article talks about bit-banging an RS232 software UART for a
UART-less uC.

The I2C bus and protocol is completely different. It doesn't frame its
bytes with start and stop bits. AIUI, each byte is acknowledged by the
recipient with an ACK bit. Furthermore, traffic is bidirectional,
along a single wire, ie no separate Tx/Rx wires. Commands and data are
both sent down the same wire.

ISTM, that you are monitoring all I2C traffic, not just the EEPROM
data. You may like to read a datasheet for a common I2C serial EEPROM
chip.

24AA00/24LC00/24C00:
http://ww1.microchip.com/downloads/e...Doc/21178E.pdf

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.


Don't know whether using 74LS05 rather than L or salvaged X24C04P or my
breadboarding , but not getting very far.
Selected LPT1 in iicuni.exe
Philips profile just gave error SDA low with any button presses/settings or
even disconnected
In MIR profile and trying various settings of BaseAdr+0 /2 of 00,FF,CF,DF
SDA normally L would go H momentarily pulsed on pressing I2Clist on all of
those BaseAdr settings
SCL would go H or L but not osc on various of those settings and button
pushes

My translation of I2Clist function
'I2C List'-Button: To determine which devices exist on the I2C bus
are. Sends all the even device addresses from (0,2,4 ... FE)

maybe problem something to do with win 98SE or this
"http://www.boerde.de/~matthias/delphi/

IIC Bus - Universal V 1.2 a program (Executables - Source) to control
I²C-Bus devices at the parallel port, for any passive I²C-Bus Interface
(e.g. Philips, Eagle-files and pdf), with E²PROM editor. Price winning tool
(3th national price in Elektor's International Electronic Software
Competition 1996). If you want to use the sources you need the component
DStamp too. Attention: Use "Default Settings for output":BaseAdr+2 = DF with
newer MoBo's. For Win2k or XP you need userport.sys (cached here)."