Skip to content
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

Problems using ltchiptool 4.6.0 to write kickstart-bk7231t-2023-08-29.uf2 #9

Open
DraakAnubis opened this issue Sep 30, 2023 · 1 comment

Comments

@DraakAnubis
Copy link

Get following error when writing flash with ltchiptool 4.6.0 and file : kickstart-bk7231t-2023-08-29.uf2

S [ 13.255] (+0.000s) -> RX: FF .
S [ 13.255] (+0.000s) -> RX: b'\x01'
S [ 13.255] (+0.000s) -> RX: E0 .
S [ 13.255] (+0.000s) -> RX: FC .
S [ 13.255] (+0.000s) -> RX: F4 .
S [ 13.255] (+0.000s) -> RX: b'\x06\x00\x07'
S [ 13.255] (+0.000s) -> RX: b'\x00\x00\x10!\x00'
S [ 13.553] (+0.299s) <- TX: 01 E0 FC FF F4 06 00 0F 20 00 20 21 00 ........ . !.
E [ 14.563] (+1.009s) ValueError: No response received
E [ 59.191] (+44.628s) |-- File "ltchiptool\gui\work\base.py", line 24, in run
E [ 59.191] (+0.000s) |-- File "ltchiptool\gui\work\flash.py", line 58, in run_impl
E [ 59.191] (+0.000s) |-- File "ltchiptool\gui\work\flash.py", line 109, in do_write
E [ 59.191] (+0.000s) |-- File "ltchiptool\soc\bk72xx\flash.py", line 204, in flash_write_uf2
E [ 59.191] (+0.000s) |-- File "ltchiptool\util\streams.py", line 156, in update_from
E [ 59.191] (+0.000s) |-- File "bk7231tools\serial_init
.py", line 149, in program_flash
E [ 59.191] (+0.000s) |-- File "bk7231tools\serial\cmd_flash.py", line 216, in flash_erase_block
E [ 59.191] (+0.000s) |-- File "bk7231tools\serial\protocol.py", line 210, in command

programing setup works tested with bk_writer1.60 and there firmware works but i like to test kickstart.
only deference i see is the communication speed of 1000000 and not 115200

@kuba2k2
Copy link
Member

kuba2k2 commented Oct 1, 2023

You're probably resetting the chip twice. Make sure to connect CEN to GND and release it on time. If you connect it again too soon, it will cause problems like this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants