doc

Hey pay_C, du hast grad post-nr. 666 Gibst Du einen aus, oder was ? ;D :P Gruss Doc

Sorry Ryan for my bad english, do you mean with polar caps those electrolyt caps (elko) ? If so, you have to use 0.1 uF and 0,47uF. But be careful with the polarity. Generell the rules are saying not to use them as C3/C6 (because of the "wobbling" - if this is the word :D ). But better with those than with none ! Doc

Hallo Gracid, da die Fehlerbeschreibung sehr allgemein ist, versuche ich Dich mit allgemeinen Fallen zu traktieren 8). Vorweg: Core wartet auf kein Signal vom SID sondern es arbeitet auch ohne. Du schreibst, du hast den PIC gebrannt. Hast Du denn auch schon das MIOS via Midi-OX drauf gespielt ? (Vorher kannst Du auf dem Display nichts sehen). Falls ja. Hier noch ein paar "übliche" Verdächtige. - Hast Du die Jumper oberhalb des PICs alle gesteckt ? - Hast Du mal am Kontrast-Poti gedreht ? Meistens zeigt das Display erst im letzten Drittel Zeichen. Übrigens solltest Du auf jeden Fall schwarze Balken in einer Zeile sehen, wenn Du den Kontrast ganz hochschraubst. Das solls erst mal sein. Hoffe es hat dir schon mal geholfen. Doc

Hello Phattline, I can burn them for you if you like (I'm german). Where are you from ? If I understood you right, you want the following ID's on your pics: 0,0,0,1,2,3 - thats no problem. The mios is loaded via Midi-OX. I can put this on for you also. Just give me a message bye Doc

Hallo Ryan, you shouldn't leave those caps out. The power supply may work without them but not as "smooth" as with them (don't know the exact word in english). You can vary a little bit. For example: For C6 you can use any value between 220n and 680 n and for C3 between 68n and 220n. You can use other types than ceramic also. Greets Doc

Sorry Ryan, don't know any other issue. Maybe someone else ? Doc

Do you have installed the seperate Win2000/XP driver for IC-Prog ? If not: You have to install it and the click in the Options that you use the 2000/XP driver (Options -> Programming) Hope this helps .... Doc

Thank you Thorsten for the pdf. Before posting my 'changed' layout could you please 'inspect' the changed tracks. I wasn't able to get them "round". (As mentioned before...I'm a EAGLE dummy :P) Thank you Doc

Hello Thorsten, while planning (layouting) my (next) MIDIbox LC I recognized a error in the layout of the MBHP_DOUT_MTC. Both files, mbhp_dout_mtc_v1.brd and .gif contains it. The error: The 220 resistors which have to be connected to pin 15 of the two 74HC595 are routed to +5V. I tried to correct it. But I'm not practised in EAGLE at all !! (I use other layout software). So can you please check the two connections I've changed and place the correct layouts in ucapps ? Heres the changed file: http://www.systemhaus-schneider.de/doc/mbhp_dout_mtc_v1a.brd Thanks and greetings. DOC

Hey payC, stimmt ! ;D .... nicht mal 2 davon (muß ich jetzt noch einen dritten bauen ??) :-[ Grüße Doc

Hi Synergic, don't know if I'm right, but maybe you have the same problems I had.... Could you check if the pins 3 and 4 of IC2 are connected on your pcb ? - If not - connect them and program the module again. - That was my problem. Before programming the wwprom your pc must have a cypress usb device and after programming you have a USB Audio device. Should be ... doc

Thanks TK, next time I print the layouts from Eagle I'll pay attention on that. Doc

No, I took your layout. In my .brd file there is also the connection missing. What is the 'ratnest' - command ? Thanks Doc

Oh, TK wrote at the same time. Take his advice, cause he's always right. doc 8) ;D

Hi, the device ID is on the primary bootstrap ! You have to burn it on the PIC first. Master = id0 slave1 = id1 slave2 = id2 slave3 = id3 The further options depend on your hardware. Take a look at ucapps Mios Bootstrap loader. After the pics are burned you have to 'pearl' the MIOS four times with a different device id (don't forget the -os_upload switch - it's explained in the readme) The sids can be linked together except in one step: When you 'sysEx' the different id's after the mios is loaded. You also have to 'pearl' the SID Application four times with different id's. So there is no problem when you upload a new firmware. Hope I got everthing right. Doc

I have it !!! :D :D :D It's really the layout :P I connected Pin 3 and 4 of the eeprom together and guess what ..... It worked ! (Now the Power LED is lightning...I didn't recognized this damned LED till now !) Now the EZ Control Panel worked fine and I get 2 times 0000 FF and the eeprom is programmed also ! I'm happy ! ::) Could you please check the layout. I think the pins should be connected there also. Thanks again, doc

Thank you again for your quick replay, I checked the voltages. I have only 3.0 - 3.15 V. Could this be the problem ? By checking the schematic against your layout I recognized, that PIN 2,3,4 are connected to ground in the schematic. But not on the PCB layout. There only pin 4 is connected to ground. Pin 2 and 3 and 7 are going to the 100n cap and a 470 Ohm resistor near the power led. Is this correct ? Here are the result of the Voltage check: EEPROM in his socket: Gnd from the Power connector: Gnd - Pin1,8 = 3.2 V Pin 1(+3.3V) - Pin 2,3 = 0 V (!?) Pin 1(+3.3V) - Pin 4 = 3.2V Gnd - Pin5 = 3.2V Gnd - Pin6 = 3.2V Pin1 - Pin7 = 0V Do you think the same. 8) Could it be the layout ? Can you check this ? Thanks again DOC

... da da da daaam is Beethoven ;)

Hi TK, sorry to disturb you again. I still don't get my four USB Modules to work. None of them. I tried it now on Win2000 (2 different PC's), on WinXP and on a old Win98. Today I tryed to program the eeprom with the .syx MIOS file. This part works fine. But when I plug the EEPROM in the USB modul, the PC recognizes still a "Cypress EZ-USB (2131Q/2131S/2135S) - EEPROM missing " device. No way to get a "USB Audiodevice". As mentioned before: When I download the mbhp_usb.hex file with the EZUSB Control Panel, the PC recognizes a "USB Audiogeraet" (and it works fine till power down ;)) So the problem doesn't seem to be the eeprom. But what else ? Back to the EZ Control Center I start again doing the stuff told in your "How to ..." file. The steps: 1.) Plug in the USB device without EEPROM (PC recognizes: "Cypress EZ-USB (2131Q/2131S/2135S) - EEPROM missing " device" 2.) I start the EZUSB panel, plug in the eeprom and press download to upload the vend_ax.hex file. The output window tells a lot of hex stuff and ends with: "Toggle 8051 reset" When I press the "Get dev" Button (just to test) I get the following messages: Device Descriptor: bLength: 18 bDescriptorType: 1 bcdUSB: 256 bDeviceClass: 0xff bDeviceSubClass: 0xff bDeviceProtocol: 0xff bMaxPacketSize0: 0x40 idVendor: 0x547 idProduct: 0x2131 bcdDevice: 0x4 iManufacturer: 0x0 iProduct: 0x0 iSerialNumber: 0x0 bNumConfigurations: 0x1 I'm not able to send the Vedor Request things anymore. This only worked the first time. I only can send a Vendor Request with the following param.: Req 0xA9 Value 0x0000 Index 0xBEEF Length 1 Dir 1 IN Hex Bytes FF Then I get a message: Vendor Request 0000 CD --- why CD and not FF ?? If I send a Venor Rrq. with Dir 0 Out nothing happens anymore. The chip "hangs" When I open the Pending window it shows the Pending message: Pending: OPindex=51 : OP Index = 3 = Vendor Request That was it. Theres no change to do something more. You have to disconnect /connect the module again. Don't know what to do now. Are the Cypress chips faulty (all four ??) ? Is there a way to 'delete' the cypress chip and the eeprom just to start from new ?? Why does it work when I download the mbhp_usb.hex file ? What is the "VendReq" thing. Why does it only work once ? A lot of questions for now. I have to wait for the answers and do something else instead..... Thanks, doc

Thank you again, I try it with the ELV programmer first. But... which file shall I program? The .hex file or the .iic file ??? If it doesn't work I'll ask you again for a .syx file to upload it via MIOS. Thank you TK doc

Thanks again, ...the M$ Knowledge Base gave nothing new for me. Still searching .... But theres something I tried: I searched the forum for other users having simular problems. I tried to download the .hex file (instead of eeprom the iic file). After that win2000 recognizes a USB Audio device. Sure it's gone after power down. But now I think I have a problem with the EEPROMing. Am I right ? Do you think, that the strange behavior in the control-panel depends on the operating system , too ? (The problem, that the usb always hangs after the "Vend Req" Button pressed. The Pending Operations window displayes: " Pending: Opindex=46: Optype=3=Vendor Request "). I think I'm not able to load the EEPROM then. I don't know, what this "Vend Req"-thing does exactly, but can I program the EEPROM with my "universal programmer" instead ? (I have a ELV programmer which supports several EEPROMS from microchip). doc

Thanks T, i'll search there. Can you give me some keywords to search for ? Thanks again. doc

Hi all, back again on the ground. I have some troubles with the USB Module. I build four of them but I get NONE to work. Operating System Win2000. First everything looked great. I connected the module and installed the driver. The driver is named: "Cypress EZ-USB (2131Q/2131S/2135S) - EEPROM missing " The I started the EZ control-panel and did the download, did the "Vend Req" thing, and burned the eeprom as told in TK's "How to.." Still everything seemed to be fine. I closed the Control panel. and did a restart on Win 2000 (German: "Alles gut macht der Boot..." ;D After the restart I looked in midi-Ox for the new Audio-Device. It should be there, or not ? I didn't found a new device anywhere. The USB Module is still in the device manager with the name: "Cypress EZ-USB (2131Q/2131S/2135S) - EEPROM missing " OK. Then I tried the second USB module with the same problems. The I tryed to do the eeprom grocess again. Now I have several problem. After doing the download, I didn't get the system to do the "Vend Req". When I open the "Show pending" Windows I see that it's still pending. Nothing I can do against this. I tryed all the programming steps again on another midiport. I reprogrammed the eeproms again and still had now new "Audio device". On the new USB Port I tried to programm once again. But the second time I still have the "Show Pending" - problem. What shall I do ???

Puh... so viele Fragen auf einmal.... :o Denk dran es ist schon spät... und der Rotwein ... :P Also, von Anfang an. Ich bin mir nicht ganz sicher, aber ich glaube, das LCD sagt nix ohne mios. Du musst den SysEx load starten, nachdem im midiOx Monitor-Input die Message kam (innerhalb von 2 Sekunden). Um es richtig zu stellen. Innerhalb von 2 Sekunden das Betriebssystem uploaden. DANACH erst kannst du was auf dem Display ablesen. (Das Mios macht einen reboot und zeigt auf dem Display READY an. ALso nach dem Bootstrap loader kannszt Du nix am Display lesen. Ich glaube nicht, dass der PIC defekt ist, sonst hättest du mit dem JDM den Bootstrap loader nicht drauf gekriegt (hab noch nie nen PIC geschlachtet...das geht, glaube ich, nur mit roher Gewalt !) Beim Midi-Ox Monitor Input siehst du die Meldungen deines Core. Wénn Du da nach dem Einschalten des Core NICHTS siehst, überprüfe nochmal die Midi Einstellungen. (Das blaue Symbol mit dem Diodenstecker). Viel Glück ! Doc ( ... und gute Nacht...geh jetzt schlafen. der Rotwein und so ...)

Nachtrag: So wie du die Sache beschrieben hast, könnte es tatsächlich an einem Transistor liegen. Hast du noch zwei übrig ? - Dann tausche die mal. Vielleicht hast Du einen Transistor verbrutzelt ?