Hi-Link HLK-B30 Development Board with C-Chip CC8000 and OpenBK7231U Firmware

Question

There are a few posts around that reference the C-Chip CC8000/BK7231U chip and that it can be found on the Hi-Link HLK-B30 development board, but experiments with it appear mixed in with several other threads, so here's a thread dedicated to the HLK-B30 and now with OpenBK7231U. [line...

insmod · Accepted Answer

To make sure that MAC and calibration data is correct TLV must be moved from 0x1FE000 to 0x1E0000 on BK7231U.

insmod · Accepted Answer

In ESPHome it is not important where TLV is located, it can be adjusted at build. Code: text Expand Select all Copy to clipboard esphome:   name: Your Name   friendly_name: Your Name   platformio_options:     board_flash.tlv: 0x10000+0x1000, Change 0x10000 to wherever it is located. For BK7231U those are also appliable Code: text Expand Select all Copy to clipboard     board_build.bkcrypt_coeffs: 00000000000000000000000000000000     board_build.bkboot_version: 0.1.4-bk7231u     board_build.mcu: bk7231u With bkcrypt_coeffs zeroed, you could flash it via uart.

jmkrzyszt · Accepted Answer

>>21589904I've followed ESPHome instructions provided by @insmod (thank you!) and I've been able to flash my BK7231U ESPHome image (.rbl) to CC8000 over UART. However, original MAC address was not detected and got overwritten with C8:47:8C:42:00:48 (similar to C8:47:8C:42:88:48 with OBK).I've examined platformio documentation for BK7231T and compared a BK7231T factory image vs the BK7231U factory image. Based on that, I've managed to resolve the MAC issue by replacingCode: YAMLLog in, to see the codeentry with﻿Code: YAMLLog in, to see the codeand re-flashing (OTA).Thank you @insmod and @divadiow for your support.Additional note: in the board_build.bkcrypt_coeffs entry, the string of zeros must be quoted, otherwise the build fails.

divadiow · Answer

OTA test success. this was with quick GUI page Code: TextLog in, to see the code web app OTA filtering for .img not .rbl currently Added after 7 [hours] 42 [minutes]: @akosschneemaier this fw should work on your AiDot Leedarson module bulb if you still have it

divadiow · Answer

adding v2.1 pics from for ref debug log has been from TX2 (D12/P0)

jmkrzyszt · Answer

Hi, I can see BK7231U images officially included in 1.18.125. Is it safe to flash the BK7231U image with uartprogram to a CC8000 device?

divadiow · Answer

>>21588692 what is your device, module etc?

jmkrzyszt · Answer

>>21588807 That's a Winees WS010078261 RGBW bulb, with this module: >>21025914 (the one made by Leedarson).

divadiow · Answer

could give it a go? Maybe start by taking a full backup from 0x0 and I test your bootloader with the BK7231U release, make sure it boots and see if OTA works? also, not sure if this would be an issue for a full freeing from cloud for your device. Added after 1 [minutes]:that assumes you'll only be able to flash over UART though so cannot replace bootloader. Do you have CH341A?

jmkrzyszt · Answer

>>21589202 I'm attaching backups of factory firmware taken already before, one with uartprogram (.img), another one with bk7231tool (.bin). Does any of them contain the bootloader you'd like to examine?I don't have a CH341A, I've been flashing with an FTDI based USB-serial adapter.

divadiow · Answer

ah yes, I remember now. The other Leedarson dump we have is just as chatty on log out. Well, your 2mb backup boots just fine. Code: TextLog in, to see the code with OpenBK7231U_UA_1.18.125.bin renamed to OpenBK7231T_UA_1.18.125.bin and flashed with EF in T mode then OpenBK7231U boots. BL still silent. It is BK7231U_1.0.6, however. Code: TextLog in, to see the code Device has the same generic mac as my QIO flashed example on HLK-B30 - C8:47:8C:42:88:48 - not the mac your factory fw is seen with - 1c:d6:bd:d4:57:83 Looks like TLV is at 0x10000 in your fw - your original mac can be seen in there: regarding TLV location, the same is true of the other AiDot Leedarson dump: So I guess if these types prove popular they may justify a release build to cater for the odd TLV location, with ref to: factory OTA is at 132000, as it is with OpenBK7231U. here shows OBK OTA in progress with your bootloader Code: TextLog in, to see the code silent as the BL OTA process may be, it is still successful. I flashed down to PR build 1680_merge_55ebe0a12aba from 1.18.125 and it came back up as that. (I did get malloc failed with both OTA gui/app methods quite a bit). So, I guess it's TLV that's the most obvious issue Added after 12 [minutes]:manually setting mac in OBK does not seem to be supported at present. Comes back up as original

insmod · Answer

Is TLV header where it is now gets overwritten? We can't simply change where it is located, since OBK config and flash vars are dependent on its location. And perhaps bootloader log is on UART0?

divadiow · Answer

ah OK OK Here is dump of HLK-B30 with original Leedarson fw + OBK + those two OTAs mentioned above and the mac address change attempt original TLV remains

insmod · Answer

>>21589584 Then it means we need some function on OBK (web app?) to read it and then write it at needed offset.

divadiow · Answer

nothing on USB/CP210x P11 only D12/P0

jmkrzyszt · Answer

>>21589591 Hi, thanks for your efforts. AFAICU, the answer to my question is: yes, it's safe to flash my device with OpenBK7231U UART image, renamed to T, using BK7231 Easy UART Flasher. However, OBK is not yet able to detect and use device's MAC address from TLV and replaces it with its own, always the same, so only one device can be connected to a network (broadcast domain). Does that describe current status correctly?

divadiow · Answer

yes. that sounds like an accurate summarisation of the current situation to me. which I believe puts you in the same position as with your ESPHome efforts

jmkrzyszt · Answer

>>21589202 >>21589904 >>21589904 Perfect, thank you! I'll give it a try tonight and report.BTW, is that 0.1.4-bk7231u a dummy placeholder just to avoid pulling a conflicting T bootloader (and using the one from flash instead), or does it point to an existing U bootloader version?Is there anything else I can do for you and your project about my device?

insmod · Answer

>>21589989 It is a placeholder, but not for pulling T bootloader. If a default bkboot_version (for T) is detected, it sets a specific variable, that changes how it boots. It is a specific Tuya change, without it BK7231T bootloader doesn't fully boot. And if it is enabled on non-Tuya bootloader - it won't boot too. Extra: if you have the ability to flash via SPI (bootloader can't be flashed via UART on BK7231U/T/S), you can flash BK7231T bootloader and use normal T firmware (albeit built with zero keys). Though since it is now possible to flash U devices, it is not needed.

divadiow · Answer

is this a possible/likely work-around?

insmod · Answer

>>21590030 There is a read command. This is a choice of either adding separate write and erase commands and adding a script in web-app, or just adding a read TLV, erase destination and write what we've read, directly on device in one function.

Pin	Pin Name	Type	Descriptions
1	CEN	I	Chip enabled, highly effective
2	P26_PWM5	I/O	P26,PWM5
3	P24_PWM4	I/O	P24,PWM4
4	P23_TDO_F_S0	I/O	P23,ADC3
5	P22_TDI_F_SI	I/O	ES0, enter at command mode / restore factorysettings, please pull up if not used, same as P28
6	P21_TMS_F_CS	I/O	P21
7	P20_TCK_F_SC	I/O	P20
8	VBAT	P	3.3V power supply
9	P28	I/O	Enter at command mode / restore factory settings, please pull up if not in use, same as P22
10	P16	I/O	P16
11	P17	I/O	P17
12	P14	I/O	P14
13	P15	I/O	P15
14	P6_PWM0	I/O	P6,PWM0
15	GND	P	GND
16	P7_PWM1	I/O	P7,PWM1
17	P8_PWM2	I/O	WiFi indicator light
18	P9_PWM3	I/O	P9,PWM3
19	P1_URAT2_RXD	I/O	P1,UART2
20	P0_UART2_TXD	I/O	P0,UART2
21	P10_UART1_RXD	I/O	P10,UART1, For upgrading, command settingand transparent transmission
22	P11_UART1_TXD	I/O	P11,UART1, For upgrading, command setting and transparent transmission

HLK-B30	CH341A
RST	D2
D17	SCK
ESO/D16 (between D17 and D15)	CS0
ESO (between GND and D1)	MOSI
D15	MISO
GND	GND

Hi-Link HLK-B30 Development Board with C-Chip CC8000 and OpenBK7231U Firmware

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Topic summary