- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I made my own board with a BCM20732S module version B1 and when I try to use it for the first time I can't either program it or recover it with the reference images. It seems that it can't erase the chip. I use the SDK 1.1. I don't know if it can impact the programation but the I2C line is loaded by 2 devices : LIS3DH and AT30TS75A. I checked the RX and TX signals with an oscilloscope and they look good.
This is my download.log when trying to recover:
Download minidriver successfully had written 64 bytes to address 0x0020AF00
Download minidriver successfully had written 64 bytes to address 0x0020AF40
Download minidriver successfully had written 64 bytes to address 0x0020AF80
Download minidriver successfully had written 64 bytes to address 0x0020AFC0
Download minidriver successfully had written 64 bytes to address 0x0020B000
Download minidriver successfully had written 64 bytes to address 0x0020B040
Download minidriver successfully had written 64 bytes to address 0x0020B080
Download minidriver successfully had written 64 bytes to address 0x0020B0C0
Download minidriver successfully had written 64 bytes to address 0x0020B100
Download minidriver successfully had written 64 bytes to address 0x0020B140
Download minidriver successfully had written 64 bytes to address 0x0020B180
Download minidriver successfully had written 64 bytes to address 0x0020B1C0
Download minidriver successfully had written 64 bytes to address 0x0020B200
Download minidriver successfully had written 64 bytes to address 0x0020B240
Download minidriver successfully had written 64 bytes to address 0x0020B280
Download minidriver successfully had written 64 bytes to address 0x0020B2C0
Download minidriver successfully had written 64 bytes to address 0x0020B300
Download minidriver successfully had written 64 bytes to address 0x0020B340
Download minidriver successfully had written 64 bytes to address 0x0020B380
Download minidriver successfully had written 64 bytes to address 0x0020B3C0
Download minidriver successfully had written 64 bytes to address 0x0020B400
Download minidriver successfully had written 64 bytes to address 0x0020B440
Download minidriver successfully had written 64 bytes to address 0x0020B480
Download minidriver successfully had written 64 bytes to address 0x0020B4C0
Download minidriver successfully had written 64 bytes to address 0x0020B500
Download minidriver successfully had written 64 bytes to address 0x0020B540
Download minidriver successfully had written 64 bytes to address 0x0020B580
Download minidriver successfully had written 64 bytes to address 0x0020B5C0
Download minidriver successfully had written 64 bytes to address 0x0020B600
Download minidriver successfully had written 64 bytes to address 0x0020B640
Download minidriver successfully had written 64 bytes to address 0x0020B680
Download minidriver successfully had written 64 bytes to address 0x0020B6C0
Download minidriver successfully had written 64 bytes to address 0x0020B700
Download minidriver successfully had written 64 bytes to address 0x0020B740
Download minidriver successfully had written 64 bytes to address 0x0020B780
Download minidriver successfully had written 64 bytes to address 0x0020B7C0
Download minidriver successfully had written 64 bytes to address 0x0020B800
Download minidriver successfully had written 64 bytes to address 0x0020B840
Download minidriver successfully had written 64 bytes to address 0x0020B880
Download minidriver successfully had written 64 bytes to address 0x0020B8C0
Download minidriver successfully had written 64 bytes to address 0x0020B900
Download minidriver successfully had written 64 bytes to address 0x0020B940
Download minidriver successfully had written 64 bytes to address 0x0020B980
Download minidriver successfully had written 64 bytes to address 0x0020B9C0
Download minidriver successfully had written 64 bytes to address 0x0020BA00
Download minidriver successfully had written 64 bytes to address 0x0020BA40
Download minidriver successfully had written 64 bytes to address 0x0020BA80
Download minidriver successfully had written 64 bytes to address 0x0020BAC0
Download minidriver successfully had written 64 bytes to address 0x0020BB00
Download minidriver successfully had written 64 bytes to address 0x0020BB40
Download minidriver successfully had written 64 bytes to address 0x0020BB80
Download minidriver successfully had written 64 bytes to address 0x0020BBC0
Download minidriver successfully had written 64 bytes to address 0x0020BC00
Download minidriver successfully had written 64 bytes to address 0x0020BC40
Download minidriver successfully had written 64 bytes to address 0x0020BC80
Download minidriver successfully had written 64 bytes to address 0x0020BCC0
Download minidriver successfully had written 64 bytes to address 0x0020BD00
Download minidriver successfully had written 64 bytes to address 0x0020BD40
Download minidriver successfully had written 64 bytes to address 0x0020BD80
Download minidriver successfully had written 64 bytes to address 0x0020BDC0
Download minidriver successfully had written 64 bytes to address 0x0020BE00
Download minidriver successfully had written 64 bytes to address 0x0020BE40
Download minidriver successfully had written 64 bytes to address 0x0020BE80
Download minidriver successfully had written 64 bytes to address 0x0020BEC0
Download minidriver successfully had written 64 bytes to address 0x0020BF00
Download minidriver successfully had written 64 bytes to address 0x0020BF40
Download minidriver successfully had written 64 bytes to address 0x0020BF80
Download minidriver successfully had written 64 bytes to address 0x0020BFC0
Download minidriver successfully had written 64 bytes to address 0x0020C000
Download minidriver successfully had written 64 bytes to address 0x0020C040
Download minidriver successfully had written 64 bytes to address 0x0020C080
Download minidriver successfully had written 64 bytes to address 0x0020C0C0
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- loading minidriver
Download minidriver successfully had written 64 bytes to address 0x0020C100
Download minidriver successfully had written 64 bytes to address 0x0020C140
Download minidriver successfully had written 64 bytes to address 0x0020C180
Download minidriver successfully had written 64 bytes to address 0x0020C1C0
Download minidriver successfully had written 64 bytes to address 0x0020C200
Download minidriver successfully had written 64 bytes to address 0x0020C240
Download minidriver successfully had written 64 bytes to address 0x0020C280
Download minidriver successfully had written 64 bytes to address 0x0020C2C0
Download minidriver successfully had written 64 bytes to address 0x0020C300
Download minidriver successfully had written 64 bytes to address 0x0020C340
Download minidriver successfully had written 64 bytes to address 0x0020C380
Download minidriver successfully had written 64 bytes to address 0x0020C3C0
Download minidriver successfully had written 64 bytes to address 0x0020C400
Download minidriver successfully had written 64 bytes to address 0x0020C440
Download minidriver successfully had written 64 bytes to address 0x0020C480
Download minidriver successfully had written 64 bytes to address 0x0020C4C0
Download minidriver successfully had written 64 bytes to address 0x0020C500
Download minidriver successfully had written 64 bytes to address 0x0020C540
Download minidriver successfully had written 64 bytes to address 0x0020C580
Download minidriver successfully had written 64 bytes to address 0x0020C5C0
Download minidriver successfully had written 64 bytes to address 0x0020C600
Download minidriver successfully had written 64 bytes to address 0x0020C640
Download minidriver successfully had written 64 bytes to address 0x0020C680
Download minidriver successfully had written 64 bytes to address 0x0020C6C0
Download minidriver successfully had written 64 bytes to address 0x0020C700
Download minidriver successfully had written 64 bytes to address 0x0020C740
Download minidriver successfully had written 64 bytes to address 0x0020C780
Download minidriver successfully had written 64 bytes to address 0x0020C7C0
Download minidriver successfully had written 64 bytes to address 0x0020C800
Download minidriver successfully had written 64 bytes to address 0x0020C840
Download minidriver successfully had written 64 bytes to address 0x0020C880
Download minidriver successfully had written 64 bytes to address 0x0020C8C0
Download minidriver successfully had written 64 bytes to address 0x0020C900
Download minidriver successfully had written 64 bytes to address 0x0020C940
Download minidriver successfully had written 64 bytes to address 0x0020C980
Download minidriver successfully had written 64 bytes to address 0x0020C9C0
Download minidriver successfully had written 64 bytes to address 0x0020CA00
Download minidriver successfully had written 64 bytes to address 0x0020CA40
Download minidriver successfully had written 64 bytes to address 0x0020CA80
Download minidriver successfully had written 64 bytes to address 0x0020CAC0
Download minidriver successfully had written 64 bytes to address 0x0020CB00
Download minidriver successfully had written 64 bytes to address 0x0020CB40
Download minidriver successfully had written 64 bytes to address 0x0020CB80
Download minidriver successfully had written 64 bytes to address 0x0020CBC0
Download minidriver successfully had written 64 bytes to address 0x0020CC00
Download minidriver successfully had written 64 bytes to address 0x0020CC40
Download minidriver successfully had written 64 bytes to address 0x0020CC80
Download minidriver successfully had written 64 bytes to address 0x0020CCC0
Download minidriver successfully had written 64 bytes to address 0x0020CD00
Download minidriver successfully had written 64 bytes to address 0x0020CD40
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- loading minidriver
Download minidriver successfully had written 64 bytes to address 0x0020CD80
Download minidriver successfully had written 64 bytes to address 0x0020CDC0
Download minidriver successfully had written 64 bytes to address 0x0020CE00
Download minidriver successfully had written 64 bytes to address 0x0020CE40
Download minidriver successfully had written 64 bytes to address 0x0020CE80
Download minidriver successfully had written 64 bytes to address 0x0020CEC0
Download minidriver successfully had written 64 bytes to address 0x0020CF00
Download minidriver successfully had written 64 bytes to address 0x0020CF40
Download minidriver successfully had written 64 bytes to address 0x0020CF80
Download minidriver successfully had written 64 bytes to address 0x0020CFC0
Download minidriver successfully had written 64 bytes to address 0x0020D000
Download minidriver successfully had written 64 bytes to address 0x0020D040
Download minidriver successfully had written 64 bytes to address 0x0020D080
Download minidriver successfully had written 64 bytes to address 0x0020D0C0
Download minidriver successfully had written 64 bytes to address 0x0020D100
Download minidriver successfully had written 64 bytes to address 0x0020D140
Download minidriver successfully had written 64 bytes to address 0x0020D180
Download minidriver successfully had written 64 bytes to address 0x0020D1C0
Download minidriver successfully had written 64 bytes to address 0x0020D200
Download minidriver successfully had written 64 bytes to address 0x0020D240
Download minidriver successfully had written 64 bytes to address 0x0020D280
Download minidriver successfully had written 64 bytes to address 0x0020D2C0
Download minidriver successfully had written 64 bytes to address 0x0020D300
Download minidriver successfully had written 64 bytes to address 0x0020D340
Download minidriver successfully had written 64 bytes to address 0x0020D380
Download minidriver successfully had written 64 bytes to address 0x0020D3C0
Download minidriver successfully had written 64 bytes to address 0x0020D400
Download minidriver successfully had written 64 bytes to address 0x0020D440
Download minidriver successfully had written 64 bytes to address 0x0020D480
Download minidriver successfully had written 64 bytes to address 0x0020D4C0
Download minidriver successfully had written 64 bytes to address 0x0020D500
Download minidriver successfully had written 64 bytes to address 0x0020D540
Download minidriver successfully had written 64 bytes to address 0x0020D580
Download minidriver successfully had written 60 bytes to address 0x0020D5C0
Download minidriver successfully had written 8 bytes to address 0x0020D904
Launch minidriver at 0x0020AF00 succeeded
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Terminated with error
Chip erase timeout (nLastProgressReportTime)
Do you have any idea or suggestion to check/test?
Kind regards
Daniel
Solved! Go to Solution.
- Labels:
-
FlashEEPROM
-
SDK 1.X
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What is the state of the HCI RXd line? Note that the state of this pin is the most common problem users see when attempting to have the 2073XS device come up in programming (as opposed to Application) mode.
Are you using a header and FTDI cable to program your custom 20732S based board as described here: Re: Information: Programming your BCM20732S-based board from an onboard UART header
What are the slave addresses being used on the I2C bus? This thread and several others does a good job of walking through a procedure to t-shoot potential slave address conflicts: Re: i2c clock frequency
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What do you mean by state? If it's the electrical level, it is high (approximatly 2V) when no communication is performed and of course a square signal when communicate. I can see a first communication starting from the host to the module but also some data sent from the Module to the Host (RX and TX look ok).
Yes I'm using the FTDI communication signals from the evaluation board but as I said The communication looks good. I Think that if something was bad the communication would stop before in the process, when the host try to identify the module. But here it seems that the device is recognise.
Regarding the adress, the LIS3DH is 001100xb and the AT30TS75A was 1001000xb and I changed its address to 1001001xb in order to try, but no change. is the internal flash connected to the same I2C bus? What is the internal EEPROM address?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
See here: http://community.broadcom.com/message/2696#2696
Power your board up while making sure that RXD is held high during power up (this will cause the HCI UART to come up in programming mode).
Note that by default this pin is pulled low through an internal 10k ohm resistor.
The EEPROM driver API provides low level access to write to any EEPROM location (only the lower 64KBytes will be used/accessed by the firmware), so the application can still use the upper 64KBytes by specifying a different I2C slave address than the one used for the lower 64KBytes, which is usually 0xA0/0xA1 (some parts also use 0xA2/0xA3 while others use 0xA8/0xA9).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
dear mmfae,
- I checked and the RX line (from module point of view) is high when I reset the device.
- now I do not want to drive the EEPROM from the firmware I just want to recover the system or to program it with a sample application provided in the SDK. This is not working ! Regarding the EEPROM address , does it mean that in the modules you are producing (the BCM20732S) you don't know what the address can be ? There is no constancy ?
By the way you didn't told me if inside the module the EEPROM is connected to the same bus as the external I2C bus?
Anyway I removed the AT30TS75A from the I2C bus which was the one with the closest address and the result is still the same !!!!!
Any idea?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem is solved, there was an issue in the external I2C bus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is only 1 I2C bus. The addresses used for the EEPROM were given in a previous post (Normally 0xA0/0xA1)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You gave several addresses and mentioned "normally" in the last message! So I'm not sure what I can find in a module?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
daniel - you claim the <<< electrical level, it is high (approximatly 2V) when no communication is performed
This seems very low for a Logic 1 state on the UART_RX signal. What voltage level are you driving the board at?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The complete board is driven @ 2V.