Recently, I have come into contact with the BL602 chip, but there is one thing to say, the documents and materials are indeed pitiful, or it may be because I am more skilled and can't understand it.
Alas, no matter what, let's set up the environment first.
The module I bought in a certain treasure, I will definitely buy it if I search it, so I won’t put the link here.
SDK source code download link: https://gitee.com/jixinzhineng/bl_iot_sdk.git
Burning software download link: https://dev.bouffalolab.com/download?chip=BL602%2F604
After downloading the SDK source code, unzip it. The docs/html/index.html in the SDK directory is for the development document, and only this one is the development document. Then follow the procedure inside to configure it, I won't write it again. But there are a few things to pay attention to.
1. Originally I planned to use Linux to develop, the system is Ubuntu 16.04, but I don't know why the compilation fails when I always compile the app. Later, I changed to msys64, but I couldn't make it through when I installed some libraries. Here I suggest to use msys64 and need to use the latest version , don't ask why, because I was scammed like this for several days.
2. The SDK actually comes with a burning software, but according to my previous situation, I still download the link of the burning software above to burn . According to the document, it is correct.
3. When downloading, IO8 should be pulled high and the jumper cap should be placed on the right H; when running, IO8 should be pulled low, and the jumper cap should be placed on the left L, and the internal IO8 of the module has been pulled down. If it is to change the jumper cap without power on, remember to press the reset button to reset it.
4. As long as the compilation is successful, there will be a build_out folder in the directory, and there will be a bin file inside.
Well, this is the problem I encountered in setting up the development environment, but the problem is still less documented, and it is only an evaluation at present, and see if I continue to use this chip in the future!