Problems encountered in debugging Pingtouge's scenario-based Bluetooth Mesh

littleshrimp

Problems encountered in debugging Pingtouge's scenario-based Bluetooth Mesh [Copy link]

 

 

Today, I am preparing to connect the module to the network according to the Bluetooth MESH Gateway Development Board Quick Start Guide. The following problems are encountered when following the manual:

1. Getting the MAC address of the gateway is done by inputting wifi-mac in the cli. What does cli mean here? Is this command sent through the serial port assistant?

Second, because I didn’t notice that I had to use the mac address as the DeviceName, there was no option to delete the wrong test device that I added.

3. It may be because the test device cannot be deleted, which causes the newly created project to be unable to be deleted.

These two test items cannot be deleted. When deleting them, it prompts that there are devices below. When deleting the temperature and humidity node above, it also prompts that there are devices under the node. It is guessed that the device under the node should refer to the test device, but the test device cannot be deleted, resulting in the inability to delete the entire project.

4. An internal service exception error occurred when adding a device to the Pingtouge Chip Open Community. It was normal after repeated login.

Later, considering that W800 should download firmware, I downloaded CDK. When the original path was opened, CDK would crash. This is because there is Chinese in the path, which is a normal phenomenon. However, domestic IDE is recommended to support Chinese paths.

5. Because I don't have CK-LINK, I considered using the serial port to download. I went to the official website of Lianshengde and downloaded W800 serial port burning tool_V1.4.8.rar, but the download failed immediately. It only prompted Download xxx fail. There was no prompt as to why it failed.

Start the download ...

Download "E:/gateway_released_sdk/solutions/ble_mesh_gateway_demo/generated/total_image.hex" fail!

littleshrimp

In addition, this path should include the project name, otherwise if there are too many projects, you will have to go back to the main directory every time to enter the corresponding project.

littleshrimp

Now it is confirmed that although the extension of the serial port firmware is written in HEX, it can only download .fls files. There is no description on how to generate .fls files. CDK does not generate .fls files by default.

littleshrimp

The new development is that the .fls file should require the program wm_tool.exe to generate,

However, I haven't found any specific instructions on how to use this software.

Not much information can be obtained by searching using corresponding keywords.

littleshrimp

Why didn’t I find it? Because I was lazy and didn’t use Google.

littleshrimp

On the official product page of W800, the only document is WM_W800_Parameter Area Usage Instructions_V1.2.pdf. The 1.2 version no longer has the instructions for wm_tool.exe.

The .img file just generated is the information in the document "WM_W800_Parameter Area Usage Instructions V1.0" found by searching on Google.

littleshrimp

I forgot which document I saw that .fls requires secboot. Try adding -sdb W800_secboot.bin and you will get the following prompt.

The WM_W800_Parameter Area User Manual V1.2 is all for operation under Linux. If you don’t know Linux, I don’t know if you can still download the W800 firmware.

littleshrimp

WM_W800_Firmware Upgrade Guide V1.1 says that after compiling the SDK, a w800.fls file will be generated.

There are indeed these files in the bin directory of the SDK. I checked the time and found that they were just generated. It turns out that this document did not deceive me.

In the past, other brands of microcontrollers did have a bin file in some SDKs. This file was always the original compiled file from the official routines. The files modified by the user were always in the directory corresponding to the project. I didn't expect that the bin file in the root directory of the SDK was the newly compiled one. Finally found it.

With this experience, I compiled the gateway SDK of gateway_released_sdk again. After searching, I found that yoc_total.fls and yoc.fls were the files just generated.

I still don’t know the difference between total and no total, so I’ll just try it out. Finally I see success.

littleshrimp

However, after downloading the .fls file without TOTAL, the MCU is still in the BOOT state, and CCCC is still printed when restarting and powering on again.

After burning the total .fls file, it can work normally and prompts the following message. It seems that this prompt was also there when I first got the board. Now I am not sure whether this status is normal or abnormal. I didn’t see any explanation in the manual.

littleshrimp

Follow the instructions in the document to copy the previously downloaded KP file to E:\gateway_released_sdk\boards\IoTGW_CB800\bootimgs, and then recompile with CDK (not sure if just copying it will work?)

After compiling, download the yoc_total.fls file next time.

After powering on again, the same prompt appears. Is this normal or abnormal?

wangerxian

It seems that there are quite a few problems. I hope they can be optimized!

littleshrimp

Here rename means rename, right? Do you mean rename the KP file to fcds? There is no extension, right?

littleshrimp

This time I renamed it

Then I was afraid of problems, so I rebuilt it, not built it.

Then I re - download the yoc_total.fls file generated by the re -build project after the kp file after my re -name

Restart , or the original prompt,

littleshrimp

I compared it and the output in the manual is different.

littleshrimp

After "carefully" analyzing the log, it seems that there is something wrong with this sentence. Is there no ID? Is it the MAC address?

littleshrimp

I tried using OCC Gateway Config Tool.exe, USB connected to J1, AT command interface, and can upgrade the gateway firmware.

I said call settings_load() before, I looked for the settings_load function in the project

The definition of CONFIG_BT_SETTINGS is as follows, and the definition of BLE_MESH_SETTINGS is not found

Change the code directly to this, compile, and download

The error message doesn't change, maybe the call is wrong?

littleshrimp

I looked at the document carefully again, and it seems that the official document also has a reminder that App must call settings_load(). The problem is not here, but why is the output different?

My tips are:

[ 2.608]<I>AOSBT bt_dev_show_info:HCI: version 5.0 (0x09) revision 0x0120, manufacturer 0x0504

[ 2.610]<I>AOSBT bt_dev_show_info:LMP: version 5.0 (0x09) subver 0x0208

[ 2.650]<D>GATEWAY_MESH mesh node init ,and it has been proved

[ 2.655]<W>BT_MESH_NODE mesh node provisioner enable success

[ 2.656]<D>GATEWAY_MESH mesh node provisioner init success

The manual says:

[ 2.822] AOSBT bt_dev_show_info:HCI: version 4.0 (0x06) revision 0x0120, manufacturer 0x0504

[ 2.838] AOSBT bt_dev_show_info:LMP: version 5.0 (0x09) subver 0x0208 Bluetooth init succeed.

[BZ] Breeze adv per device

[BZ]Breeze unbind

[BZ]need awss

Here are some more tips I have:

[ 2.650]<D>GATEWAY_MESH mesh node init ,and it has been proved

[ 2.655]<W>BT_MESH_NODE mesh node provisioner enable success

[ 2.656]<D>GATEWAY_MESH mesh node provisioner init success

未来开发者

Answering a few questions about the post:

1. Yes, cli is to send commands through the serial port assistant. cli is the command line service. You can enter commands on the log serial port for debugging. The wifi_mac command mentioned in the manual is used to view the wifi mac address of W800;

2&3. For how to delete devices on the Life IoT platform, please refer to this document: https://help.aliyun.com/document_detail/126546.html

4. Clear your browser cache and try again

5. The serial port tool can only download fls. The fls is generated in: out/<project name>/ (<project name> is the actual CDK project name). After successful compilation, the fls file of the gateway SDK is generated in the example root directory, gateway_released_sdk\solutions\ble_mesh_gateway_demo\yoc_total.fls

littleshrimp

Future Developers published on 2021-10-31 12:14 Answer a few questions about the post: 1. Yes, cli is to send instructions through the serial port assistant, cli is the command line service, which can be used in daily...

Thanks for your reply. I have successfully deleted the device, obtained the MAC address, and generated and burned the KP of the gateway.

After configuring the SSID and password, you can connect to the Internet normally.

ifconfig returns information

Ping occ.t-head.cn is also normal

But there are still some error messages, such as

<E>AOSBT adv_send:Advertising failed: err -22 and <E>dev_mesh don't have correct occ_pid

In addition, I also encountered some problems when downloading the node firmware. I hope you can help me take a look. Thank you.

https://en.eeworld.com/bbs/thread-1184193-1-1.html