I want to create and integrate a Bluetooth mesh network using CYW920820EVB-2 boards. Can someone please guide me with appropriate documents and procedure to build the Bluetooth mesh network using Modus Toolbox? I was trying to do that with Modus Toolbox 2.0 but could not find any appropriate documentation for integrating 820 mesh. I tried with Modus Toolbox 1.1 also but in that I could not find CYW920820EVB-02 to select. Help in this regard will be really appreciated.Show Less
Could not start debugging with CYW920819EVB-02 , Also could not use external Jlink debugger. Installed latest ModusTool Box 2.0
Previously everything was working with ModusToolBox 1.0
I recently purchased some CYW920819EVB-02 Evaluation Kits. I am trying to program one of Cypress sample applications (Light Dimmable) via USB (without a debug probe) using ModusToolbox 2.0. I am not able to find instructions on how to do this. In my ModusToolbox Quick Panel I do not see any “Build + Program” option in the Launches section as mentioned in the ModusToolbox IDE User Guide. So do I need to create a launch configuration for the CYW920819EVB-02 so I can program it via USB? If so, what settings should I use in the Debug Configuration window?
Hi Cypress team,
Recently we want to use the 89820 on Automotive project.
Almost end customer wants to use the IAR.
The previous question is below:
I modified the make file but we could not build the reference application. (currently, I'm using the hello client application)
Below is the error message
Compiling hello_client.c -DWICED_BT_TRACE_ENABLE ......
Command line error: Unable to open the command file "freestanding"
make: *** [../../../wiced_btsdk/dev-kit/baselib/20820A1/make/core/build.mk:379: C:/Users/wayne/mtw2/BLE_989820EVB01/ble/hello_client/build/CYW989820EVB-01/Debug/hello_client.o] Error 2
I've changed the makefile in hello client project.
And also changed the "IAR.mk"
CY_CROSSPATH="C:/Program Files (x86)/IAR Systems/Embedded Workbench 8.4/arm/bin"
What is the "freestanding"? Is there anything to build with the IAR compiler?
When four CYBT-213043-02 are connected to USB port(via USB hub), it's quite boring to program them.
The program configuration find first card and program it.
Thus, once a particular card is programmed, it must be disconnected from the USB so that the program configuration can program the next.
Does exist some workaround ?
I've tried mesh application powering all CYBT-213043-02 modules over USB.
Everything was Ok. Then I switched to powering from CR2032 coin on one of modules and reseted device.
After this MESH application couldn't find device.
Then I switched back to USB powering and tried to find it in MESH application again.
The device remains not found.
I started developing BLE mesh network using CYBT-213043-MESH dev kit & i am stuck on choosing the suitable gateway hardware that allow me to pub/sub the network devices to AWS IoT so i can monitor/control them anywhere through AWS ioT core.
What hardware kit i need to use? does Bluetooth Wiced Studio has a firmware/stack for it?
i appreciate if tutorials/resources are there so i can read & learn.
Hello Cypress IoT team
We evaluate CYW20819 with MoodusToolBox. We referred to below and understood APIs are not thread-safe.
We also think that "wiced_bt_spp_send_session_data" API should not be called from a thread. Because the API is difficult to exclusion control since "GKI_getpoolbuf" in the API may be called out of user control.
Are there any other such APIs that should NOT be called from a thread?
Yoshinori TakanoShow Less
in the bluetooth mesh, when I send the recall scene command by the mesh client control. there is a uart debug messages which are "company_id:ffff opcode:8242 "
in the function get_msg_handler_callback. so the device have received the recall scene messages. however the device don't perform the specify scene actions
for example the light status change. the message is not been transmitted to the application layer for execution.
I am expecting a reply!
Dear Cypress team,
Recently we want to use the F/W upgrade feature using the "OTA_FirmwareUpgrade" application.
But this sample application is not working on the customer board.
I found the reference board is working fine.
After comparing two board and review the sample application, I assumed this application uses the external memory for upgrading.
So could you let me know how to support the OTA firmware upgrade feature without external memory?
I do not do anything on the OTA firmware upgrade sample code.
Please guide the patch based on that sample code.