Hey…
I’m using my usb module in standlone operation and have a prob with the 1st midi i/o in that when a device is plugged in 1, it’s data goes straight OUT of midi out1 at the same time too, so it’s like a midi thru instead of an out…the 2nd midi i/o behaves fine…
Cheers
Dan
Hi Dan,
the firmware cannot forward incoming events to the output port by itself, so it must be a software routing issue (check your MIDI-Ox setup) or a direct feedback of the Rx/Tx signals at your board
Best Regards, Thorsten.
Hey T…
I checked the tx and rx connections with a dmm (infact i checked ALL connections) with a DMM and beep good…def not a midi-ox routing prob, I even monitered it on my new midimon box…
Could it be that I may ve using V1 firmware? I can’t remember which 1 I burnt the eeprom with…I’ve since tried to upload the 1.1 but I can’t get the module recognised in xp without the (already programmed) eeprom in…same prob I had before as I remember…
Why would the 2 midi i/o behave okay tho?
Best
Dan
Hi Dan,
I’m not sure about the firmware version, v1.0 worked fine under Windows ME, but didn’t work under Linux. So I rearranged the descriptors in v1.1.
But the descriptors cannot be the reason for the feedback.
> Why would the 2 midi i/o behave okay tho?
Totaly unsure, because the first has a bad soldering joint?
In the meantime I’m also using WinXP, the installation of the Cypress USB driver was successfull (but I used the original package from http://www.cypress.com — unfortunately 65 MB!), the MIDI ports are running w/o problems.
Best Regards, Thorsten.
In the meantime I’m also using WinXP, the installation of the Cypress USB driver was successfull (but I used the original package from http://www.cypress.com — unfortunately 65 MB!), the MIDI ports are running w/o problems.
Hey T, have u got a name for these drivers - even better a link to em…I can’t find em on the site
Cheers
Dan
yes, it’s well hidden :-/
-> Design Resources
-> Select “Developer Boards”, “Universal Serial Bus”, “USB Full Speed Peripherals”
-> Go
-> select “Developer Kit: AN2131-DK001 EZ-USB Development Kit”
-> Download “EZ-USB Development Tools V2.61.700” and install it
-> Unplug the EEPROM and reboot your PC
thereafter the cypress chip should be regognized and the Control Panel should work.
If you’ve more Windows experiences like me, could you please try another way: could you try to extract and install the driver from the package w/o starting the setup program? If this works, we could provide a smaller .zip file for other MBHP_USB users which only contains the driver itself
Best Regards, Thorsten.
Hey T,
Do you know what files you need out of the huge zip? I can
extract the appropriate files from the .cab and put them info
a .zip if that is helpful. I have SmashTV’s USB board but
haven’t sourced the parts for it yet so I haven’t installed the
driver…
—john.
Hey T…
Ye, managed to extract just the drivers - but still wont install the damn thing in xp…
mebbe if I could a pre-programmed eeprom of sum1 with the 1.1 firmware on ;p
Cheers
D
Hi Dan,
maybe it doesn’t install because you’ve tried too much before? Somewhere under “System Control -> Device Manager” it is possible to remove the driver which is assigned to the connected USB device. After doing this, disconnect/connect the module (you can also use the powerline jumper near by the USB socket) and WinXP should ask for the new driver again.
Best Regards, Thorsten.
maybe it doesn’t install because you’ve tried too much before? Somewhere under “System Control -> Device Manager” it is possible to remove the driver which is assigned to the connected USB device. After doing this, disconnect/connect the module (you can also use the powerline jumper near by the USB socket) and WinXP should ask for the new driver again.
Indeed - I know this and must of done it a hundred times…XP just wont install the usb module without the eeprom (which is already programmed with the firmware from b4) in the socket…
Comes up with ‘there was a problem installing the cypress eeprom missing driver’ and summin to do with .inf file - which is the driver file…
So, i’m pretty much consigned to the fact this usb module is only useful for 1 midi i/o
cheers
Dan
Had the same prob: With the EEPROM WinXP had no probs to recognize the MBUSB. Without exactly the same prob like you had (really weird …).
I went to a friend and tried it there (Win98). Guess!
Right: Without EEPROM everything ran perfect. I burned it and tried to install it there. Boom! Nope, won´t install it on Win98…
So: Try to burn the EEPROM on some older machine (Win98 worked out for me).
Greets
I’ve now uploaded a new package version of MBHP_USB which contains a .syx file with the V1.1 firmware
Just follow the instructions which are given in the README.txt
http://www.ucapps.de/mbhp/mbhp_usb_v1_1b.zip
Best Regards, Thorsten.
Hey T…
Yes, that eeprom mios core upload method worked fine 
(on a 24LC256 too) but still the prob is there :/. So it has to be connection somewhere…no idea where tho, been over n over it upteen times…
Cheers
Hi Dan,
do you see two Audio devices in MIDI-Ox or only one?
How did you connect your core module to the MBHP_USB? via MIDIbox Link or via optocouplers?
Best Regards, Thorsten.
Hey T…
do you see two Audio devices in MIDI-Ox or only one?
Two.
How did you connect your core module to the MBHP_USB? via MIDIbox Link or via optocouplers?
neither, i connect via regular midi cables - like a standalone midi interface…so optocouplers are stuffed in both the usb module and the cores (if a midibox is plugged in)
Cheers
Dan
alright, and what does happen when you rip up the track to TxD0 (pin #15) very near by the Cypress chip?
This is just a simple test to ensure that there isn’t a short between Rx and Tx, later you can patch this connection with a short piece of cable
Best Regards, Thorsten.
cut the track now i get no input on midi in 1
EDIT:
just checked midi-ox again and i’m gettin midi input - only its pretty random data…
cheers
D
So, now do the same with the Rx track, but cut it near by the Cypress chip and near by the optocoupler.
Use a cable to connect the optocoupler directly with the chip - results?
Best Regards, Thorsten.
P.S.: the 1.2k pull-up resistor between the optocoupler output and +5V is still required
Best Regards, Thorsten.
resistor part has thrown me abit - i’ve done this:
