Prev: will have to watch Cardinals game in b/w!
Next: Duracell dumbness
From: N_Cook on 19 Apr 2010 03:10
As nearly fully separated 3 lines of 28 control buttons I will try the small
subset of 378 combinations of adjascent pairs and the subset of adjascent
triplets of 3276, 3 button press combinations at power up, unfortunately
having to leave 10 seconds in between as longish 5s or so power-down/clear.

Then monitor the 3 clock lines to the CPLD and then try forcing the GSR
(Global Set Reset) pin

This other person's experience

"When connected to a PC computer via USB, the computer recognizes that a USB
device is found but cannot install it because it does not recognize what it
is. I went to the Event support site and downloaded the EZbusInstaller,
Firmware, ASIO update and XP update. Followed instructions to install the
Installer and that seemed to work, but when I try to run the Firmware it
does not recognize the unit and gets and error message that says no EZbus
connected. The Firmware instructions say that in order to run the file, the
unit has to be set so that the display is at the USB setting, by pressing
the System button and then the Next button several times. But it won't pass
the message that shows "becoming EZbus..." "

suggests that and this is a "pre-POST" problem but there is some variation
in LEDs lit on some button press combinations at power up , sometimes the
MIX LED lights on one pair of button presses , rather than the System+Audio
LEDs, as normal. Does this suggest a post-POST problem?

unlike from the EZbus FAQ having presumably gone past that and then hanging
at a blank screen but is initialising the USB function there.
" symptom:
I tried to update my EZbus firmware and, and now my EZbus LCD blank.
so;ution:
If for some reason the firmware updating process in interrupted (e.g., the
USB cable is accidentally removed, or you have a power failure), the EZbus
will not have the complete set of operating system instructions it needs to
function properly. The most obvious symptom of this condition is the blank
LCD.

1) If you are using the latest EZbus driver, you simply need to
double-click on the firmware updater to reload the firmware into the EZbus.
Note that you may have to do this several times, power-cycling the EZbus
in-between each attempt, before the firmware will be successfully loaded.
This is normal, and is not an indication of any additional problem.

2) If you are not using the latest EZbus driver, download the zipped
file (below) for your operating system (Win XP or ME) to your computer's
desktop, or a folder of your choosing

WinXP Firmware zip:
WinME Firmware zip:

3) Unzip the file, again to either your desktop or a folder of your
choosing.

4) Navigate to your computer's Device Manager and highlight USB Device.
Now go to Properties and click on Update Driver. Point the Update Wizard to
the desktop or to the folder into which you downloaded and unzipped the
files. At this point, Windows will reinstall the file EZbus.inf, which will
allow you to refresh the firmware, as in Step 1, above.

5) Once the EZbus.inf file has been installed, the listing within Device
Manager will now read EZbus-Needs Firmware Refresh, rather than USB Device.
At this point, follow the procedures outline in Step 1, above, until the
EZbus operating system is restored. "

Would it be worth trying to download firmware code and trying a USB link up?
going by the other person's experience, no point


From: N_Cook on 19 Apr 2010 05:16
2 and 3 button power-ups produced nothing. About 10MHz on the 3 CPLD clocks
and GSR goes high briefly about 3 seconds in then stays low. Whereto next ?
not graveyard / mule paddock surely


From: N_Cook on 20 Apr 2010 03:12
mike <mlightner(a)survivormail.com> wrote in message
news:9209ec55-2ae2-4aa4-8446-a97613678f43(a)x3g2000yqd.googlegroups.com...
>
>
> N_Cook wrote:
> > N_Cook <diverse(a)tcp.co.uk> wrote in message
> > news:hqhmlg$gas$1(a)news.eternal-september.org...
> > > <Meat Plow> wrote in message news:3me52r.nqj.19.2(a)news.alt.net...
> > > > On Mon, 19 Apr 2010 10:16:29 +0100, "N_Cook"
<diverse(a)tcp.co.uk>wrote:
> > > >
> > > > >2 and 3 button power-ups produced nothing. About 10MHz on the 3
CPLD
> > > clocks
> > > > >and GSR goes high briefly about 3 seconds in then stays low.
Whereto
> > next
> > > ?
> > > > >not graveyard / mule paddock surely
> > > > >
> > > >
> > > > Email Event and ask them if they know of anyone who might have more
> > > > information?
> > >
> > > Well I've sent the following but I somehow doubt anything useful in
reply
> > >
> > >
> Maybe they just changed their address, found this on the web:
>
> http://event1.com/contact.php
>
> they also have a different email on their support page.
>
> Mikel

reply for what its worth

"We no longer support the EZbus, everything I have is at this link:
http://eventelectronics.com/support.html "

named contact

I had monitored the wrong pins before, for the CPLD / TQ100 pinning
CLK1 is 22.58125MHz
CLK2 is 23.99700 MHz
CLK3 is logic low
so something else to explore, if CLK3 is absolutely necessary for CPLD
function


From: N_Cook on 20 Apr 2010 04:07
clocks presumably related sum and diff fashion with the crystals 22.579200
and 24.57600
the CLK3 seems to come from the USB chip with a 12MHz crystal associated
with it, will have to explore the Cypress datasheet


From: Chris Tansit on 20 Apr 2010 04:48
N_Cook said..
>clocks presumably related sum and diff fashion with the
>crystals 22.579200 and 24.57600 the CLK3 seems to come
>from the USB chip with a 12MHz crystal associated
>with it, will have to explore the Cypress datasheet

So no luck on the reset? It has stored config somewhere right?
If so it has to have some way of resetting a config then.

I'd still go with a flash but I would be hesitant to do that
without resetting first (if possible).
I've found most resets codes are unpublished.
Try to find out who the service agents were for them as well.

Two more things about the firmware.
If it does allow USB boot recovery (e.g. the firmware fails at some
point in post) it is either going to fix the problem 100% or due
to an underlined hardware problem do nothing.
Hopefully if its truly a proper boot recovery it works before the
code interfaces to the hardware.

I think either way software or a hardware hang flashing it
will not make you worse off if its your only option.



First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: will have to watch Cardinals game in b/w!
Next: Duracell dumbness