Motor Control Workbench v6.3.0
I tried making a clone of the EVLSPIN32G4-ACT dev kit PCB and it seems to somewhat work after debug downloading but has a few issues:
- UART1 and ASPEP protocol seems to only receive the first transmission and it does not respond
- Button press C13 to make the motor spin does not work
- Resetting the processor with NRST results in weird values being initialized into structs and lots of structs saying "Cannot access memory"
Problem 1: UART1 seems to only receive first transmission, and does not respond
- Starting from debug download start I see that aspepOverUartA has rxHeader[0-4] = 0
- I have a python script I'm using to test the EVLSPIN32G4-ACT dev kit comms. I use it to send a beacon command of "0x85 0xff 0xff 0xbf", to which the dev kit responds with "05 c3 00 d4". I see that the custom board receives the BEACON command of "0x85 0xff 0xff 0xbf", but the python script does not get a response.
- Further attempts to send messages to the custom board does not change what is in aspepOverUartA.rxHeader[0-4]
- I reset the processor with a button press and observe the aspepOverUartA.rxHeader[0-4] is not filled with zero's like it was after debug downloading. Instead it contains "0x00 0xF0 0x8E 0xF8". Every reset of the processor results in this value being in the registers. I power cycled the board, debugged without downloading, and the values were still the same. Other register values on reset. There's a lot of registers that say "can't access memory"
- Once in a while the mcu will respond after debug downloading. Like this time that I debug downloaded, then tried sending the expected beacon values (from the dev kit response):
Press Enter to send command 05c300d4...
Sent 05c300d4. Response: fcfcfcfcfc
Any have an idea what's going on? I've reviewed the schematic several times and it looks like a match to the dev kit. I'll try looking at other dev kits to see if they did something different with various circuits but if anyone has other ideas for testing please let me know.
It's almost like when I accidentally flash the wrong chip and some peripherals are at the same memory location and others are not. Really strange.
