1 2 Previous Next 25 Replies Latest reply on Jan 15, 2017 9:25 AM by MichaelF_56 Go to original post Branched to a new discussion.
      • 15. Re: OTA support for BCM94343W?
        MichaelF_56

        I need the developers to confirm that OTA (Not OTA2) works within SDK versions 3.6.3 through 3.7.x for the following broad market platforms:

         

        BCM943364WCD1_EVB

        BCM94343WWCD1_EVB

        BCM943362WCD4_EVB

         

        This help article was created for 3.1.2, but somewhere between that point it seems we lost support.: WICED OTA Upgrade and Factory Reset (SDK 3.1.2 through WICED Studio 4.x)

         

        Is that your understanding as well? If there is no longer support for standard OTA, then I need to figure out the plan for moving these STM32FXXX platforms over to OTA2, because the 4390X discussed here: OTA2 Update for SDK-3.7.0

         

        Is irrelevant to most users here in the forum since the 4390X has yet to move to the broad market.

        • 16. Re: OTA support for BCM94343W?
          axel.lin_1746341

          mwf_mmfae wrote:

           

          If there is no longer support for standard OTA, then I need to figure out the plan for moving these STM32FXXX platforms over to OTA2, because the 4390X discussed here: OTA2 Update for SDK-3.7.0

           

          Is irrelevant to most users here in the forum since the 4390X has yet to move to the broad market.

          I think in previous discussion the Broadcom/Cypress team give people wrong expectation that OTA2 can replace OTA.

          The fact is OTA2 requrires more storage to work (maybe 8MB flash, I'm not sure as there is no official document mentioned the minimum storage requirement.).

           

          You cannot just drop OTA support, unless you can confirm OTA2 also works for devices with on small flash. (e.g. 2MB flash)

          Otherwise, people still need OTA to work.

          1 of 1 people found this helpful
          • 17. Re: OTA support for BCM94343W?
            MichaelF_56

            Agree 100%

             

            I've solicited support from JaeyoungY_71 as she is going to test out the instructions in her aforementioned blog with the Avnet 4343W board and the BCM943362WCD4_EVB to determine how close we are to a working version of OTA for these very popular broad market evbs,

            • 18. Re: OTA support for BCM94343W?
              JaeyoungY_71

              I've tested OTA for both WICED SDK 3.7.0 and Studio 4.0 and they run successfully with no issues using the snip.scan app as the update. Instructions from the following blog post was used;

              WICED OTA Upgrade and Factory Reset (SDK 3.1.2 through WICED Studio 4.x)

               

              BCM94343W_AVN and BCM943362WCD4 were used in testing and the OTA update and the following reset/scan run as expected on both. I'll try out other apps with bigger sizes but it seems the basic function of OTA is working.

               

              Amit, Axel,

              Are you saying that the OTA does not work with the stock example apps?

               

              Thanks,

              Jaeyoung

              1 of 1 people found this helpful
              • 19. Re: OTA support for BCM94343W?
                axel.lin_1746341

                jaeyoung wrote:

                 

                I've tested OTA for both WICED SDK 3.7.0 and Studio 4.0 and they run successfully with no issues using the snip.scan app as the update. Instructions from the following blog post was used;  WICED OTA…

                I need to apply robjderr's changes in https://community.cypress.com/thread/7328?start=15&tstart=0

                Otherwise it does not work.

                 

                Other people have reported exactly the same issue.

                I have no idea why you don't need to apply robjderr's changes.

                • 20. Re: OTA support for BCM94343W?
                  JaeyoungY_71

                  Hi Axel,

                   

                  Yes, we are looking into robjderr's changes and will incorporate it into the SDK if it is confirmed. In the meantime, can you let us know which of the snip apps you used for OTA testing? The issue seems to occur intermittently so knowing which app you used would help us nail it down. Thank you.

                   

                  Best,

                  Jaeyoung

                  • 21. Re: OTA support for BCM94343W?
                    axel.lin_1746341

                    jaeyoung wrote:

                     

                    Hi Axel,

                     

                    Yes, we are looking into robjderr's changes and will incorporate it into the SDK if it is confirmed. In the meantime, can you let us know which of the snip apps you used for OTA testing? The issue seems to occur intermittently so knowing which app you used would help us nail it down. Thank you.

                     

                    Best,

                    Jaeyoung

                    I remember that when I found it didn't work for my own application, I tested it follow the standard documentation. i.e. using snip.scan for test and result is the same.

                    I don't think it's related to any snip apps.

                    • 22. Re: OTA support for BCM94343W?
                      darius1

                      Hi.

                      I want confirm that OTA not worked for me. Because have more errors.

                      One off real system errors I reported her: Incorrectly using wiced_packet_get_data return params .

                      Possible,  OTA tested on the "table", not in real system. If packet not merged then Ok it work, when packet are merged then problem.

                       

                      Other note:

                      robjderr's write:

                      When the system resets the values in spi_current_config aren't reset and the system assumes that the spi bus has already been configured and doesn't properly enable the spi bus.  So the system halts when the spi bus is accessed because it's not enabled.

                      It possible same problem I reported her: Bootloader error

                      1 of 1 people found this helpful
                      • 23. Re: OTA support for BCM94343W?
                        jmartin_1809706

                        I am using the OTA on an Avnet BCM4343W_AVN. My application is about 50-60% bigger than snip scan_fr. My app doesn't work with OTA unless I disable FR_APP and DCT_IMAGE in the make file. I have modified the app to rebuild the DCT if not correct for the new downloaded app.I have used SDK 3.7.0 and 4.0.

                         

                        I assume the board needs more flash and ram and will never work with OTA2 due to the much larger resource requirements.

                        Is there any documentation on the memory requirements for OTA?

                        • 24. Re: OTA support for BCM94343W?
                          akolamb1

                          Jayi,

                           

                          Yes OTA does work for me with on Avnet BCM94343W_AVN Platform. But it seems OTA only provides SoftAP based application update capability. I am interested in "Background" over the air update capability where module periodically checks a server for an image and when found automatically updates it. I am assuming OTA does not provide this capability and i will have to use OTA2 for this purpose?

                           

                          Anyone has Background over-the-air success with Avnet BCM94343 using OTA2?

                          1 of 1 people found this helpful
                          • 25. Re: OTA support for BCM94343W?
                            MichaelF_56

                            OTA2 is resource intensive and requires more memory than what is available on partner modules with embedded STM32 F411/F412 MCUs.  This is most likely why the only implementation supported today uses the BCM/CYW4390X, which has a CPU internal to the device with lots of available memory.  The team has gotten OTA2 to work on an STM32, but it was the highest end unit available at the time.  It required alot of custom work to get this working, which is why we have been slow to release OTA2 to the broad market on standard STM32 based partner modules.

                             

                            JaeyoungY_71

                            1 of 2 people found this helpful
                            1 2 Previous Next