Page 3 of 60
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 06 Apr 2020 23:52
by arkadiusz.makarenko
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.
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 06 Apr 2020 23:58
by arkadiusz.makarenko
Higgy wrote: 06 Apr 2020 21:00
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.
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 07 Apr 2020 15:30
by terriblefire
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 07 Apr 2020 16:41
by 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.
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 07 Apr 2020 18:00
by arkadiusz.makarenko
terriblefire wrote: 07 Apr 2020 16:41
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.
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 07 Apr 2020 19:38
by terriblefire
OK cool. I'll try and get amiga.c setup on this chip and i'll post you a board.
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 08 Apr 2020 11:18
by 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
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 08 Apr 2020 17:49
by arkadiusz.makarenko
terriblefire wrote: 08 Apr 2020 11:18
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?
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 08 Apr 2020 18:54
by terriblefire
arkadiusz.makarenko wrote: 08 Apr 2020 17:49
terriblefire wrote: 08 Apr 2020 11:18
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.
Re: TF CD32 Riser Revision 2 Design Complete
Posted: 08 Apr 2020 19:10
by arkadiusz.makarenko
terriblefire wrote: 08 Apr 2020 18:54
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?