-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
version 1.3 OF spi mem manager: XM25QH64C shows up as "Unknown SPI Chip" #112
Comments
|
Double checked wiring, its all correct, and the chip is known good, as I
pulled it from a working IP camera, just need to dump it and get the admin
password as the cam doesn't have a reset button.
I'll try another chip, and where on the flipper, might I find the logs?
…On Tue, Jan 23, 2024, 12:36 a.m. あく ***@***.***> wrote:
- Check wiring (maybe try to connect another chip)
- Check part number on the chip
- Check if anything detected or not in logs
- Is it new chip or old one? It may be damaged, try another one.
—
Reply to this email directly, view it on GitHub
<#112 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANOW4K4RPOWSVFVEGCKXPZ3YP5D7FAVCNFSM6AAAAABCGLY27SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBVGMZDINJZGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Logs are available in CLI or on GPIO UART. https://docs.flipper.net/development/cli#_yZ2E |
Tried another chip, slightly different part no... it reads fine. and i don't see the XM25QH64C in the flipper chip list. just the XM25L chips. |
Update: Very odd... for some reason, the flipper app store is installing version 1.0, even though version 1.3 is listed in the store. |
Accidentally closed the last post, sorry...
Anyways, in the changelog for SPI MEM MANAGER V.1.3, it shows that XM25QH64C support was added. i connected one of those chips and it's not being detected.
mine though is made by XMC, but has the same part number. Is there any way to get this to work? I have a device with this chip that i need to reflash the firmware on.
The text was updated successfully, but these errors were encountered: