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
HolyBro Kakute H7 Mini ESC Firmware Issue (Blackbox) #11440
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
@SteveCEvans any idea about this resource? |
The KAKUTEH7MINI FLASH device is reporting an ID of 0xEF3016 which we don't currently support. The fact that I get that far means the config is correct. Now trying to figure out what that device is. The KAKUTEH7 FLASH device is not responding at all, so that may be more of a challenge. |
I've faked the same config in the FLASH detection as a W25Q128 and I can write and read BB logs, but I need to confirm the FLASH geometry before raising a PR. |
I'm seeing four copies of each log. The device is behaving like a 32Mbit device, and the device ID ending in 16 suggests that is the case. Treating this as if the ID is 0xEF4016 gives a 4Mbyte FLASH that works as expected. Query of the device ID with Winbond technical support... |
🤯 Including #11537 did not solve it. |
Try this image. |
|
The hex solved the problem (making the Onboard flash available in configurator instead of showing a blank option, still configurator thinks it also has an SDCard)
|
Oh dear. the FLASH is a W25X32, marked as a W25Q128. https://www.winbond.com/resource-files/w25x32a_revb_080709.pdf#page14 |
@JPOVPhoto Bad news... this is not a firmware issue. Your onboard flash chip is not what it is supposed to be. |
Vince with Holybro here. After the first production cycle, we found that there were a small percentage of the flash on the KakuteH7 Mini being W25X32, but marked as a W25Q128 (what it supposed to have). We immediately checked all our inventory and done reworked at that time, but now it looks like there may be a very small quantity of board with the W25X32 flash that was already shipped. All our Kakute H7 Mini board since then does not have this issue. Sorry for seeing this post so late. |
Describe the bug
I can't access the onboard flash for Blackbox Data. This happens in the following versions of Betaflight Configurator 10.7, and 10.8
Here is my issue. In the dump I have the following resource defined for the flash memory which is the unified target default value for the Kakute H7 Mini FC...
Code:
resource FLASH_CS 1 A04
In the active IO resource assignment list I have the following...
Code:
A04: PREINIT 2
If the blackbox flash chip had been assigned and initiated properly then you should be seeing the following in the active IO resource assignment list for A04...
Code:
A04: FLASH_CS
This occurs in both 4.2.10 and 4.2.11
To Reproduce
Go to The Black box tab in Betaflight and attempt to switch blackbox to "onboard flash," but the option isn't there. You can choose serial, or none.
Expected behavior
I should be able to choose onboard flash.
Flight controller configuration
Flight controller
Holybro Kakute H7 Mini (purchased from Pyrodrone)
Other components
Caddx Vista (most recent firmware)
TBS Crossfire Micro TX with Nano Diversity (not the most recent firmware)
How are the different components wired up
Vista is connected to the FC via supplied jet plug. The FC is connected to the ESC via supplied cable and just plugs.
The TBS Nano Diversity is is wired per the diagram on the Holybro website.
Add any other context about the problem that you think might be relevant here
No response
The text was updated successfully, but these errors were encountered: