-
Notifications
You must be signed in to change notification settings - Fork 89
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
Strange behaviour of CYW920819EVB-02 #44
Comments
Looks like you got a chip with a more recent patch level :) Ideally, it should have the same ROM, so you can simply copy the file as you did. The most important definitions in the firmware file define the memory layout and functions in the ROM, which will not change with firmware updates. On the evaluation boards, the patches, which are usually shipped as |
Ah, thanks for the explanation..I'm a little wiser again :) Is there a way to verify that the ROM layout remained the same as in |
hello, |
hello, |
Hello,
I noticed that when using the CYW920819EVB-02 dev board with internalblue on linux, the chip identifier has a strange value of
0x2305
, and the initialisation then falls back to using defaultfw.py
file.I browsed trough the available files and identified that the
fw_0x220c.py
should contain the values for this board, thus I copied the file and renamed it tofw_0x2305.py
to get matched with the board. However I am not sure that this approach is correct as well as the values.My questions thus is, why does the chip identifier differ?
Thank you very much!
The text was updated successfully, but these errors were encountered: