- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
I have a problem migrating a project from BCM20732S to BCM20736S.
We worked until now with 732 module mounted on a custom board (see image, note that # means not mounted)
System worked perfectly, but I discovered that this chip is no more supported by SDK, so I decided passing to 736 module.
I verified that pinout is the same, so I simply mounted new module instead that old one.
I installed new WICED 2.1.1 SDK and, connecting to P501 I programmed the hello_sensor example in with BCM20736 configuration.
Programming is successful.
Opening a terminal window and resetting the board I see following stamps:
Initialization function has been called, then I see no other debug stamsp, even if in hello_sensor() there should be timer stamps.
Then I can't find device using a BLE client.
Summarizing:
-same HW configuration, working on BCM20732S
-using WICED 2.1.1 SDK
-compiling and programming successfully hello_sensor example
-I see only call to hello_sensor_create(), then no other action, and device is not discoverable.
I hope you can help me.
Thank you
Solved! Go to Solution.
- Labels:
-
Crystal Warm-Up
-
PCBLayout
-
SDK 2.X
-
Windows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
business explains in this thread the steps that need to be taken to implement the crystal warmup fix within your application: Re: BCM20732S module keeps crashing
Scroll down to his post on Mar 6, 2014 5:31 PM.
We managed to resolve this issue in firmware by doing the following:
1 - create a CSG file inside the application folder named app.csg with the content below:
ENTRY "PMU Crystal Warm up Time"
{
"Crystal warm up time" = 5000
}
Note that the default Crystal warm up time is 2500. By increasing this to 5000 we managed to resolve the issue.
2 - Add the following line to makefile.inc in the same folder:
GS_LIST += $(DIR)/app.cgs
This trick only works in SDK 1.1 and does NOT work in version 1.0.1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Note that the traces on SDK 2.x are encoded, so you wont be able to view them through a terminal session.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you tried increasing crystal warmup to 5mS?
- 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
Hi all,
finally I solved Issue.
It was related to interrupts firing continuously. This is because in new TAG 3 board some pins are used that I have floating in my schematic.
Anyway, where can I find the .cgs file for crystal warmup time configuration?
Thank you for help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
business explains in this thread the steps that need to be taken to implement the crystal warmup fix within your application: Re: BCM20732S module keeps crashing
Scroll down to his post on Mar 6, 2014 5:31 PM.
We managed to resolve this issue in firmware by doing the following:
1 - create a CSG file inside the application folder named app.csg with the content below:
ENTRY "PMU Crystal Warm up Time"
{
"Crystal warm up time" = 5000
}
Note that the default Crystal warm up time is 2500. By increasing this to 5000 we managed to resolve the issue.
2 - Add the following line to makefile.inc in the same folder:
GS_LIST += $(DIR)/app.cgs
This trick only works in SDK 1.1 and does NOT work in version 1.0.1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, Ill do it.
Thank you again!