MicroUSB. Whats a preferred alternative interface?
in [Commodore]
|
From: agila61 on 15 Dec 2006 15:35 Tristan Mumford wrote: > Ah right. > It's more of an all purpose 'fantasy' chip, that fills the "I wish I had > an IC that does X" kind of area. That could be extremely useful. Precisely. "I wish I had an IC that passed through line 1 in state %00 and %01, inverted line 1 in state %10, and passed through line 2 in state %11." Or, "I wish I had a tri-state /CLK, /CS chip with 2 2bit ANDS, 2 2bit NANDS and a 4bit NOR."
From: agila61 on 15 Dec 2006 15:43 Tristan Mumford wrote: > I'm not sure how my project is faring right now though. Now I have > communications working it unearthed a problem in the other end. > It seems as though something is causing it to be a little hard of hearing, > or something to that effect. > It's strange. It can detect a device connected to it But it can't finish > initialising. > The code gets stuck on process(3), which essentially means that the code > goes into a busy wait. It's waiting for bit 1 to go high, signalling the > end of a read operation (USB peripheral -> controller), but it never > happens. .... > I guess logically the USB IC is getting a clock signal because the USB > detection part works. I saw that on the other thread. If the serial clock line is inverted against what the chip is expecting, you'd detect it, but not necessarily be able to get any serial data registered? Or the chip clock out of phase with the serial clock line? Me, I'd ask a hardware guy to have a look at it. So, go have a look at it. 8-)# IOW, Good luck, I'm barracking for you.
From: Tristan Mumford on 15 Dec 2006 18:40 On Fri, 15 Dec 2006 12:43:12 -0800, agila61 wrote: > Tristan Mumford wrote: > >> The code gets stuck on process(3), which essentially means that the code >> goes into a busy wait. It's waiting for bit 1 to go high, signalling the >> end of a read operation (USB peripheral -> controller), but it never >> happens. > > ... >> I guess logically the USB IC is getting a clock signal because the USB >> detection part works. > > I saw that on the other thread. > > If the serial clock line is inverted against what the chip is > expecting, you'd detect it, but not necessarily be able to get any > serial data registered? Well, I fixed the RS232 signal by buffering with a schmitt trigger. Inverting was a red herring, once I thought about it. It is interesting about what you say about the inversion of the USB data though. That thought occurred to me. However, I have checked the wiring of the USB connection. It is correct. Following on from that, once a low speed USB device is detected, the 811HS swaps D+ and D-. Apparently that is something special related to low speed devices. So if it detects a low speed device it _should_ be doing everything correctly. I found some more mistakes though. It seems I couldn't tell the difference between uF and nF. So next week I'll have to get some new caps with the correct value. Speaking of which. Found most of what I wanted on Farnell. But the only way to get it is to pay $10 for a courier. For a crystal, a regulator, and some caps. Seems a bit excessive. Leaving it for now. Especially since I just realised that I forgot to fill in a form so I don't get paid :( Another one is in for(x=0;x<7;++x) The value of x will only range from 0 to 6 inside the loop. That's where part of the lack of communication was stemming from. > > Or the chip clock out of phase with the serial clock line? > I'm sorry. Could you please explain that a little further? > Me, I'd ask a hardware guy to have a look at it. So, go have a look at > it. 8-)# Looked at it. Considered stomping on it. > > IOW, Good luck, I'm barracking for you. Thanks. I need it. And thanks for your help and support. -- -----> http://members.dodo.com.au/~izabellion1/tristan/index.html <----- ===== It's not pretty, it's not great, but it is mine. =====
From: agila61 on 15 Dec 2006 18:50 Tristan Mumford wrote: > I found some more mistakes though. It seems I couldn't tell the difference > between uF and nF. So next week I'll have to get some new caps with the > correct value. Great to hear -- not that the wrong values were used, but that they were found. Its when you run out of mistakes that the risk of hair-pulling starts to rise.
From: Tristan Mumford on 16 Dec 2006 01:11
On Fri, 15 Dec 2006 15:50:57 -0800, agila61 wrote: > Tristan Mumford wrote: >> I found some more mistakes though. It seems I couldn't tell the difference >> between uF and nF. So next week I'll have to get some new caps with the >> correct value. > > Great to hear -- not that the wrong values were used, but that they > were found. Its when you run out of mistakes that the risk of > hair-pulling starts to rise. That's for sure. I'm getting closer to that point. As of today I have fixed the low 3.3v rail problem. It helped a little. I also added a simple interrupt based menu. Basically at any time I can hit 't' and it brings up the menu, which allows me to reset the uC and 811HC. I was adding a simple debugger, but that will be finished later. It's still really erratic but working better. I was juct going to look at one of the joystick drivers to see what I need to do to get one of them working. I can only use a USB mouse by stealing it from another computer (currently in use). -- -----> http://members.dodo.com.au/~izabellion1/tristan/index.html <----- ===== It's not pretty, it's not great, but it is mine. ===== |