- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am developing an Wiced SMART application with BCM20737S which use 23.8kiB RAM (*1). During running application, I found some strange behavior ( bonding is sometimes failed / sometimes cannot write to characteristic etc / wiced return GATT_ERROR(0x83) to android application as write result). They are not always occur, but if they occur once, it cannot recover after reboot.
Then I guess memory on SS area or other configuration area are broken. As supporting evidence, reproducibility becomes larger when I increase application size. When I reduce application size, this issue doesn't reproduce.
I'd like to calculate how many Total RAM footprint is available. Do you have any idea?
(*1)
--------------------------------------------------------------------------------
Patches start at 0x00204568 (RAM address)
Patches end at 0x0020537C (RAM address)
Application starts at 0x00204FD0 (RAM address)
Application ends at 0x0020A49E (RAM address)
Patch size (including reused RAM) 3604 bytes
Patch size 2664 bytes
Application size 21710 bytes
------
Total RAM footprint 24374 bytes (23.8kiB)
--------------------------------------------------------------------------------
Solved! Go to Solution.
- Labels:
-
FlashEEPROM
-
SDK 2.X
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Below is another excellent thread that discussed about this topic.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you do this with our Android app "WICED Smart Explorer"? It's available for download from playstore.
- 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
Thanks, Boont! This is what i need.