jamesadrian wrote:
There are several, if not many, projects that can profitably use the 6502, slow as it it.
I'm not disputing that. I've got a project that uses/will use a 65c02, and WDC is still afloat, so it's clearly profitable. And I'd be inclined to say that it's fairly quick for its clock speed. It's just that the discrete chips only go up to 14MHz, and more modern processors can go into the GHz range.
jamesadrian wrote:
I am interested in the ones that involve a USB port. If the 6502 were a tenth as fast as it is, it could still run a USB port.
I know of a way that the 6502 can act as a USB host; the CH376 can do that(with FAT support out of the box, and it appears that it might possibly have multiple interface options. I haven't been able to find any in-depth information(particularly an actual datasheet, or the company that makes them) by googling a bit, so it might be iffy.
This looks like it's meant to be an answer to my request for proof. This is not proof. This is a statement without proof. And I wasn't actually asking for the 6502's ability with USB. I was asking about the 6502's ability regarding your intended application. I didn't phrase my question all that well. Speaking of which, what is your intended application?
jamesadrian wrote:
We have a different idea about the hardware design.
This sounds interesting. Please, tell me more.
jamesadrian wrote:
I am looking for people who like programming in 6502 assembly language, and also some who understand the USB port. This site is called 6502.org. To me, it makes sense to try to find people here.
Ok... That seems to be saying that you're looking to recruit a team. If that's the case, why didn't you say so plainly?
jamesadrian wrote:
If nobody thinks it is sane to use a 6502 for a USB port device, then I have had another question: Would you like the device better if it used a faster processor and a cross assembler for 6502 programmers?
Cross-assembler? I don't know quite what you're driving at here. A cross-assembler is a program running on one type of processor, that takes in assembly code for a different type of processor, and produces machine code for that second type of processor. What you seem to be describing is something that takes in assembly code for one type of processor and produces machine code for a different type of processor. I'm no expert, but that doesn't seem feasible unless there's an emulator involved.
Mind you, I'm not saying you shouldn't pursue your idea; it's your hobby. Nor am I saying that you should go away; I daresay that you'll be able to get help here. But I don't think you'll get any recruits for a team here, assuming that's what you're trying to do.
My recommendation is this: If we've given you enough information to get started, start designing and prototyping your device.