-
Notifications
You must be signed in to change notification settings - Fork 6
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
Non-zero status code: BkFlashRead4KResp(status=6, start=0x0, data=bytes(1)) #34
Comments
Try running Get chip info. It might be falsely detecting the chip type (T/N/etc) which could cause incorrect reading options. Also, please post the full log of the flash operation (even better with enabled debug log level). |
|
so is this chip supported by libretiny platform, or did i just wasted my money , i thought all 7231 is supported so i bought too much of them at once |
It can be supported, don't give up yet. Apparently this bootloader could be locking readout from 0x0. Try using bk7231tools to read the flash chip contents:
|
|
Right, so it seems it detects the flash size correctly. |
dump.bin.txt |
Just curious, where did you find these BK7231S chips? We've never seen this particular model before, are these available to buy somewhere as bare chips? |
https://fcc.report/FCC-ID/2AR7VC-8133U/4225568.pdf |
is there any chance for this to work |
Yes. You can probably just flash ESPHome, provided that you use this in your YAML: esphome:
name: my-device-name
platformio_options:
board_build.bkcrypt_coeffs: 00000000000000000000000000000000
board_build.bkota.key: 0123456789ABCDEF0123456789ABCDEF
board_build.bkota.iv: 0123456789ABCDEF
board_flash.calibration: 0x1F3000+0x1000 Note that the bootloader on this device is the oldest we've seen, it looks very much different from all the standard bootloaders. After compiling ESPHome, try flashing the As long as you don't flash anywhere in between 0x0 and 0x11000, you should be fine. |
what cpu should i select in esphome |
You should use |
Hm, maybe YAML is converting the coeffs to integer. Try wrapping it in quotes, like |
what version do i download for cli tool |
the Beken Application Image for direct flashing |
it is not very easy to flash this because the cp2102 code not have auto reset, and i lost my ch340 |
Unfortunately I don't have a fix for that. It's not possible for me to fix such low-level issues without physically owning such a chip. You could try flashing the same RBL file using other software, such as BkWriter. It should only be used as a last resort. |
how can i send you one of these |
If you don't live anywhere near Poland, I think it would be much more expensive than the entire device is worth 😄 |
it is def more expensive then this is worth, but if you cant buy it there its the only option |
beken writer erase flash also fail |
what version of bkwriter was it? |
1.60 |
chip may or may not be supported, new to none esp, cannot tell
The text was updated successfully, but these errors were encountered: