help with HIC ID issue #956
-
Hello, PS if one google 'micro:bit stuck in maintenance mode' you will see that users also have micro:bit with HIC ID 97969908. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 24 replies
-
If you send an email to help@microbit.org (or open a ticket via https://support.microbit.org) the micro:bit support team should be able to help. |
Beta Was this translation helpful? Give feedback.
-
As I wrote previously I have 2 counterfeit micro:bits v1.5. Both have M26M7V and N51822 chips. One of them is running well on 0254 FW that came with it. It appears as MICROBIT drive and works well with Makecode and with other original micro:bits v.2 I also have. Here is details.txt: DAPLink Firmware - see https://mbed.com/daplinkUnique ID: 99013601066cff495751835187024435a5a5a5a597969908 As you may see it has 9901 in UID which refers to micro:bit board_id. However HIC ID is 97969908 which refers to STM32F103XB. If I start that micro:bit in MAINTENANCE mode the details.txt is: DAPLink Firmware - see https://mbed.com/daplinkUnique ID: 00000000066cff495751835187024435a5a5a5a597969908 You may see that UID starts from 0000. Another one counterfeit micro:bit is stuck in MAINTENANCE mode after attempt to flash it with original micro:bit FW because I had no idea that the product is counterfeit. His details.txt is: DAPLink Firmware - see https://mbed.com/daplinkUnique ID: 00000000066bff565349655287032725a5a5a5a597969908 You may see that Interface CRC's are different. I digged a bit into DAPLink source code to find a solution and have few questions: Does it mean that both micro:bits have flashed boatloader with stm32f103xb_bl? When I try to flash kl26z_microbit_if.hex FAIL.TXT shows: Is it OK to flash 0257 interface to 0254 bootloader? What can I investigate from Interface CRC? Regards, |
Beta Was this translation helpful? Give feedback.
-
I tried to change IF ROM addresses but it looks like micro:bit IF FW is 95Kb (0x17C00), but with STM32 bootloader there are only 79Kb (0x13C00) available for the IF ROM. So that's mean that I need to reflash bootloader with KL26Z_BL.HEX. However counterfeit micro:bit worked well with STM32 BL. Does anybody have an idea what to do with KL26Z_MICROBIT_IF source to make it possible to flash it at 0x0800C000? |
Beta Was this translation helpful? Give feedback.
-
I tried to build IF firmware: Changes in projects.yaml:
Microbit.yaml: common: Changes in microbit.c: #include "IO_Config.h" I compiled and flashed it well and DETAILS.TXT now is: DAPLink Firmware - see https://daplink.ioBuild ID: 83a882d (gcc, local mods) However it doesn't work with any HEX file produced by Makecode, FAIL.TXT is: What did I wrong? Any idea please? |
Beta Was this translation helpful? Give feedback.
-
fake_Microbit V1.1 zip |
Beta Was this translation helpful? Give feedback.
-
fake_Microbit_V1.1.zip Try this file. |
Beta Was this translation helpful? Give feedback.
-
Thanks,
Its working again
Greetings Benny
Op za 21 jan. 2023 16:35 schreef Rodrigo Couto ***@***.***>:
… fake_Microbit_V1.1.zip
<https://www.mediafire.com/file/m41o34rf8pk9a42/fake_Microbit_V1.1.zip/file>
Try this file.
—
Reply to this email directly, view it on GitHub
<#956 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJUPD4OTBMVOWJLU5YQROO3WTP63DANCNFSM5T5BCNVA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
fake_Microbit V1.1 zip
Try this 。zip 2 bin