1 2 Previous Next 29 Replies Latest reply on Jan 17, 2015 1:03 AM by userc_7511

    Change BCW920737TAG from EEPROM to SFLASH failed

      Hi All,

       

      We changed the resistors as 920737TAG03-HWUM100-R.pdf described.

      setting.png

      But when we tried to download in the IDE, the following error comes out:

       

      err.png

       

      The board worked well with EEPROM.

       

      What should we check? Thanks in advance!

       

      Best Regards,

       

      Philip

        • 1. Re: Change BCW920737TAG from EEPROM to SFLASH failed
          JaWa_2142591

          Have you put "PLATFORM_NV=SFLASH" when make target?

          • 2. Re: Change BCW920737TAG from EEPROM to SFLASH failed

            Thanks a lot. We will try...

             

            I didn't notice the "PLATFORM_NV=SFLASH" in the documents. Could you please let me know which doc it is inside?

            • 3. Re: Change BCW920737TAG from EEPROM to SFLASH failed
              ZhaohuaS_76

              Hi janusw,

              I had add the "PLATFORM_NV=SFLASH" in make target, but still download failed.

               

              Failed log:

               

              echo Downloading application... && Tools\ChipLoad\Win32\ChipLoad.exe -BLUETOOLMODE -PORT COM3 -BAUDRATE 115200 -MINIDRIVER Platforms/BCM920737TAG_Q32/uart_DISABLE_EEPROM_WP_PIN1.hex -BTP Platforms/BCM920737TAG_Q32/20737_SFLASH.btp -CONFIG build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release.hex -CHECKCRC -NOVERIFY -DLMINIDRIVERCHUNKSIZE 251 > build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/download.log 2>&1 && echo Download complete && "Tools/common/Win32/echo.exe" && echo Application running || echo '****Download failed - Press the reset button on the device and retry ****'

              • 4. Re: Change BCW920737TAG from EEPROM to SFLASH failed

                Hi Janusw and all,

                 

                 

                I added "PLATFORM_NV=SFLASH" and the result still the same.

                 

                 

                the console window of the IDE said

                 

                 

                echo Downloading application... && Tools\ChipLoad\Win32\ChipLoad.exe -BLUETOOLMODE -PORT COM32 -BAUDRATE 115200 -MINIDRIVER Platforms/BCM920737TAG_Q32/uart_DISABLE_EEPROM_WP_PIN1.hex -BTP Platforms/BCM920737TAG_Q32/20737_SFLASH.btp -CONFIG build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release.hex -CHECKCRC -NOVERIFY -DLMINIDRIVERCHUNKSIZE 251 > build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/download.log 2>&1 && echo Download complete && "Tools/common/Win32/echo.exe" && echo Application running || echo '****Download failed - Press the reset button on the device and retry ****'

                Downloading application...

                '****Download failed - Press the reset button on the device and retry ****'

                 

                 

                Please anybody can help me. Thanks in advance

                • 5. Re: Change BCW920737TAG from EEPROM to SFLASH failed

                  I'm not sure I could help.

                  But what build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/download.log says?

                  • 6. Re: Change BCW920737TAG from EEPROM to SFLASH failed

                    It (build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/download.log) says

                     

                    " BluetoolDownloadMinidriver failed!"

                     

                    that's all.

                    what should I check further?

                    • 7. Re: Change BCW920737TAG from EEPROM to SFLASH failed
                      ArvindS_76

                      Can you try downloading after turning off dip switches 5,6,7, and 8 on SW4 and then resetting the device? It is likely that since this is the first time the chip tries to boot from SF (which is generally empty coming out of the factory), it will come up in recovery mode. So edit your application's make target and add UART=COMXX (where XX is the com port to which the device is connected to) and instead of 'download' use 'recover'. See the quick start guide for info on recovery mode.

                      • 8. Re: Change BCW920737TAG from EEPROM to SFLASH failed

                        Hi Arvinds,

                         

                        Thanks for your reply.

                         

                        I turned off 5,6,7,8 of SW4 and changed the command line to

                         

                        hello_sensor-BCM920737TAG_Q32 recover UART=COM32 PLATFORM_NV=SFLASH VERBOSE=1

                         

                        where COM32 is the first com port listed in windows device manger.

                         

                        then reset target with SW5 pressed.

                         

                        the recovery failed as the console window said:

                         

                         

                        "

                        echo Recovering platform ...
                        Opening ../../build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/A_20737A1-hello_sensor-rom-ram-spar.elf to read
                        Seeking to 3280 into ../../build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/A_20737A1-hello_sensor-rom-ram-spar.elf
                        Recovering platform ...

                        Tools\ChipLoad\Win32\ChipLoad.exe -BLUETOOLMODE -PORT COM32 -BAUDRATE 115200 -NODLMINIDRIVER -MINIDRIVER Platforms/BCM920737TAG_Q32/uart_DISABLE_EEPROM_WP_PIN1.hex -BTP Platforms/BCM920737TAG_Q32/20737_SFLASH.btp -CONFIG build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release.hex -CHECKCRC -NOVERIFY -DLMINIDRIVERCHUNKSIZE 251 > build/hello_sensor-BCM920737TAG_Q32-rom-ram-Wiced-release/download.log 2>&1 && echo Recovery complete && "Tools/common/Win32/echo.exe" && echo Application running || echo **** Recovery failed - retry ****

                        "

                         

                         

                         

                        However, there were more information in download.log file this time. It seemed that the flash write CRC check failed.

                         

                        "

                        Download minidriver successfully had written 251 bytes to address 0x00209F00
                        Download minidriver successfully had written 251 bytes to address 0x00209FFB
                        Download minidriver successfully had written 251 bytes to address 0x0020A0F6
                        Download minidriver successfully had written 251 bytes to address 0x0020A1F1
                        Download minidriver successfully had written 251 bytes to address 0x0020A2EC
                        Download minidriver successfully had written 251 bytes to address 0x0020A3E7
                        Download minidriver successfully had written 251 bytes to address 0x0020A4E2
                        Download minidriver successfully had written 251 bytes to address 0x0020A5DD
                        Download minidriver successfully had written 251 bytes to address 0x0020A6D8
                        Download minidriver successfully had written 251 bytes to address 0x0020A7D3
                        Download minidriver successfully had written 251 bytes to address 0x0020A8CE
                        Download minidriver successfully had written 251 bytes to address 0x0020A9C9
                        Download minidriver successfully had written 251 bytes to address 0x0020AAC4
                        Download minidriver successfully had written 251 bytes to address 0x0020ABBF
                        Download minidriver successfully had written 251 bytes to address 0x0020ACBA
                        Download minidriver successfully had written 251 bytes to address 0x0020ADB5
                        Download minidriver successfully had written 251 bytes to address 0x0020AEB0
                        Download minidriver successfully had written 251 bytes to address 0x0020AFAB
                        Download minidriver successfully had written 251 bytes to address 0x0020B0A6
                        Download minidriver successfully had written 251 bytes to address 0x0020B1A1
                        Download minidriver successfully had written 251 bytes to address 0x0020B29C
                        Download minidriver successfully had written 251 bytes to address 0x0020B397
                        Download minidriver successfully had written 251 bytes to address 0x0020B492
                        Download minidriver successfully had written 251 bytes to address 0x0020B58D
                        Download minidriver successfully had written 251 bytes to address 0x0020B688
                        Download minidriver successfully had written 251 bytes to address 0x0020B783
                        Download minidriver successfully had written 251 bytes to address 0x0020B87E
                        Download minidriver successfully had written 251 bytes to address 0x0020B979
                        Download minidriver successfully had written 251 bytes to address 0x0020BA74
                        Download minidriver successfully had written 251 bytes to address 0x0020BB6F
                        Download minidriver successfully had written 251 bytes to address 0x0020BC6A
                        Download minidriver successfully had written 251 bytes to address 0x0020BD65
                        Download minidriver successfully had written 251 bytes to address 0x0020BE60
                        Download minidriver successfully had written 251 bytes to address 0x0020BF5B
                        Download minidriver successfully had written 251 bytes to address 0x0020C056
                        Download minidriver successfully had written 251 bytes to address 0x0020C151
                        Download minidriver successfully had written 251 bytes to address 0x0020C24C
                        Download minidriver successfully had written 251 bytes to address 0x0020C347
                        Download minidriver successfully had written 251 bytes to address 0x0020C442
                        Download minidriver successfully had written 251 bytes to address 0x0020C53D
                        Download minidriver successfully had written 251 bytes to address 0x0020C638
                        Download minidriver successfully had written 251 bytes to address 0x0020C733
                        Download minidriver successfully had written 251 bytes to address 0x0020C82E
                        Download minidriver successfully had written 251 bytes to address 0x0020C929
                        Download minidriver successfully had written 104 bytes to address 0x0020CA24
                        Download minidriver successfully had written 8 bytes to address 0x0020D254
                        Launch minidriver at 0x00209F00 succeeded
                        Download config successfully had written 40 bytes to address 0xFF000000:  01 08 00 F0 00 00 62 08 C0 5D 89 FD 04 00 FF FF FF FF 40 06 00 00 B6 1E 7A 73 20 02 0A 00 00 40 00 00 00 20 00 00 00 10
                        Downloaded 0 code bytes ( 0.0%) and 40 data bytes ( 0.7%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Terminated with error


                        A total of 1 contiguous memory areas were filled:
                        [FF000000..FF000027] DATA (40 bytes)
                        CRC mismatch while checking 40 bytes starting at address 0xFF000000; host computed 3B99D3C8, firmware computed 8CD04C73

                        "

                        • 9. Re: Change BCW920737TAG from EEPROM to SFLASH failed
                          MichaelF_56

                          Are you using the same Macronix Serial Flash that is supported by the ROM and ships on the latest TAG board?Macronix.png

                          • 10. Re: Change BCW920737TAG from EEPROM to SFLASH failed
                            ZhaohuaS_76

                            Hi mwf_mmfae,

                            Yes, I use the 20737 EVK, Macronix Serial Flash is on it.

                            I had turned off the dip switch 5-8 on SW4, and try the download and recover mode, still download failed.

                            • 11. Re: Change BCW920737TAG from EEPROM to SFLASH failed
                              ArvindS_76

                              And do you have the resistors as in Table 2/Figure 2 (page 9) populated as in 920737TAG03-HWUM100-R.pdf?

                              • 12. Re: Change BCW920737TAG from EEPROM to SFLASH failed
                                ZhaohuaS_76

                                Hi arvinds,

                                Yes, I do it, change the RD2/RD3/RD4, and install R100 and R101.

                                • 13. Re: Change BCW920737TAG from EEPROM to SFLASH failed

                                  Hi mwf_mmfae, arvinds and all,

                                   

                                  Thanks for your replies..

                                   

                                  I did not change the flash ic on the EVK. And I did all the resistors settings according to the Broadcom document 920737TAG03-HWUM100-R.pdf.

                                   

                                  Is it a bug? Does the same BCW920737TAG work well with the on-board sflash at your site?

                                   

                                  Regards,

                                   

                                  Philip

                                  • 14. Re: Change BCW920737TAG from EEPROM to SFLASH failed

                                    By the way, have you changed hello_sensor_puart_cfg?

                                    > // Following structure defines UART configuration.  Please note that

                                    > // if Serial Flash is being used GPIO_PIN_UART_TX should be 24 and

                                    > // GPIO_PIN_UART_RX should be 25.  Because standard 31 and 32 are used

                                    > // by Serial Flash

                                    > const BLE_PROFILE_PUART_CFG hello_sensor_puart_cfg =

                                    > {

                                    >     /*.baudrate   =*/ 115200,

                                    >     /*.txpin      =*/ GPIO_PIN_UART_TX,

                                    >     /*.rxpin      =*/ GPIO_PIN_UART_RX,

                                    > };

                                    1 2 Previous Next