Jump to content

killerfrog

Members
  • Posts

    14
  • Joined

  • Last visited

    Never

Everything posted by killerfrog

  1. well ... sorry. as I said before i'm not a Pic programmer and I want to build the whole thing with the best of my knowledge and I did't get it about the bug... anyway, by the time I wrote down more explanations for the customer service of Microchip and there is their answer : personnaly, at this step I can't go further as I cannnot explain with technical terms to them the problem. I will probably just abandon the idea like others did :(
  2. could you be more specific please ?
  3. well those are took on my comp. As I said it doesn't work for now on my comp. We had not the time to get printscreens on my friend's comp because he had a severe bug that has corrupted his windows and his motherboard has memory read errors (not the memory itself, but slots !) and we unable to precess more test with his computer (that have Sonar, Professionnal audio soundcard etc.) at the same time we were testing... That's an illusrated example of the Murphy Law !!! As long we cannot test, it cannot go further. My friend will probably need to get a new comp (or at least new MB and maybe other parts...). So by the time if anyone would have get more info ? By the time, I have contacted Microship to get some help here is their response : If you click on the weblink, you can see that is seems to be an version B4 of the pic and in the errata, there is nothing about the EUSTART bug so it MAY work for the second part... as long the first (detection) is solved...
  4. maybe you are right for the reinstallation. But, for the very little time we had on my friend's comp, it seems it was beeing display exactly the same way in his devices that it was on mine... that's why it's wreid... According to this post, there is at least one working version of the device (see post # 17) http://forum.microchip.com/tm.aspx?m=85120#
  5. thank you for this information. That part seems to be ok in the code... at least for my poor knowledge
  6. just to give a little update, My friend and me have started to test the circuit on his computer with an professionnal audio card and professionnal software (Sonar 4) and it seems to be detected same way that it was with my comp (http://www.midibox.org/forum/index.php?topic=8817.msg62252#msg62252) with the diff that it appears in Sonar 4. During we were starting to test on his computer, he had a crash and memory failure (socket itself, not the memory !!) and we had to stop. So up to now I can't confirm it works, but with the brief tests we took, it seems to be in the good way. I must say that even if I install Sonar 4 on my comp, the Midi card doesn't appear for me... that's wreid... Can someone explain me how go get the pic revision version (to know right know if we are subject to the silicon bug or not) ? Is there anyone who would test the circuit in // with us to concure on inconcure ? Thank you
  7. i'm going to see a friend for the next hours wish is more skill in pics, Midi and have more Hadware to test than I have. I'll put some more infos in if we find something during this time. If someone else would have infos of any sort, that would be nice to share ! Thank you.
  8. So am I !! In fac, I never has used PIC before this week. So I don't know a lot about them. I just wanted to do this for fun, but I found it is much more harder than a plug and play device... At least, according to what I think of that bug that apply to transmition, this should have nothing to do with the detection or not in Windows XP : I mean that even if data would not pass (with this revision of the PIC, but not with the A0, A1 or A2 (mabye A4 ?)), there shouldn't be any reason for the device to not beeing detected by Windows... or at least to not be completely on hands for the user...
  9. Yes, I'M aware of that bug (I've called this bug the Silicon bug in 2 or 3 other posts in this topic by using the same name the owner of this website has given to it !). Thank you. That's the reason why I ask How I can get the revision version of my pic. My Windows is Win XP.
  10. Maybe I have not expressed myself clearly (probably because of language barrier). There is nothig else than "SigmaTel Audio" that appears there. In fact, SigmaTel Audio is my supposed Sound Blaster chip I've paid for when I have ordered my Inspiron 9400... I ask again a question I've have asked before; what is the way to know wich version of PIC18F2455 I have ? At least it seems there is another solution comming out as "EZ-USB FX1" proposed by Lall, but the PIC version seems to be so more simple to build and to use! (at least if it can work at all !)
  11. the only places where I found it I've have put in in those printscreens. It is no where else (at least that I think of). Other idea ?
  12. I see... Do you think this could have something to do with the silicon bug, or that's a bug with code itself ? Thank you P.S. Mabye someone has tried it so may have more information ?
  13. that's cool. Here on this forum people really take time to read !! If I go foward in my idea, I would ask if anyone would have try to put the midinator code in a PIC18f2455 (or another that may be compatible ?) who may confirm it works or not ? How can I get the version of my Pic ? Is it by using the pickit starter 2 ? You were right about the device in Windows. Its appear when plugged under name (or in audio of windows under section hardware) : "périphérique audio USB" Fabricant : USB Audio Générique Emplacement : Emplacement 0 (Pic18F2455 MIDI V2.1) État du périphérique : Ce périphérique fonctionne correctement If I translate a little bit, it would say that everything works fine! I join 3 pictures to show what I have, but I'm not sure it is detected by MIOS studio, is it ? Thank up to know for fast answers and handfull help ! 1.GIF 2.GIF 3.GIF
  14. Edit : dont take the time to read this thread, no solution has been found. Sorry !
×
×
  • Create New...