HID2AMI - *Any* HID mouse and HID gamepad to Amiga adaptor/converter

[sampedenawa]

Originally Posted by dwfa

Thanks for this - that is the BOM I used (v1.1) and noticed the Rev 1.0 Col. I may have misunderstood it, I thought it meant that the item in the row is optional for 1.0 build, but required for 1.1. Did I read it wrong?

Ops, sorry my mistake.
I never did update the BOM column's header.
Read it this way:


|-------|------- |----------|-----------|-------------|
|Part | Value | Device | Package | Opt./Man. |
^^^^^^^^^^^
All optional components can be safely omitted from your assembly. They are there only to show full compliance to STM32 uP reference design, but they are mostly redundant for this use.

[dwfa]

Originally Posted by sampedenawa

Ops, sorry my mistake.
I never did update the BOM column's header.
Read it this way:


|-------|------- |----------|-----------|-------------|
|Part | Value | Device | Package | Opt./Man. |
^^^^^^^^^^^
All optional components can be safely omitted from your assembly. They are there only to show full compliance to STM32 uP reference design, but they are mostly redundant for this use.

No worries, thx for the info.


Is there some documentation I can read to understand what some of those header values mean. I think I understand Part and Opt/Man cols . There others I am not 100% sure about and looking to understand how to read BOMs correctly.

[kipper2k]

Hi,

-what is the purpose of the 4 digit code that is required?
-Is it needed for the device to work?

[sampedenawa]

Originally Posted by kipper2k

Hi,

-what is the purpose of the 4 digit code that is required?
-Is it needed for the device to work?

The 4-digit code is the unique id code of each board, coming from the unique id code of the STM32 assembled on it.


In order to be able to run on any single hardware, each copy of the firmware must be signed/encrypted with a matching code.


So, in poor worlds, each firmware copy is 1:1 tied to one and only one board.

Originally Posted by dwfa

Is there some documentation I can read to understand what some of those header values mean. I think I understand Part and Opt/Man cols . There others I am not 100% sure about and looking to understand how to read BOMs correctly.

A good starting point could be here:

https://en.wikipedia.org/wiki/List_o...ackaging_types

[kipper2k]

Originally Posted by sampedenawa

The 4-digit code is the unique id code of each board, coming from the unique id code of the STM32 assembled on it.


In order to be able to run on any single hardware, each copy of the firmware must be signed/encrypted with a matching code.


So, in poor worlds, each firmware copy is 1:1 tied to one and only one board.




https://en.wikipedia.org/wiki/List_o...ackaging_types

So it is a copy protection then ?

[dwfa]

Originally Posted by sampedenawa

A good starting point could be here:

https://en.wikipedia.org/wiki/List_o...ackaging_types

Thx - I have some reading to do ...

[sampedenawa]

Originally Posted by kipper2k

So it is a copy protection then ?

I would name it "anti-unauthorized-clone" protection.


I was fed up of seeing so many excellent open sourced retro projects being plundered by vultures out there, making money on other's work cloning stuffs, without any effort or contribution to the original project.


So I decided to keep the hw open whereas protecting the firmware from easy cloning.


One of the "vultures" I mentioned above once told me that there was no point in my position, as he could write a compatible alternative fw in few hours, so my protection was worthless.
I am convinced he was right: an STM platform coding pro would make it witout any doubt in actually few hours, but on the other side, I am still sitting here waiting for that vulture to come out with his own firmware build

[Lemaru]

Originally Posted by sampedenawa

I would name it "anti-unauthorized-clone" protection.


I was fed up of seeing so many excellent open sourced retro projects being plundered by vultures out there, making money on other's work cloning stuffs, without any effort or contribution to the original project.


So I decided to keep the hw open whereas protecting the firmware from easy cloning.

The one that really bugs me, is when someone modified someone else open design, and never credits the original developer on their versions, and maybe a link to the original project. It's the least they can do, give credit where it's due.

Oh and honour the license of the original design. Plenty don't do that, especially when it often means releasing their own files

[sampedenawa]

Just released firmware update v1.9.6, flowing now through usual distribution channel.


Should someone not be receiving it notice me with PM.

[sean_sk]

Hi sampedenawa,

Just a question:

The BOM specifies the LM1117MPX-3.3 voltage regulator, but they're too hard to get at the moment in AUS. Most suppliers say out of stock till next year. Can the LM1117IMP-3.3 be substituted instead since these are much easier to get.

Thanks a bunch!

P.S. This chip shortage is really making it difficult to get anything at the moment for any of these hobby projects. Can't even get any STM32F105RBT6 until the end of the year at best guess!

[sampedenawa]

Yes, absolutely, The LM1117IMP-3.3 should be extended temperature range, so you can test your adapter up to -40C


Chip shortage is the same all around the world at the moment. Here in EU is not different; can't find on retail even the simplest chip I can imagine.


Should you find alternative STM32F105RCT6 (though I doubt it), they will fit as well.

Originally Posted by sean_sk

Hi sampedenawa,

Just a question:

The BOM specifies the LM1117MPX-3.3 voltage regulator, but they're too hard to get at the moment in AUS. Most suppliers say out of stock till next year. Can the LM1117IMP-3.3 be substituted instead since these are much easier to get.

Thanks a bunch!

P.S. This chip shortage is really making it difficult to get anything at the moment for any of these hobby projects. Can't even get any STM32F105RBT6 until the end of the year at best guess!

[sean_sk]

Excellent! That's really helpful. Thanks for your help and this excellent project!

[solaris104]

Would it be possible to add wheel support such as Rys MKII?
[ Show youtube player ]

[sampedenawa]

Originally Posted by solaris104

Would it be possible to add wheel support such as Rys MKII?
[ Show youtube player ]

I am developing a rev2 version of the adapter, whit the aim to


- reduce the overall size of the pcb
- make it compatible with CD32 PAD protocol
- make it compatible with mousewheel


In addition, I will probably share a little hardware "hack" to modify current Rev1 adapters everyone has got in order to be compatible with newest v2 firmwares and the above features.


To be more precise:
- at the moment I am waiting a bunch of new v2 pcbs to arrive from the manufacturer
- I am working on CD32 PAD protocol (ETA: around XMas or so)
- Next I will address mousewheel (which needs an Amiga-side driver counterpart)

[sean_sk]

Hi sampedenawa,

I'm about to build 5 HID2AMI's, 3 for me and 2 for a mate.
At the moment grabbing any STM32F105RBT6's from places like Element14/Farnell are near impossible.

Anyway my mate went and bought 6 off eBay.
Because you've built quite a few HID2AMI's and therefore have seen quite a few of these chips in your lifetime, I was hoping if you would be able to identify if these chips are real or fake.

I've personally never had a good experience buying chips from eBay sellers.

I've included some pictures:

[sampedenawa]

Originally Posted by sean_sk

Hi sampedenawa,

I'm about to build 5 HID2AMI's, 3 for me and 2 for a mate.
At the moment grabbing any STM32F105RBT6's from places like Element14/Farnell are near impossible.

Anyway my mate went and bought 6 off eBay.
Because you've built quite a few HID2AMI's and therefore have seen quite a few of these chips in your lifetime, I was hoping if you would be able to identify if these chips are real or fake.

I've personally never had a good experience buying chips from eBay sellers.

Hard to tell with ease but a few considerations:

- from your pics I don't spot any *obvious* clue they are fake (e.g. wrong label font, fake part number, extra dimples, etc)

- even if they were fakes, they could be useful anyway: hid2ami does not make use of analog, i2c, etc ..

- you will gather more clues when, after having assembled a couple hid2ami, you'll generate unique board IDs. In general, fake clones tend not to have unique valid IDs inside (and then I can spot them easily)

So my advice at this point is to assemble a couple boards and check what happens before assembling the remaining ones.

[sean_sk]

Thanks sampedenawa for the info.
Will try your suggestion.

[sean_sk]

EDIT: PM'd instead.

[sampedenawa]

Originally Posted by sean_sk

EDIT: PM'd instead.

Replied and sent you further email with new firmware to test.

[sampedenawa]

Released fw update v1.9.8:

Added support for Microsoft Wireless Mobile Mouse 4000
Added support for Logitech MX Revolution Mouse
Added support for Logitecg G400 Gaming Mouse
Added support for Logitech G700 Laser Mouse
Added support for Logitexh MX Master 3S
Added support for PS3 DualShock3 BT adapter plus coded trick to detect USB o BT connection (move hat soon after connecting)
Fixed deadzone values for per XBOX360 pads


Should any user not receiving it, please advice.