CB5654 Development Board Review 4

tobot

CB5654 Development Board Review 4 [Copy link]

 

In the previous article ( https://bbs.eeworld.com.cn/thread-1187579-1-1.html ), the environment has been set up. We select "New Project" in Welcome . On a computer with a lower resolution, you may need to drag the scroll bar back and forth to find this link:

New Construction

Select SC5654 chip,

Click Next to create an IoT project. For CB5654 , there are two examples. First, select "Driver Development Example" and name the project " test ". You can see that the version is V7.2.2.1 :

Click Finish , and it will be automatically downloaded to the local disk. You can see that the introduction of this project ( README.md ) indicates that this example is used to implement system APIs and various drivers:

Start building the project through the menu bar " Project->Build Active Project " or the shortcut button " Build Project " or the keyboard " F7 ". Depending on the computer performance, it may take tens of seconds to several minutes. In the " OutPut View " at the bottom , you can see the words " 0 error(s), ...". According to my experience, as long as the code is moved, some " warnings " will inevitably appear, which can be ignored. As you can see, my computer performance is very average, and it took 8 minutes to build this project .

Look carefully, something seems wrong. Why is there " No such " on it? Let's take another look.

Obviously the environment is not installed properly.

Copy all files in the folder __workspace_pack__\cb5654\v7.2.2\ to the specified directory \test\Boards\cb5654\v7.2.2\ , and then execute build again .

As you can see, the result this time is completely different from the last time:

Use the menu bar " Flash->Download " or the shortcut button " Flash Download " to download the built code to the board. Then this appears:

Obviously, the board is not connected or not set up yet. Use " Setting->Target Setting ":

Click " OK " and you will see that the target chip has been recognized:

In the menu " Control->RunDebuggerServer ", pull up this service, and you can see that the shortcut buttons and status bar on the interface have changed:

Go back to CDK and try to download Flash , and finally it appears:

Replace the USB interface on the board, use SecureCRT to operate, and press the restart button on the board:

The system stays on the above interface for more than 5 minutes, still does not proceed to the next step of printing, and the input has no response. I don't know the reason.

tobot

Another example is also compiled and burned successfully, and an error message will be prompted

tobot

Create a " test2 " and use the "Intelligent Voice Terminal Solution" according to the documentation:

Refer to the document operation, you can see that this is a voice application, and " build " the project again . After a long wait, it finally succeeds. This time there are some warnings, which can be ignored for now, as follows:

Burn it into the development board and use the serial line to check the information. You can see that BT_LOG has an abnormality and the next step has not been taken for a long time:

Looks like:

BT_HCI command_timed_out hci layer timeout waiting for response to a command.

Something went wrong. Judging from the comments, it seems to be waiting for a command response.

I tried to find the error point by single-step execution, but I am not very good at using CDK . I couldn't find the location of the error print by searching the file. I really don't know what to do next, so I posted this for help.

nmg

Feedback has been sent to Pingtouge, waiting for their technical support

In addition, the title should have a clear theme. 1, 2, 3, 4 are a bit abstract.

未来开发者

tobot posted on 2021-12-2 23:12 Another example is also compiled and burned successfully, and an error will be prompted

Please tell me which routine it is

未来开发者

This is probably because the Bluetooth circuit of 8723ds is not soldered properly, resulting in the failure of software Bluetooth initialization. If you have the hardware capability, you can re-solder RTL8723 and then re-solder it to see the result. It is recommended to contact the staff for direct replacement.

tobot

Future Developer published on 2021-12-3 15:21 This should be because the Bluetooth circuit of 8723ds is not soldered properly, resulting in the failure of software Bluetooth initialization. If you have the hardware capability, you can re-solder the RTL8723...

Received. The board has been sent back. Will continue the evaluation after receiving the replacement.