arkadiusz.makarenko wrote: ↑Fri Dec 20, 2019 10:45 pm
Is there firmware for this stm32f10x chip?
Maybe it should be stm32f7x0 (fake chip issue and more power?) And port the code?
So i expect that whatever the thing actually says it will have the same pinout as this project.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
arkadiusz.makarenko wrote: ↑Fri Dec 20, 2019 10:45 pm
Is there firmware for this stm32f10x chip?
Maybe it should be stm32f7x0 (fake chip issue and more power?) And port the code?
So i expect that whatever the thing actually says it will have the same pinout as this project.
Damn. No full source code. (Or I had too much wine) I guess it has to be f103 then. Good news is that Chinese clones are getting pretty good.
Well you get good ones if you buy em from RS like i do.
Maybe we can change it to something else but really i wanted to put something i the mix that was a starting point.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
The amazing thing with doing a refactor like this is that you can see what can be removed.
50% of the HID2AMI can go. There is no need for those transistors with the approach i'm taking.
Basically what we end up with is ...
ARM talks to HID devices and maintains updates etc.
ARM can pump Keyboard data directly into the CD32 with the keyboard data lines.
when the CD32 talks to the joyport/mouse ports it is actually talking to the ARM
- IF a HID device is plugged in, otherwise no override happens and standard joyport/mouse is used.
How this works is the ARM will signal the CPLD if it can provide data for a port. If the CPLD gets this signal then it asserts PUNT when an access to the joystick/mouse port happens and signals the ARM "hey put your data on the bus now".
The CPLD handles the control side of things. ARM handles the data/usb side of things.
Might not work but we'll see.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Pretty sure you could use one of the SPI channels MOSI + SCK for the keyboard. Not tried it though.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
