easyHID question


Closed Thread
Results 1 to 40 of 49

Hybrid View

  1. #1
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959

    Default

    Yes, that program definitely works.
    Dumped in on an 18F4550 before I uploaded it here.

    I don't see anything directly in the schematic.
    But up in the top left corner, there's some connections labeled P$1. Where do they go? Nowhere I hope.

    Which type USB connector are you using? A, B, mini?
    DT

  2. #2

    Default

    Quote Originally Posted by Darrel Taylor View Post
    Yes, that program definitely works.
    Dumped in on an 18F4550 before I uploaded it here.

    I don't see anything directly in the schematic.
    But up in the top left corner, there's some connections labeled P$1. Where do they go? Nowhere I hope.

    Which type USB connector are you using? A, B, mini?
    I'm really glad at this point that my PIC has a "working firmware" in it, very glad indeed. Thank you Darrel
    With working I mean that this is a real milestone here and next I shall/must/will find an error on the pcb. If not ... that is not an option.

    I will take a big magnifying glass and look throughly what could be wrong with the pcb. The error/fault/"something wrong" have to be there, so it needs a sharp and thorough inspection...

    It is a prototype at this stage. This means that there is an USB connector so you can easily use the USB on it, connect it to your PC etc.

    The connectors in the left upper corner are there for the final situation, at that point the USB connector will disappear from the pcb and it is moved then behind those connectors.

    The USB connector is B type, attached also an excerpt from the Eagle.pcb just to demonstrate the connector type

    A USB mini connector wouldn't be good for testing purposes...
    Attached Images Attached Images  

  3. #3

    Default

    ... error on the pcb. If not ... that is not an option.
    Still that is not an option. However can not find anything wrong, it seems to be electrically good when measuring all routes around USB, nothing seems to be wrong or even can not suspect any routes.

    However, I have one question, what should one see on D+ and D-?
    Now those seem to be steady, about 100mV.

    Darrel: that software you kindly provided as a hex-file... When not knowing what is inside I'm not sure about what I should see on those two pins (23,24)?
    .

  4. #4
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959

    Default

    Quote Originally Posted by keymuu View Post
    However, I have one question, what should one see on D+ and D-?
    Now those seem to be steady, about 100mV.
    That's not good.
    They are a differential pair. So when one is high, the other is low.
    You should never see both low.

    Oh, and according to the PCB layout, the B-type connector is wired to the SN65220 correctly, and the pinout is right. But is was a pretty small portion. Hard to tell where the traces go from there.
    Last edited by Darrel Taylor; - 26th October 2008 at 01:15. Reason: B-Type
    DT

  5. #5

    Default

    Quote Originally Posted by Darrel Taylor View Post
    That's not good.
    They are a differential pair. So when one is high, the other is low.
    You should never see both low.
    Yes, of course... however they still are both "down" so probably the USB portion of my PIC is broken. How has that happen, can not tell, don't know but that seems to be the case. Have to wait for Monday to get a new PIC.

    Oh, and according to the PCB layout, the B-type connector is wired to the SN65220 correctly, and the pinout is right. But is was a pretty small portion. Hard to tell where the traces go from there.
    Everything is ok there, that picture was just for showing the connector. As said earlier, if Eagle says that the board and schematic are consistent then there really can't be such errors. Have measured all traces, they go where they should go and they are not broken either and they are not too close each others either.

    Could it be possible that the PIC would have been "broken" when bought? I could not think so, but on the other hand Murphy's law says something else...

  6. #6
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959

    Default

    Quote Originally Posted by keymuu View Post
    Could it be possible that the PIC would have been "broken" when bought? I could not think so, but on the other hand Murphy's law says something else...
    Always a possibility.

    Attached is a new HEX file.

    It blinks PORTA.2 at a 0.5hz rate. 1 sec on, 1 sec off.

    I've re-enabled the Oscillator switchover, in case the main isn't working. If it's switching over, the blinks will get REALLY long. (~20 sec)

    WDT is on, in case it locks up somewhere.

    And MCLR is still disabled.

    Attached Files Attached Files
    Last edited by Darrel Taylor; - 26th October 2008 at 04:17. Reason: 20 sec
    DT

  7. #7

    Default

    Quote Originally Posted by Darrel Taylor View Post
    Attached is a new HEX file.
    Thank you indeed...
    It blinks PORTA.2 at a 0.5hz rate. 1 sec on, 1 sec off.

    I've re-enabled the Oscillator switchover, in case the main isn't working. If it's switching over, the blinks will get REALLY long. (~20 sec)

    WDT is on, in case it locks up somewhere.
    It gives just what you said, on PORTA.2 one can see a 50% cycle about 0.5Hz. When I plug the cable there is a very short pause in that cycle and then it continues again. So at this point I was quit surprised when I saw that D+ and D- worked as they should, one was down and the other up. I heard also the plug and unplug signals (ding-dong and dong-ding) and the port did not die, at least when plug and unplugged three four times.
    So how was this possible?
    My mistake...
    If this (with toggling RA2) was working, why was not the previous one working earlier? At this point I'm sure that I did not use the real file because I renamed it to the one that was last compiled and could so (so I taught) straight away (Ctrl-P) compile it with meProg. Now I know that, that file (last compiled) is not necessary the one you think of if you do not come via/from MicroCode Studio. Now I now (can see) that the name of the used file is also in the caption.

    Today I used for the first time File/Open in meProg when I realized that this is also possible, I have not had need to that earlier when one could start the programmer from MicroCode Studio. When I now programmed it (straight from meProg) I can see D+ and D- to be opposites and also Vusb to be 3,20V.

    I don't see how this could solve the original problem when it suddenly was not hw matter after all. This misleading thing (suspected hardware failure) was solely and alone my fault, my carelessness...

    And MCLR is still disabled.
    It seems to me that the meProg overwrites all configurations. I have verified that with the MCLR, it is not disabled when it is "burned" into PIC. There might be some conflict with original configuration and implemented ones.
    Used configurations are as an attachment.
    Attached Images Attached Images  

  8. #8

    Default

    I had a failure in current supply that seemed to affect also the USB life somehow, however can not explain the process, can only say what I hear and what I can see. That is fixed now, but did not fix the main problem here...

    Now I can see on D- something happening quit quickly after power-up, then nothing or let us say the same about 100mV staying quit steady. But the plugged and unplugged sound (ding-dong ... dong-ding) does not come.

    Darrel: Could you please add a toggle portA.2 (or lata.2) somewhere in your code so that when your program is running I could detect it via that pin (4). That would help to localize, or at least to take me closer to the error source.

    I’m kind of lost here, don’t know should that code say ding-dong or not, and don’t know if it is running or is it stuck somewhere.

  9. #9
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959

    Default

    OK, I'll put a blinky on RA2.
    Give me some time to modify and test.

    In the mean time.

    1. Check the voltage on pin 18 Vusb. It should be ~3.3V.

    2. D+ uses the internal pull-up to signify FULL speed operation. You should see around 2.8-3.3 volts on pin 24. If not, disconnect the USB cable, and check again.

    3. Try plugging another USB device into that USB port on the computer or hub. Make sure the port itself is working.
    DT

  10. #10

    Default

    Quote Originally Posted by Darrel Taylor View Post
    OK, I'll put a blinky on RA2.
    Give me some time to modify and test.
    Thank you
    In the mean time.
    1. Check the voltage on pin 18 Vusb. It should be ~3.3V.
    USB ON MY PIC HAVE TO BE BROKEN!
    There (pin 18) is a voltage that is about 10mV without the cable connected and something over 40mV with cable connected, however that value seems to grow slowly, maybe 10mV in 20sec.

    2. D+ uses the internal pull-up to signify FULL speed operation. You should see around 2.8-3.3 volts on pin 24. If not, disconnect the USB cable, and check again.
    Well, do not see that as could be guessed... it is broken, I can see on pin 24 (D+) something around 100-200mV

    3. Try plugging another USB device into that USB port on the computer or hub. Make sure the port itself is working.
    Yes, all ports work as they should. I can change devices from one port to an other without any problems etc.

Similar Threads

  1. USB and EasyHID Problems
    By Rob in forum USB
    Replies: 8
    Last Post: - 6th January 2007, 18:19
  2. Please answer my first question
    By John_001 in forum Off Topic
    Replies: 1
    Last Post: - 15th September 2006, 06:49
  3. HIDMakerFS versus EasyHID
    By Demon in forum USB
    Replies: 4
    Last Post: - 15th August 2006, 08:01
  4. EasyHID VB help with multiple HID's
    By pfinfrock in forum USB
    Replies: 1
    Last Post: - 6th October 2005, 19:16
  5. Replies: 0
    Last Post: - 5th September 2005, 09:09

Members who have read this thread : 0

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts