Bitcraze Forums

When using the micro-SD deck with the Z-Ranger V2 together on my crazyflie 2.1, the self-test occures twice than fails.
I use the latest firmware on my crazyflie. I also tried older firmware without success.
Those boards should work fine out of the box together as mention on the compatibility table. https://www.bitcraze.io/docs/cf2_expansiondecks/
The problem seems to happen when there is a config.txt file in the micro-SD card.
When looking at the console in the python client I get this:
SYS: The system resumed after watchdog timeout [WARNING]
SYS: No assert information found

Those boards work well separatly on my crazyflie which makes me believe that they aren't broken.

Thank you!

Hi!

They should be working together indeed. So let's find out what is happening.

You mentioned this happens when config.txt is on the sdcard. The assert does not happen when this file is not on the card? Could you send us the content of config.txt?

The assert doesn't happen when the file isn't present.

Here is the content of config.txt:

1 # frequency
10 # buffer size
log # file name
1 # enable on startup (0/1)
2 # mode (0: disabled, 1: synchronous stabilizer, 2: asynchronous)
acc.x
acc.y
acc.z
ctrltarget.roll
ctrltarget.pitch
ctrltarget.yaw

kimberly wrote: ↑Tue Feb 25, 2020 8:56 am Hi!

They should be working together indeed. So let's find out what is happening.

You mentioned this happens when config.txt is on the sdcard. The assert does not happen when this file is not on the card? Could you send us the content of config.txt?

The assert doesn't happen when the file isn't present.

Here is the content of config.txt:

1 # frequency
10 # buffer size
log # file name
1 # enable on startup (0/1)
2 # mode (0: disabled, 1: synchronous stabilizer, 2: asynchronous)
acc.x
acc.y
acc.z
ctrltarget.roll
ctrltarget.pitch
ctrltarget.yaw

I think this is a memory issue and I bumped into it as well when trying to add functionality so the micro-SD could more easily be moved to SPI3 bus. I have attached a STM32 FW with the changes I made. Can you try this? I will try to get these changes to the master branch during the week.

tobias wrote: ↑Mon Mar 02, 2020 1:58 pm I think this is a memory issue and I bumped into it as well when trying to add functionality so the micro-SD could more easily be moved to SPI3 bus. I have attached a STM32 FW with the changes I made. Can you try this? I will try to get these changes to the master branch during the week.

It seems that you found the solution to my problem! No error occured and I am able to log with the micro-SD card with the range sensor plugged in.
Thanks alot!

Great @tobias ' binary worked! I will notify this as an issue on github so we will fix this in the official firmware as well. Thank you for letting us know.