TF CD32 Riser Revision 2 Design Complete

[arkadiusz.makarenko]

I'm really hoping something like this will work on one usb port and a usb mouse keyboard combo on the other.

https://www.ebay.co.uk/p/7031293974?iid=143292049862

Dual controllers on one dongle... This might be a challenge to have support universally. At this point only one should work. But adding support for this particular device shouldn't be too difficult.

[arkadiusz.makarenko]

Would you be thinking of say mapping PS3 controls to replicate CD32 pad? I have a PS2 controller adapter to Dtype for my CD32 as it came with no pad (or psu!).

At this point library is capable of supporting only standard PC HID gamecontrollers. It depends how hid descriptors on dongles for PS2/PS3 devices are constructed, but it is unlikely that they would work with current library. I am planning to expand support, but it may take a while.

[terriblefire]

riser_revision2.txt

[terriblefire]

I'm having issues programming the F722 ...

specifically I can't erase it when i try to run something :(

Code: Select all

Memory Programming ... Opening and parsing file: ST-LINK_GDB_server_a16228.srec 
File : ST-LINK_GDB_server_a16228.srec Size : 13052 Bytes Address : 0x08000000 
Erasing memory corresponding to segment 0: Erasing internal memory sector 0 
Error: failed to erase memory Error: failed to erase memory

EDIT: Solved. The ARM was installed with flash read/write/erase memory protection. I guess it wasnt a new chip!

Used ST-Link Utility and set LEVEL 0 in the Options.

[arkadiusz.makarenko]

I'm having issues programming the F722 ...

specifically I can't erase it when i try to run something :(

Code: Select all

Memory Programming ... Opening and parsing file: ST-LINK_GDB_server_a16228.srec 
File : ST-LINK_GDB_server_a16228.srec Size : 13052 Bytes Address : 0x08000000 
Erasing memory corresponding to segment 0: Erasing internal memory sector 0 
Error: failed to erase memory Error: failed to erase memory

EDIT: Solved. The ARM was installed with flash read/write/erase memory protection. I guess it wasnt a new chip!

Used ST-Link Utility and set LEVEL 0 in the Options.

I had some similar issues with new chip from the same family f730. Erasing with utility usually solved all issues.
Weird enough that occasionally I had to do it, because stm32cubeide just couldn't program it.

Another observation is that those seems to be more fragile than f10x series or xillinx cplds.

[terriblefire]

OK cool. I'll try and get amiga.c setup on this chip and i'll post you a board.

[terriblefire]

OK my new issue is that i start the debugger it starts debugging but dies in the sysconfig bit. :/

I agree the STM32F7's seem a lot more fussy than the 105s

[arkadiusz.makarenko]

OK my new issue is that i start the debugger it starts debugging but dies in the sysconfig bit. :/

I agree the STM32F7's seem a lot more fussy than the 105s

Have you configured SYS debugging?

[terriblefire]

OK my new issue is that i start the debugger it starts debugging but dies in the sysconfig bit. :/

I agree the STM32F7's seem a lot more fussy than the 105s

Have you configured SYS debugging?

Is that a MCU option? I have soldered up a second board without the MCA connector and the ARM starts... Not powered by the CD32.

[arkadiusz.makarenko]

Have you configured SYS debugging?

Is that a MCU option? I have soldered up a second board without the MCA connector and the ARM starts... Not powered by the CD32.

Power issue or damaged mpu?