CF doesn't work after forcing deck drivers

Post here to get support
Post Reply
thasu
Beginner
Posts: 15
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.

Post Reply