Good morning!
I've been working in a project whose purpose is communicate AEK-MCU-C1MLIT1 board and AEK-COM-ISOSPI1 through SPI/isoSPI protocols. At first, I've tried to apply the hardware configurations and script as mentioned in the user manual(UM3187) to exchange 512 bytes between two devices through isoSPI, however I don’t know how reliable the results in debug step are to assure this communication is working properly. Another detail that I've noticed is about disable pin, which stay always turned on, mainly when I select configuration as “micro” in AEK-COM-ISOSPI1 Component RLA > Application Cofiguration. What should I do to enable AEK-COM-ISOSPI1 board?
About the wire connections, I used as reference the board view within AutoDevKit Studio. I’d like to know if there is some connection that is missing, especially about the ISOm e ISOp signals, because the board view doesn’t show if I should to connect the USB port on the computer to debug step, for instance.
Debug step:
Board View within AutoDevKit Studio
Thank you!
1 ACCEPTED SOLUTION
Accepted Solutions
Maybe you have made some mistakes during debugger configuration.
Let me share my settings for SPC582Bxx micros:
If you followed the QSG and installed your drivers correctly, using the latter C1MLIT1 configuration should enable your debugger.
Best regards,
Simone
AEK_Team
Hi Gustavo,
I see you are using plsUDE, I suggest, in case you haven't yet, to download AutoDevKit 2.7.0. With this update you can debug boards quickly using openOCD from the AutoDevKit environment.
I am attaching a Quick Start Guide to configure your environment.
Anyway,
as far as I understand you are having some trouble debugging if your ISOSPI device is working.
Please take a look to the following AEK application demo code:
SPC582B - ISOSPI1_LEDdriver test application for discovery
In this example SPI signals are sent from an AEK-MCU-C1MLIT1 to an AEK-LED-21DISM1 via 2 AEK-COM-ISOSPI1.
The commands here are sent via SPI, converted in ISOSPI from the first transceiver, reconverted back in SPI from the second transceiver, and then received by the LED board.
If you have 2 ISOSPI boards, start from this demo and check signals during transmission using a scope.
This should let you debug the communication and tune AEK-COM-ISOSPI configurations to achieve your goal.
Regarding the connection between 2 ISOSPI boards, make sure to connect ISOp board1 with ISOp board2 and ISOL board1 with ISOL board2
Best regards
Simone,
AEK Team
Thank you for the informations Simone! I’ll start with this demo and use a scope to check signals as you mentioned.
About the openOCD, I’ve been trying to use it to debug within AutoDevKit, but an error message is showed when I try to finish debug configuration. It seems something related a file’s version error.
Best regards,
Gustavo.
Maybe you have made some mistakes during debugger configuration.
Let me share my settings for SPC582Bxx micros:
If you followed the QSG and installed your drivers correctly, using the latter C1MLIT1 configuration should enable your debugger.
Best regards,
Simone
AEK_Team
Hi Simone,
I have a doubt about openOCD debugger. Is it possible to use openOCD debugger without
a debug adapter? I was trying to debug by connecting PC and MCU directly through C1MLIT1’s micro-USB connector.
I'm not using this adapter:
Best regards,
Gustavo.
Hi Simone!
I’m still working in the project that I’ve mentioned before and I’ve been trying to deploy SPC582B - ISOSPI1_LEDdriver test application for discovery as example. However, I’d like to figure out better about configurations needed in AutoDevKit Studio to change SPI allocated pins from AEK-LED-21DISM1 to AEK-MCU-C1MLIT1 works as Master, because the first board isn’t needed to check the isoSPI signals. I’ll share with you the Board View connections that is showed when I imported ISOSPI1_LEDdriver test application.
Best regards,
Gustavo.
Hi Gustavo,
Actually, if your goal is to communicate with a SLAVE board (LED or any other) connected via ISOSPI to your micro you should not change anything.
The 4 SPI pins you are seeing (in your scheme related to the LED 21DISM21) have to be plugged to the SPI pins of the first AEK-COM-ISOSPI board, then, if everything is supplied correctly and you board are configured, you should see the SPI signals at the second node.
In case the system is different and you need more nodes/different SPI speed, then you should take advantage of the AEK-COM-ISOSPI component:
If you click on it you can add nodes ad allocate/deallocate ISOSPI configurations
For further details, please, take a look to the ISOSPI User Manual
Best regards,
Simone
AEK_Team
Thank you Simone!
I've read the user manual and I noticed that script in the page 23, is the same I’m using in demo test application. In this case, considering that I‘m not using the AEK-LED-21DISM1 and the script have some commands related API this board, I believe that I should to adapt this script. I made a new script and I’d like to know if the script below make sense to test this application, mainly regarding some API’s spi low level commands, like spi_lld_send, spi_lld_receive and spi_ldd_start, for instance.
Best regards,
Gustavo.
