Damndest thing I ever saw since I dumped the entire authentication username and password file on an IBM 360 at my college back in '76 using openly published system control card commands. . . Grade files, Registrar and Treasury files, every username and password on the system, EVERYTHING ! Of course, that’s a whole 'nother story.
The other day I decided to - finally - hook up the Vellman 3.5" touch-screen display to Charlie and try to set it up as a secondary display.
Poor Charlie. . . . Didn’t know what hit him. Next thing I know he’s absolutely INSISTING that he’s a Grove Pi, and there was NOTHING I could do about it. Run a Dexter Update? Nope. Change the “Detected robot” file to contain “GoPiGo 3” instead of “Grove Pi” Worked, kinda wonky until the next boot.
Ultimately the solution was to remove the Vellman display board that plugs into the first 26 pins of the GPIO. He thinks he’s a GoPiGo again, but he’s still very, very sick. Ultimately I’m going to have to re-flash R4R Buster and copy all my work back over. (I should really put it up on GitHub as soon as I find a dev environment that isn’t a clunky beast.)
So, @cleoqc, here’s my question:
What is it that distinguishes the GoPiGo from the Grove Pi? What would have to happen for Charlie to become so thoroughly befuddled that it basically whacked the entire installation of R4R?
Obviously the takeaway here is the old joke about the guy who went to his doctor and said:
“Doctor, it hurts when I do that.”
“Well then, don’t do that!”