|
Very gently.
"Five fruits and vegetables a day? What a joke!
Personally, after the third watermelon, I'm full."
|
|
|
|
|
Quote: Stick 'm up punk!
|
|
|
|
|
Put away Dirty Harry's .44 something! We are not in Texas here!
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Sorry, was in a bad mood because so called "bugs" were reported that turned out to be part of the functionality, well they know how to keep me busy.
Good that I did not have a .44 at hand
|
|
|
|
|
I don't know that a UART interface (RS232 or a variant?) would be fast enough to handle multiple sticks so that might be that your hardware adapter doesn't support device enumeration and always selects device 0. Not that an 8 bit device can keep up at the full rate anyway, but i'm more thinking from the manufacturer's standpoint here, not how you're using it particular. All speculative, but it's something to stick a mental pin in maybe.
I don't remember how to select devices with the USB protocol although i know the specs are available online (i've perused them before), much less over your adapter. Sorry.
I just thought i'd add the caveat above that it might not be possible with your interface, as i would hate to see you wind up on a wild goose chase.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
It's a standard UART, as you would use for RS232, but without +/- 15V level shifting. This USB converter takes the TTL/CMOS level signals of the UART directly. Speed surprisingly is not much of a problem. This particular UART, a CDP1854, is specified to allow a whopping 200 kbit/sec as max. bitrate. Double that when you raise its second supply voltage to 10V. Not bad for a device from 1976. Back then they actually thought that CMOS was slow.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Wow, that's better than I expected. But your little 8bit monster can't keep up with that unless your clocking is insane haha. I ran a 56k baud modem in an old XT once just for grins (one of the rare ones that was small ISA) and the poor thing couldn't even operate at 33.6 
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
No, it will not, despite going with a (then) ridiculous clock frequency of up to 6.4 MHz and, as one of the earliest CMOS processors, being famous for reckless overclocking decades before such things came into fashion on PCs. I just leave it to the UART's RTS/CTS signals to take care that not a single bit is lost and let the processor pick up the bytes as fast as it can. I can live with getting 'only' 100%. 
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
forgive me if i missed it somewhere, but which CPU are you using?
6502 holds a special place in my black little 8 bit heart.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Memory sticks use the USB protocol, which is available at www.usb.org. The higher-level software protocol is typically USB attached SCSI (UAS), available from the same place.
I don't know what protocol is used for mice, keyboards, or hubs, but I'm sure that you can find it on the site as well.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
yup, and AIUI it's a fairly complex protocol to implement properly; you can't just bitbang it via a simple GPIO pin on a microcontroller.
To bridge a retroPC to a USb stick what you probably would need to do is to have an RPi/etc that speaks both RS232 (or that can bit-bang whatever retro-protocol that the target computer expects to get its IO on) and USB; and then write an application on it that can translate from USB to retro IO.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Dan Neely wrote: To bridge a retroPC to a USb stick what you probably would need to do is to have an RPi/etc that speaks both RS232 (or that can bit-bang whatever retro-protocol that the target computer expects to get its IO on) and USB; and then write an application on it that can translate from USB to retro IO.
Look at the adapter module that I posted the link to. It's actually intended to be used with a Raspy. The conversion magic is done in the lonely chip on the small board. On one side you have the USB port and on the other side you have the four signals for a UART plus ground, at TTL/CMOS levels and not shifted to RS232 levels. That should work with any UART, 8 bit computer or not.
Provided that works as advertised, the big question is what I will have to send over my UART and what response I will get. Maybe I should look for some Raspy users to tell me what they use the adapter for and how they access the USB devices with it.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Whatever you do, during the conversation, don't mention it's size. Memory sticks hate that.
Also, avoid the question "Does my capacity look big in this USB port?"
It's a trick question that can never be answered to the memory stick's satisfaction.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
That's not the worst. Memory sticks never forget any of your mistakes and also store the exact date and time of every (non)event. Just forget any one of them and you suddently must sleep on your couch or in the dog house.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Forgive me, but how exactly do you think that USB interface device will help you?
That interface device functions as a USB client. What you need is a device that can function as a USB host.
The memory stick would be the client and the host device is what would talk to it and relay the information to your 8-bit.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Thanks. I had to find the datasheet of the chip on the adapter to finally find out what it is for. Like you say, the USB side goes to a PC, which then is the host and the UART side of the adapter goes to a client that only has a UART and can then act as a USB client.
It would have been too easy. Back to plan B then. PS/2 for keyboard and mouse, serial ATA to access compact flash memory cards.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
|
The device in the link is something very different than what you are looking for.
Remember that USB has devices with Master role; tose are usally the hosts that initate and manage all the comunication on the bus. Then there are Slave devices that respond to master's requests and send out data in an orderly manner, when instructed to do so.
The device you are referring is of the latter type; it can only reply to a host requests and it can't talk to other USB devices. What you want to implement is a master node.
As you may have understood, the master has very complex tasks to accomplish, since the USB bus is a Plug 'n play thing. One of the first things the master has to do is to enumerate the devices that are on the bus, and it has to do it dynamically, since a device can be added at any time. Then it has to manage the configuration of the device (if needed) and then set up the comunication. Things gets soon very complicated even for a simple comunication with a mass storage. In this case, after the USB 'low level' protocol, you will have to deal also with the "Mass storage" layer.
All I remember is that on the Microchip knowledge base there was some application note with a very simple implementation of basic usb protocol master made to be run on a their smallest microcontrollers, but i regret to say that I don't have any link to it anymore.
Whatever you do, it will be a huge work, and probably lot of fun  . Good luck !
|
|
|
|
|
If the idea of the project is to prove that you can do it on that aged CPU, just for fun, I guess you'll have to do the big work of implementing a USB host.
If you have a problem that requires a solution, one way or the other, you could use one of the tinier Arduions as a relay: Your old CPU talk through an RS232 interface to an Arduino that acts as a USB host through e.g. The Arduino USB Host Shield[^], forwarding the data to the USB devices. Making the two boards cooperate is a nice challenge as well: You will have to do some protocol development to synchronize activities under two quite different OSes. Not too hard, but well above what you would give as a homework assignment to a freshman CS student.
I am sure that there are similar Raspberry Pi solutions, but Pi solutions tend to be more ambitious, larger, more expensive. Arduino solutions are often more limited, but much simpler to handle if all you need is a very simple solution.
If you are a soldering iron person: That Arduino web page refers to the MAX3421E[^] chip on the shield. You may of course try to get hold of one of those and add to your setup, avoiding the complexities of an Arduino. You can probably pick up a lot of useful info from the Documentation tab on the Arduino page (such as the diagram for the shield).
|
|
|
|
|
CodeWraith wrote: Remember what Commodore did with the C64's floppy drives?
I had a TRS-80 Model 100, along with the external floppy drive. The drive used RS-232 at a whopping 19.2K baud to talk to the drive, which held an amazing 100K.
Software Zen: delete this;
|
|
|
|
|
Converters like the one mentioned are typically only for connecting slave devices to host computers. If you are trying to be the host and use a memory stick, you need a USB Host or OTG peripheral.
Something along the lines of the Arduino Host shield if you want a pre-made solution.
Arduino USB Host Shield[^]
|
|
|
|
|
I think it's meant to be used the other way. You talk to the usb part and out comes TTL
|
|
|
|
|
didi dodidi didi dodidi dodi do do didididi didi dodi dodido dido dodi dodidodo dodido dodi di didodo
dodo dododo didodi dididi di dodidodi dododo dodidi di dido dodi dodidodo dodo dododo didodi di
(The secret language of ancient hackers.)
|
|
|
|
|
Have you seen Mark of RetroClinic's DataCentre (RetroClinic DataCentre - USB on your Beeb[^]) for the BBC Micro? The DataCentre is discontinued, but I expect he would be willing to discuss any questions you have.
I seem to recall that one of the big issues was the Beeb's 16-bit address bus, which meant only accessing a fraction of, say, an SD card's capacity, but I have no idea what the solution was.
|
|
|
|
|
USB is complicated. Trust me. I would highly discourage you to implement your own.
That said, the protocol you're looking for is the USB Mass Storage CDC (Common Device Class). You're probably going to have to toush USB Attached SCSI as well.
If you want to do that though, this CH340 won't do, because it is a USB device and not a host. You'll need something with either a USB ROOT hub (like a RasPi), or USB OTG (I heard some AT90's and PIC16F's are capable of this, but I never found anything like that, so dunno).
You also don't "select" devices per se. When a USB device is connected, the USB hub sends you (the ROOT hub) a message. Let's say, it was hub #5. Then you instruct said hub to reset it. This will make the newly attached device assume an address of "5.0". Now, you send a GET DESCRIPTOR followed by a SET ADDRESS to USB address "5.0.0", which is the CONTROL endpoint of the new device. In SET ADDRESS, you give it a permanent address that it can use moving forward.
Now, why did I say you don't really "select" devices? Because, even though you can address individual devices, all attached USB devices will hear the ROOT's messages, and it is up to them to decide whether to activate or not. If you misconfigure a device and cause an address collision, you're screwed.
I could go on and on about USB, but I think you get the point: Don't Implement Your Own.
For your purposes, I'd use a SD/microSD card instead, as these can be used in SPI transfer mode, which is a cakewalk to implement, as opposed to the pain-in-the-backyard you're gonna have if you try to implement a USB host yourselves.
"I don't think about dying. It is the last thing I want to do. " - theoldfool
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
