6 Replies Latest reply on Jul 10, 2018 2:32 AM by KaRe_1495521

    ble mesh, provisioning

    LeCa_2156671

      I have a problem when provisioning using Meshlighting.apk.

      I connect to the eval board of 20706 and programmed mesh_onoff_server to the board.

      But 20706 seems not advertising.I can't scan it with meshlighting.apk or Bluetooth ellisys.

       

      My log is as below,seems mesh start correctly:

       

      Mesh Start

      mesh_management_cback: 15

      management_cback: LOCAL_IDENTITY_KEYS_REQUEST_EVT: result:0 keys:

      mesh_management_cback: 0

      ***** Free mem before app_init:32012

      ## mesh_application_init ##

      wiced_bt_gatt_register: 0

      ds1:0x00504000, len:0x0007e000

      ds2:0x00582000, len:0x0007e000

      platform btp: Config_DS_Location 0x00003000, Config_VS_Location:0x00001000

      WARNING: Upgrade will fail - active DS is not one of the expected locations

      WARNING: Are ConfigDSLocation and DLConfigVSLocation in the .btp set up as in nv_loc_len[]?

      mesh_application_init: wiced_bt_mesh_core_ota_fw_upgrade_init failed

      mesh_application_init: unprovisioned GATT DB status:0

      wiced_bt_mesh_model_onoff_server_init

      mesh deftt init

      def trans time:0

      Failed to write nv

      wiced_bt_mesh_model_scene_server_init

      scene_server_delete_all bytes:0

      wiced_bt_mesh_model_scheduler_server_init

      No sched events

      time srvr init

      wiced_bt_mesh_model_onoff_server_init

      mesh deftt init

      def trans time:0

      Failed to write nv

      wiced_bt_mesh_model_scene_server_init

      scene_server_delete_all bytes:0

      wiced_bt_mesh_model_scheduler_server_init

      No sched events

      wiced_bt_mesh_model_onoff_server_init

      mesh deftt init

      def trans time:0

      Failed to write nv

      wiced_bt_mesh_model_scene_server_init

      scene_server_delete_all bytes:0

      wiced_bt_mesh_model_scheduler_server_init

      No sched events

      ***** Free mem after app_init:30052

        • 1. Re: ble mesh, provisioning

          Are you using an Eval board? If so which one?

           

          Also previous versions of WICED had similar issues, but have been resolved in WICED Studio 6.1 release version. If you are already using WICED studi 6.1, can you please make sure there is no workspace mismatch?

           

          Please try re-installing the SDK if you find any mismatch.

           

          Regards,

          -Madhu

          1 of 1 people found this helpful
          • 2. Re: ble mesh, provisioning
            LeCa_2156671

            Hi,

            I'm using CYW92070xV3_EVAL and WICED studio 6.1.

            I see the explanation of "wiced_result_t wiced_bt_mesh_core_init(wiced_bt_mesh_core_init_t *)

            ---WICED_BT_SUCCESS means device provisioned. Otherwise it is not provisioned."

            In my case, is it means the device init fail and device is abnormal(not in provisioned or not provisioned state)?

            In my log, seems nvram is abnormal.

            "Failed to write nv"

            • 3. Re: ble mesh, provisioning
              LeCa_2156671

              1.I find the code is not 20706 in "mesh_ota_fw_upgrade.c":

              #define EF_BASE_ADDR                (0x500000u)

              #define FLASH_SECTOR_SIZE           (4 * 1024)

              #define FW_UPGRADE_FLASH_SIZE       0x100000    //  20739 has 1MB on chip flash

               

              2.

              /*

              * Application provided function to read/write information from/into NVRAM

              */

              static uint32_t mesh_nvram_access(wiced_bool_t write, int inx, uint8_t* node_info, uint16_t len, wiced_result_t *p_result)

              {

              /*test code*/

                  WICED_BT_TRACE("mesh_nvram_access: write:%d inx:%d len:%d*****************************************\n", write, inx,len);

                  if(inx >140)

                      inx -= 130;

               

               

                  if (!write)

                      return wiced_hal_read_nvram(NVRAM_ID_MESH_START + inx, len, node_info, p_result);

                  // 0 len means delete

                  if (len != 0)

                      return wiced_hal_write_nvram(NVRAM_ID_MESH_START + inx, len, node_info, p_result);

                  wiced_hal_delete_nvram(NVRAM_ID_MESH_START + inx, p_result);

                  return len;

              }

              when this function is called,the parameter "inx" will use 141,142,143,144,<NVRAM_ID_MESH_START + inx> will wrap WICED_NVRAM_VSID_END(0x7B)

              so the call will fail.

               

              3.After i add the test code above, I add light now.

              But when I control it,I can see log in the "mesh_application.",the the application layer can not receive the message.

              • 4. Re: ble mesh, provisioning

                Hi,

                 

                In the make target, can you please set LEGACY_BOARD=1 and then try running the example?

                 

                Regards,

                -Madhu

                • 5. Re: ble mesh, provisioning

                  Hi! 

                  I've changed "USBVideoClassBulk" example from MJPEG to YUV(from subtype : VS_FORMAT_MJPEG to Subtype : uncompressed format)

                  The descriptors are originally configured to stream MJPEG images stored in "glUVCVidFrames[]" structure which in cyfxuvcvidframes.c.

                  I have modified ‘cyfxuvcdscr.c"。The device is successfully recognized by host but cannot begin streaming any data. In "MJPEG mode" it works correctly.

                  My video frames is not visible in AMCap. I have EZ-USB® FX3™ Development Kit (CYUSB3KIT-003) connected to USB 2.0.

                  I have no cammer.Could you help me? Thank you!

                  • 6. Re: ble mesh, provisioning
                    KaRe_1495521

                    I'm interested in your log, was it from puart output?

                    I'm using a serial terminal utility to capture the log, but it's always unreadable code, my baud rate is 115200, what was yours?

                    Thanks.