1 2 Previous Next 21 Replies Latest reply on Jun 18, 2020 1:01 AM by koTs_4636851 Go to original post
      • 15. Re: Some questions about "CYBT-343026-01 WICED EZ-Serial FW Image V1.1.14"
        GiGu_4666771

        Ok for using the GAP command, but the header of the answer I receive contains a data length equal to 0x0e,

         

        (c0)(0e)(04)(18)(00)(00)(02)(03)(07)(30)(00)(1e)(00)(00)(08)(3c)(00)(00)(21)

         

        but the length is 0x15 in the documentation.

         

        I am not able to parse the answer.

        • 16. Re: Some questions about "CYBT-343026-01 WICED EZ-Serial FW Image V1.1.14"
          GiGu_4666771

          I received the last beta version of the program and it is quite aligned with the documentation.

          I can decode the GAP answer now.

           

          Thanks!

          • 17. Re: Some questions about "CYBT-343026-01 WICED EZ-Serial FW Image V1.1.14"
            koTs_4636851

            I have tried to use Gap_set_device_name in Binary Mode utilising CYBT-343026-01 series modules and ez-serial firmware version  EZ-Serial WICED Firmware V1.1.14 but it does not work.

            Gap_set_device_name command response returns error parameter 0x020C . In Text mode works fine but in binary mode does not work.

            According [1] page 28 section 3.1.3 Changing Device Name and Appearance  , Example 3 , Gap_set_device_name  command response returns error parameter 0x020C [1] (EZ-Serial System Error Codes table 7-4 - page 160).  Also it takes one input argument (Device name ) and not two input arguments according [1] page 93.

             

            The binary command

             

            D0 16 04 0F 15 45 5A 2D 53 65 72 69 61 6C 20 25 4D 34 3A 25 4D 35 3A 25 4D 36 5C

            Or

            $D0 $16 $04 $0F $15 $45 $5A $2D $53 $65 $72 $69 $61 $6C $20 $25 $4D $34 $3A $25 $4D $35 $3A $25 $4D $36 $5C

             

            from example 3.1.3  figure 3 returns error code 0x020C  and not 0x0000 as you say in example 3 figure2

             

            D0 02 04 0F 0C 02 8C

             

            Does the Gap_set_device_name work in binary mode?  If yes , please may you clarify ?

            I am using ezapi.h and ezapi.cpp for the binary commands for the ezserial firmware.

            I have created a thread in Cypress forum :

            Set device name command has Bug in EZ-Serial WICED Firmware V1.1.1 . Help!!! 

            Set device name command has Bug in EZ-Serial WICED Firmware V1.1.1 . Help!!! 


            [1] EZ-Serial_WICED_Firmware_Platform_User_Guide_for_CYW2070x-based_Modules-v1.1.14 . pdf

            • 18. Re: Some questions about "CYBT-343026-01 WICED EZ-Serial FW Image V1.1.14"
              GiGu_4666771

              I had the same experience and I found the solution: you need to add a 1 byte parameter to command as first parameter.

              Set this parameter to zero. You need to modify exapi.h and ezapi.c too..

              1 of 1 people found this helpful
              • 19. Re: Some questions about "CYBT-343026-01 WICED EZ-Serial FW Image V1.1.14"
                koTs_4636851

                Thanks GiGu

                 

                After the bug fix in ezapi.h and ezapi.cpp  the  Gap_set_device_name  command in Binary Mode  works fine utilising CYBT-343026-01 series modules and ez-serial firmware version  EZ-Serial WICED Firmware V1.1.14 .

                Gap_set_device_name command response returns error parameter 0x0000 and the device name is written properly (ram or flash) in the BLE module.

                You need to update also the user guide document [1].  The example that you have for the set device name command is wrong ( Possible the example is from previous version).

                 

                Please also describe in the document that you cannot change the device name on the fly while advertising. BLE specification 4.1 does not say that you cannot do that. This is specification from the  ez-serial firmware version EZ-Serial WICED Firmware V1.1.14. You need to stop advertising , change the device name and then start advertising. Another way is to store the device name in flash with the command ezs_fcmd_gap_set_device_name  and subsequently reset the module.  Any function which  it is not defined in the BLE specification 4.1 standard , it should be described in the user guide [1].

                 

                 

                 

                In [1] page 28 section 3.1.3 Changing Device Name and Appearance  , Example 3 , please update the Gap_set_device_name  example in order to be according command description in [1] page 93. The command description in [1] page 93  refers  two input arguments  which it is the correct description for the version EZ-Serial WICED Firmware V1.1.14.

                Please change the Gap_set_device_name   binary command example that you describe in [1] page 28 section 3.1.2 . Please see below

                 

                D0 16 04 0F 15 45 5A 2D 53 65 72 69 61 6C 20 25 4D 34 3A 25 4D 35 3A 25 4D 36 5C

                Or

                $D0 $16 $04 $0F $15 $45 $5A $2D $53 $65 $72 $69 $61 $6C $20 $25 $4D $34 $3A $25 $4D $35 $3A $25 $4D $36 $5C

                 

                from example 3.1.3  figure 3 returns error code 0x020C and not 0x0000 as you say in example 3 figure2

                 

                D0 02 04 0F 0C 02 8C

                 

                Here is the Fix also for the EzApi

                 

                Set Device name FIX

                1. Ezapi.h modifications

                 

                //-------------- Fix ------------------------------//

                /*

                #define ezs_cmd_gap_set_device_name( name) \

                ezs_cmd_va(EZS_IDX_CMD_GAP_SET_DEVICE_NAME, 0,name)

                #define ezs_fcmd_gap_set_device_name(type,name) \

                ezs_cmd_va(EZS_IDX_CMD_GAP_SET_DEVICE_NAME, 1,name)

                */

                #define ezs_cmd_gap_set_device_name( type,name) \

                ezs_cmd_va(EZS_IDX_CMD_GAP_SET_DEVICE_NAME, 0,type,name)

                #define ezs_fcmd_gap_set_device_name(type,name) \

                ezs_cmd_va(EZS_IDX_CMD_GAP_SET_DEVICE_NAME, 1,type,name)

                //-------------------------------------------------//

                 

                 

                1. Ezapi.cpp modifications

                //----------------------  FIX ----------------------------------------------------------// 

                  //0x04,0x0F,  0x81, 0x01,T_STR,    /* 71 | S  9, SDN  (gap_set_device_name) */

                    0x04,0x0F,  0x82, 0x02,T_U8,T_STR,    /*  71 | S 9, SDN (gap_set_device_name) */ //

                Fix : Add device type ( T_U8) according Ezserial 

                User guide page 93

                 

                 

                [1] EZ-Serial_WICED_Firmware_Platform_User_Guide_for_CYW2070x-based_Modules-v1.1.14 . pdf

                 

                Many Thanks

                Kostas

                • 20. Re: Some questions about "CYBT-343026-01 WICED EZ-Serial FW Image V1.1.14"
                  GiGu_4666771

                  Hello koTs_4636851,

                  I am not a Cypress guy, so I can't access user document or other documentation to modify it.

                  I am a simple user.

                   

                  Bye

                  • 21. Re: Some questions about "CYBT-343026-01 WICED EZ-Serial FW Image V1.1.14"
                    koTs_4636851

                    Hi GiGu

                    Sorry for the misunderstanding.

                    Thanks for the help.

                    Really appreciated

                    Kostas 

                    1 2 Previous Next