CF doesn't work after forcing deck drivers

Post here to get support
Post Reply
thasu
Beginner
Posts: 21
Joined: Wed Oct 18, 2017 7:16 am

CF doesn't work after forcing deck drivers

Post by thasu » Thu Jul 12, 2018 11:41 am

Corrupted OW memory message appears in the console when I plug one of my decks. After forcing the driver by adding it to the config.mk and using Make Debug to compile, it didn't boot properly. By adding DEBUG=1 in config.mk the deck started to work but there were some issues. When I give set_hoverpoint, it didn't fly and started to flash 2 red LEDs, but the data logging python code run properly.

arnaud
Bitcraze
Posts: 1707
Joined: Tue Feb 06, 2007 12:36 pm

Re: CF doesn't work after forcing deck drivers

Post by arnaud » Fri Jul 20, 2018 7:13 am

A corrupt memory error means that the memory has not been programmed and only firmware compiled in debug mode can use it (since firmware in release mode will disable all deck if it sees one with a programmed memory). So the fact that you need to set DEBUG=1 is normal.

The two red leds seems to be an unrelated problem but to help for that it would be useful to know what deck and what version of the firmware you are running.

kevinspencer
Beginner
Posts: 1
Joined: Tue Aug 07, 2018 9:01 am

Re: CF doesn't work after forcing deck drivers

Post by kevinspencer » Tue Aug 07, 2018 9:03 am

What error are you guys talking about? I suppose that now it should work well.

Post Reply