exxos's Atari, Amiga & retro forum

My central heating has packed in so didnt get near the lab tonight.

terriblefire wrote: 09 Mar 2020 22:10 My central heating has packed in so didnt get near the lab tonight.

From the dry heat of the desert, back to Scotland with no central heating - Ouch! :o

I managed to bugfix mouse initialisation. It was very silly bug, but I am beginner in C after all.

go0se wrote: 09 Mar 2020 22:49 From the dry heat of the desert, back to Scotland with no central heating - Ouch! :o

Aye. Shockaroony.

arkadiusz.makarenko wrote: 09 Mar 2020 23:52 I managed to bugfix mouse initialisation. It was very silly bug, but I am beginner in C after all.

Hardfault usually equals stack overflow in my experience with that chip.

There is another bug. Mouse X,y in mouse variable are stored as uint8_t but should be int16_t. Direction of move is lost on cast.

I've tried firing it up and with one device i always get hardfaults and the other i get...
Basically looks like the 105 doesnt have the RAM for what we're trying to do

terriblefire wrote: 11 Mar 2020 19:32 I've tried firing it up and with one device i always get hardfaults and the other i get...

hardfault.JPG

Basically looks like the 105 doesnt have the RAM for what we're trying to do

There is interface switching after receiving data from device or SOF, Device type changes and as it is non blocking code once it runs as deviceType mouse and on the other as deviceType keyboard on each cyckle. It may screw up keyboard settings or even kb_clock ? (maybe).

Device bufferes are 500bytes each, there should be enough ram to handle it. IDE say that about 3-4k is used.

May I ask what device throws hardfaults?

arkadiusz.makarenko wrote: 11 Mar 2020 20:42 May I ask what device throws hardfaults?

its one of these https://www.amazon.co.uk/dp/B00CL6353A/ ... 41_TE_dp_1

terriblefire wrote: 11 Mar 2020 21:03

arkadiusz.makarenko wrote: 11 Mar 2020 20:42 May I ask what device throws hardfaults?

its one of these https://www.amazon.co.uk/dp/B00CL6353A/ ... 41_TE_dp_1

Damn. I have lower model MK220 (works ok). I will try to get one set soon.

Meanwhile, could you read hid descriptors from them (usbhid-dump on linux) I would compare it with my one, and see where issue may be.

terriblefire wrote: 11 Mar 2020 19:32 I've tried firing it up and with one device i always get hardfaults and the other i get...

hardfault.JPG

Basically looks like the 105 doesnt have the RAM for what we're trying to do

This can only happen on usb disconnects. There must be a bug which screws something up.(I suspect mouse init - buffer length allocation). I will try to investigate this.

I have built hid2ami and written my own firmware on f105, and devices which I have at home do behave, so only way forward is to find more devices and trace this issue.