MDK Issues - Unable to test examples

Hey all,

Ive been testing out some of the examples. Initially everything was fine. I got each to run once. After that, no matter what i do and no matter which personality card I use, I get an error when it tries to update the firmware. My buddy is having the same issue. Anyone else experience this? How did you overcome it? Thanks.

Top Replies

twhalen08 over 8 years ago +1

Clear application data for the Moto mods manager service and reattach. That solved it for jlavigne08 and I. I do have a bad audio card tho

Parents

twhalen08 over 8 years ago

Clear application data for the Moto mods manager service and reattach. That solved it for jlavigne08 and I.

I do have a bad audio card tho
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel

Reply

twhalen08 over 8 years ago

Clear application data for the Moto mods manager service and reattach. That solved it for jlavigne08 and I.

I do have a bad audio card tho
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel

Children

flowflow25 over 8 years ago in reply to twhalen08

Thomas, how did your audio card go bad?

Antti, please check the Play store for the latest Mod Manager. Sadly, erasing the apps data is the current workaround while we resolve this.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
anttibrain over 8 years ago in reply to flowflow25

apps data delete was the fix, everything was uptodate already
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
twhalen08 over 8 years ago in reply to flowflow25

Hi Christian. All of the other personality cards that i received seem to work just fine when the dips are set correctly. All except for the audio card. The audio card will just come up as blinky.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
flowflow25 over 8 years ago in reply to twhalen08

You're experiencing the firmware download issue, we're working on that. The "good news" is that it only applies to the MDK, not any commercial Mods. Erasing the Moto Mods Manager's app data should get you going again.

Of course, you could also build the audio firmware and flash it directly with either the MDK Utility or openocd.
Another note is to make sure the card is seated properly, it almost sounds like the bootloader can't read the EEPROM in the Personality Card the defines the PID. If it continues to come up Blinky (MDK Utility shows Blinky, not simply "Firmware") we may need to take some steps to program the EEPROM (it isn't terrible).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel