logo elektroda
logo elektroda
X
logo elektroda
Dostępna jest polska wersja

Czy wolisz polską wersję strony elektroda?

Nie, dziękuję Przekieruj mnie tam

Easy Flasher: BK7231N/T/BK7238 etc chip ID check for Beken devices?

divadiow 42 0
ADVERTISEMENT
  • #1 21876721
    divadiow
    Level 38  
    <post moved from here to keep separate>


    @DeDaMrAz suggested a more robust chip ID check in EF so in the cases where mislabelled CB2S may actually be a BK7231T and not a BK7231N, Easy Flasher will flag and stop current operation before starting. This suggestion was based on real recent experience.

    So maybe something like https://github.com/openshwprojects/BK7231GUIFlashTool/pull/118/changes?w=1

    -move chipID stuff into new file Flashers\BKChipIdentity.cs
    -chipid dictionary for supported and a couple of OBK-unsupported BK chips
    -if chip should return chip ID but fails to, log warning to suggest wrong chip may be selected. eg, BK7231N selected, BK7231T device:
    Screenshot of BK7231 Easy UART Flasher showing “Interrupted by user” and read error logs.
    -if chip returns ID not matched to selected chip, log fail and stop. eg, BK7238 selected but BK7231N device:
    Screenshot of BK7231 Easy UART Flasher showing a warning that the selected chip type is wrong.

    -expand use of 'skip key check' to 'skip chip/key check'
    Screenshot of a tool window with tabs “LAN Scanner”, “UART timeouts”, and “BK7231N Decryption”.
    eg, BK7238 selected, BK7231N device, skip checked:
    Screenshot of BK7231 Easy UART Flasher showing “Reading success!” and COM6 settings

    -BK7231M behaviour remains as no key check enabled by default but does log chip ID:
    Screenshot of BK7231 Easy UART Flasher showing “Reading success!” and a flash read log.

    I do not have BK7258/BK7236.



    03/04/2026 - I do now have BK7258 - will check and post again
  • ADVERTISEMENT
ADVERTISEMENT