killerfrog Posted March 27, 2007 Author Report Posted March 27, 2007 In this post, in the second image down, there was no device in the list. You sure that was the same on his PC? Cause if Windows doesn't show it there, but Sonar sees it, that's unusual... IE theoretically impossible, because that window gets the list by using the same MMAPI call as sonar...I thnk TK has since retracted that :(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 :1. Once when you receive the PIC's you can find out the revision of the PIC Devices.2. Please note that you will receive the samples as per the lot available with Microchip.3. As per the revision you have the errata which gives a work around for the EUSART.4. If you have received Rev A3 then issue has the workaround is as follows: Module: EUSARTWhen performing back-to-back transmission in 9-bit mode (TX9D bit in the TXSTA register isset), an ongoing transmission's timing can be corrupted if the TX9D bit (for the next transmission)is not written immediately following the setting of TXIF. This is because any write to theTXSTA register results in a reset of the Baud Rate Generator which will effect any ongoingtransmission. Work aroundLoad TX9D just after TXIF is set, either by polling TXIF or by writing TX9D at the beginning of the Interrupt Service Routine, or only write to TX9D when a transmission is not in progress(TRMT = 1). Date Codes that pertain to this issue: All engineering and production devices.For further information please refer to the weblink given below:http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1999&ty=&dty=§ion=&NextRow=&ssUserText=PIC18F2455Hope this helpsRevert back in case of further queries.Best RegardsIf 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... Quote
stryd_one Posted March 28, 2007 Report Posted March 28, 2007 By the time, I have contacted Microship to get some help here is their response :Wrong bug, ours is another one.... Quote
killerfrog Posted March 28, 2007 Author Report Posted March 28, 2007 Wrong bug, ours is another one....could you be more specific please ? Quote
stryd_one Posted March 28, 2007 Report Posted March 28, 2007 Re: PIC18F4620: new silicon revision B4Use the search, luke. Click SEARCH, Search for : EUSART by user: TKYour bug is about 9bit mode, that's not us. Quote
killerfrog Posted March 29, 2007 Author Report Posted March 29, 2007 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 :You will have to contact our local office.Initiate your process with our local sales office.We do not have any documentation for the USART issues.Our local sales office nearby your area is as given below:Sales Office Microchip Technology Inc 6285 Northam Drive Suite 108 Mississauga,ON L4V 1X5 Canada Phone: 905-673-0699 Fax: 905-673-6509 Hope this helps.Revert back in case of further queries.Best Regardspersonnaly, 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 :( Quote
stryd_one Posted March 29, 2007 Report Posted March 29, 2007 well ... sorry. ..... I did't get it about the bug... Hah, no need to apologise, that makes both of us! That's why I suggested the search for TK's posts - I'm not much of an nameity on these things.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 :(Yeh unfortunately MC have been less than helpful on this one :( Now you know why everyone else has given up :( Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.