I've missed your reply. Recently took both and tried to connect them, with identical results(like before)adafruit_support_carter wrote:Thanks. Now repeat same process for PyBage #1.
Like I've stated before, dmesg is identical in case of both devices.
One starts CircuitPython, the other one starts simple game I've done quickly in MakeCodeArcade, like I've stated before.
The problem is none of them works over USB (USB LED stays RED, both in normal and bootloader upgrade mode[by pressing 'reset' button).
Both are LC versions, one unit got LC bootloader, the other one got 'normal' (non-LC) bootloader. But it shouldn't matter, because both worked after updating bootloader code for month(or maybe two), few times I've played with it, with my daughter.
Devices shouldn't brick like that, because 'smartctl -a' dumps S.M.A.R.T. data to json file, or sdparm changes APM mode (to prolong like of HDDs, or save-power on SSD drives).
This is the udev rule, I needed to comment, that caused hangs of PyBadges, before they USB connection failed totally:
Code: Select all
60-hddapm-badpixel.rules:#ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", RUN+="/usr/bin/hdparm -B 254 /dev/$name" # causes problems with PyBadge
It's very said that for me, that both PyBadges bricked so quickly, and Adafruit Devs have no clue, how to unbrick them, because both me and daughter really likes the form factor of it (and educational purpose).
Maybe I could try flashing them directly by STLINK v2 clone, or maybe there's some build-up of static electricity(and using jumper on some PINS, when powered-off, would help?)
Please help me, I really love this small devices :-(