[hmarthens]

in reply to: MCU memory corruption when sending data from MPU via SPi #17593

Hi Leo,

Thanks for the response. I saw it a while back, and actually I changed the program and the way of sending data over SPI, now sending much less data…the issue above never occurred again(after this change). I suspect it was related to the sending of a lot of data via SPI.

[hmarthens]

in reply to: MCU memory corruption when sending data from MPU via SPi #17406

Hello,

I am following up on this request to see if anything has been found, or if there is any suggestions ?

Thank you,

[hmarthens]

in reply to: MCU memory corruption when sending data from MPU via SPi #17311

Hi Leo,

Yes, I was able to reproduce the error sometimes when sending data from Pi, please see the script that I use attached above.

1. Sometimes when sending it occurs, so it is not something I can reproduce with certainty
2. From the python file, the speed is 1 MHz
3. When I say it reset, I mean all parameter values on MCU are re-initialized…like all other variables in program not related to SPIFromPi….there could be memory corruption I suspect with arrays writing…kindly also see the document on how I unpack the data from SPI, I hope it is helpful.

Thank you very much!

• This reply was modified 8 months, 4 weeks ago by hmarthens.

Attachments:

You must be logged in to view attached files.

[hmarthens]

in reply to: Sending data to MCU from MPU via SPi #16511

However, one thing I noticed is that the variable “spiTx” is always changing, which confirms what you mentioned…but the only confusion I have is regarding whether the “spi0” service is the default one. Please also see the attached files below.

Attachments:

You must be logged in to view attached files.

[hmarthens]

in reply to: Sending data to MCU from MPU via SPi #16510

Hi Leo,

I checked and there were no other services for SPI, expect the default “spiComm.service”.

Also, in the processes that are running, only “spi0” is present which I guess is also default ?

Nonetheless, the issue I face is still the same. I have also ensured that before building the Simulink files, SPI is setup correctly as suggested on this page “https://www.audesseinc.com/resources/simulink-on-mpu/” but I guess this is more for the case where we want to use Simulink for MPU and is not related.

Please let me know if there could be another underlying issue.
Thanks

[hmarthens]

in reply to: Sending data to MCU from MPU via SPi #16502

Hi Leo,

Thanks for your response. I have tried doing the implementation as suggested, however, when in FreeMaster, I am faced with the issue that the variable “spiFromPi” cannot remain the same and hold a value, I am only able to view it once when it is sent and then it is going back to its default value.

Below is a screenshot of the default value, and a screenshot of a time when it changed.

Is there any particular method you use for latching the value received ?

Attachments:

You must be logged in to view attached files.

[hmarthens]

in reply to: Flashing the Compute Module eMMC #15991

Hi,

I had a meeting with Rhyse, and he told me how to reinstall the OS. I was able to do it successfully!
I was also able to install virtual client usb server, and are now able to flash again to the MCU.
I wanted to kindly know if there are any other setups that I need to follow ?

I am thinking of trying the example(https://www.audesseinc.com/resources/python/) of running python script “spiLogger.py”, however is it possible to provide me with that script since all data on pi was lost.

Thanks

[hmarthens]

in reply to: Flashing the Compute Module eMMC #15956

All in all, I need to install a 64-bit Raspberry Pi OS, and it appears that even though I had changed the kernel…some of the libraries remaining were still 32-bit…meaning, the only stable way to go and be able to run the python script with the 64-bit libraries for my project is to install a new OS. And this would require me to be able to write to the eMMC storage.

[hmarthens]

in reply to: Flashing the Compute Module eMMC #15955

P.S. I needed to reinstall python3,
1. Because the one that was installed the interpreter was 32bit, and I needed to run a script that uses a library which is 64-bit
2. Because I had also changed the kernel from the default 32bit “armv71” to the 64bit “aarch64”

[Author]

Posts