9 Replies Latest reply on Sep 2, 2015 2:51 AM by min

    bcm20736S platform ?

    min

      Hi,

       

      I made a custom board with BCM20736s as same as the
      schematics of the BCM920737TAG-03 evaluation board. I tried the recovery and almost everything to solve this downloading problem with the forum. I am still unable to download the app. (hello_sensor-BCM920736TAG_Q32 download UART=COM8)

       

      Download failed. This version of
      the SDK only supports download to BCM20736A1 and BCM20737A1 devices.

       

      Is there different platforms data which I need to put in ?  or should I make some changes in HW?

       

      Thx for help, guys

       

       

      Min

        • 1. Re: bcm20736S platform ?
          MichaelF_56

          How are you connecting to the custom board?  With the FTDI USB to Serial cable recommended here on the forum?  What is the state of the HCI Rx line during reset?

           

          Can you program your custom application to the TAG3 without any issues?

           

          Are you using EEPROM or SFLASH as NVRAM?  Is there anything on the I2C bus in addition to the EEPROM that is embedded in the SIP module and connected to I2C?  If so, check the various threads on the site about I2C loading.

           

          Does the HCI UART circuitry on your board look exactly like the TAG3 board, or did you remove some of the components (note that TAG3 uses the 20737 SoC, not the SIP module, but WICED Sense uses the SIP if you want to compare your board to it).

           

          Have you read the entry here that explains the boot sequence in detail: Re: BCM2073XS Boot Sequence: Can't download to board (device not found)

          • 2. Re: bcm20736S platform ?
            min


            I followed the same schematics BCM920737TAG-03 with insignificant changes.

            • 3. Re: bcm20736S platform ?
              BoonT_56

              The tag3 uses the SoC as the design but you are trying to leverage its schematics for a SIP based design....

               

              Assuming you have no HW issue, try out the steps described in the below thread:

               

              Unable to (re) program BCM20736

              1 of 1 people found this helpful
              • 4. Re: bcm20736S platform ?
                min

                Are there much difference in design for SoC and SIP except the antenna??

                So should i modify my module as wiced smart?? Instead of tag3?

                And it means that i need to use other SDK too?

                Thanks for your help

                • 5. Re: bcm20736S platform ?
                  MichaelF_56

                  No. The SDK is the same for both.

                   

                  The firmware in the part supports both the SoC and the SIP, but the HW layout of the kits are a little different because of package differences.

                   

                  The SIP module is used on the WICED Sense kit: WICED Sense Table of Contents

                  • 6. Re: bcm20736S platform ?
                    min

                    Hi,

                    I connected a FT232 board to the custom board (Turn off all SW4s)  and I was able to download hello-sensor SDK.

                    I tried to run the program with FT232 and it didn't work. So I connected the ft2232h (from custom board and turn off only (RX) in SW4). When I started the program, the program seems to work but it stops right after "BLE_high_un_adv:timer(0)".

                    I couldn't figure it out what is the problemsT_T

                    it has been a week could you help me out?

                    thanks,

                     

                    Min

                     

                    15:57:49 - hello_sensor_create()

                    15:57:49 - 1.00

                    15:57:49 - 0118

                    15:57:49 - 0018

                    15:57:49 - 021600002a

                    15:57:49 - 48656c6c6f0000000000000000000000

                    15:57:49 - 021800012a

                    15:57:49 - 0002

                    15:57:49 - 2320567c05cf6eb4c341772851827e1b

                    15:57:49 - 322a0026f6699168eec2be444db95c3f

                    15:57:49 - 2dc38a

                    15:57:49 - 48656c6c6f2030

                    15:57:49 - 0000

                    15:57:49 - 0a2d001a89074a2f3b7ea681443ff9a8

                    15:57:49 - f29b5e

                    15:57:49 - 00

                    15:57:49 - 0a18

                    15:57:49 - 024f00292a

                    15:57:49 - 42726f6164636f6d

                    15:57:49 - 025100242a

                    15:57:49 - 3132333400000000

                    15:57:49 - 025300232a

                    15:57:49 - 93b863805f9f9171

                    15:57:49 - 0f18

                    15:57:49 - 026300192a

                    15:57:49 - 64

                    15:57:49 - 02010603190002060948656c6c6f

                    15:57:49 - 020a04

                    15:57:49 -

                    15:57:49 -  permission check retCode = 00

                    15:57:49 - 64

                    15:57:49 - 6400

                    15:57:49 - 2320567c05cf6eb4c341772851827e1b

                    15:57:49 - 02010511072320567c05cf6eb4c34177

                    15:57:49 - 2851827e1b060948656c6c6f

                    15:57:49 -

                    15:57:49 - blecm evt handler:

                    15:57:49 - 0e0401082000

                    15:57:49 -

                    15:57:49 - blecm evt handler:

                    15:57:49 - 0e0401092000

                    15:57:49 -

                    15:57:49 - blecm evt handler:

                    15:57:49 - 0e0401082000

                    15:57:49 -

                    15:57:49 - blecm evt handler:

                    15:57:49 - 0e04010a200c

                    15:57:49 -

                    15:57:49 - blecm evt handler:

                    15:57:49 - 0e0401062000

                    15:57:49 -

                    15:57:49 - blecm evt handler:

                    15:57:49 - 0e04010a2000

                    15:57:49   Trace Decoding Error - Could not find line number 314

                    15:57:49   UUID  : 2800

                    15:57:49   Attribute bytes

                    15:57:49   Handle: 0062

                    15:57:49   Perm  : 0002

                    15:57:49   Len, Max Len : 0005, 0005

                    15:57:49   UUID  : 2803

                    15:57:49   Attribute bytes

                    15:57:49   Handle: 0063

                    15:57:49   Perm  : 0002

                    15:57:49   Len, Max Len : 0001, 0001

                    15:57:49   UUID  : 2A19

                    15:57:49   Attribute bytes

                    15:57:49   Gatt DB Dump complete

                    15:57:49   bd_addr[5:2] = 20 73 6A 1F

                    15:57:49   bd_addr[1:0] = 8F51 00

                    15:57:49   GPIO 0001 (11)

                    15:57:49   GPIO 0000 (104)

                    15:57:49   GPIO 0014 (1003)

                    15:57:49   GPIO 0015 (20)

                    15:57:49   GPIO 0028 (2001)

                    15:57:49   Interrupt mask[0,1]:0001 0000

                    15:57:49   Interrupt mask[2]:0000

                    15:57:49   GPIO_WP:OFF= 00

                    15:57:49   GPIOBTN1:OFF=1,INT:0

                    15:57:49   GPIO_LED:OFF=1

                    15:57:49   GPIOBAT

                    15:57:49   GPIO_BUZ:OFF=0

                    15:57:49   Battery level: 100/100

                    15:57:49   Fine Timer(0 ms, 0/sec)

                    15:57:49   Fine TImer tick 80

                    15:57:49   Normal Timer(1 s, 80 tick)

                    15:57:49   BLE_high_un_adv:timer(0)

                    • 7. Re: bcm20736S platform ?
                      BoonT_56

                      Remove the cable after downloading and ensure you are in the "Application" mode, such that your board is ready to execute the application in your nvram.

                       

                      Alternatively, check out this thread and ensure that you have fixed it, since I noticed that you are using a sip module.

                       

                      Explanation of Crystal Warmup Issue

                      • 8. Re: bcm20736S platform ?
                        min

                        Oh, actually I was able to run the program (hello-sensor) in 'application mode' but i could not get the timeout count. ( When i checked the program with the official bcm20737tag evaluation board, the timeout count shows up and it increases in every one second)

                         

                         

                        Probably, the oscillator may cause this problem. I will try the second method when i get back to the lab tmr.

                         

                         

                        Thank you~

                        • 9. Re: bcm20736S platform ?
                          min

                          I just add

                           

                          ENTRY "PMU Crystal Warm up Time"

                          {

                             "Crystal warm up time" = 5000

                          }

                           

                          to BCM 920736TAG_Q32.

                           

                          AND the hello_sensor_timeout works!  thank you ^^