martinwoodward / martinwoodward/PyFluff

Unable to flash DLC to Furby Connect

Open
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
121
Forks
22
PR merge metrics
No merged PRs in 30d

Description

Hi, excellent work. Server and web page work just fine.

However, I'm trying to use custom_dlc.py to upload a DLC to my Furby Connect. (server not running to allow connection).

It presents %done during the uploading but I don't see any change in my Furby. I tried the Hacked.dlc expecting to get some confirmation of success but nothing happened after the program closed. I did increase the sleep to 30s after 'Activating DLC' but nothing happened.

The debug 6 screen shows no changes (I had it visible throughout).

Others have had success so I guess it's just me (or my Furby) - I have read loads of repos and tried other dlc uploaders to no avail.

I guess I'm not getting my Furby into a state to accept an upload of a DLC.

What is the preferred sequence of actions required to make this work please?

BTW, why is the default slot set at #2? I have tried a variety of slots with no effect.

I would appreciate some hints on how to do this please.

Thanks.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with custom_dlc.py and trace the upload sequence through the “Activating DLC” step, using the debug 6 screen and Hacked.dlc reproduction described in the report. Compare the expected device state and slot handling with the existing uploader behavior; done means identifying why the Furby does not accept the upload or documenting the required action sequence.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.