The below table is a running list of known defects in AmbiqSuite SDK release 4.0.0, along with fixes that can be applied to resolve the defect. The affected files for each fix are referenced and attached. These fixes will be integrated into a future AmbiqSuite release.
General Instructions for applying HAL updates:
- Copy the updated files into the appropriate HAL folder in AmbiqSuite.
- The provided files may need to be renamed to their original name.
- Rebuild the HAL project using the same compiler as used for application projects.
- Use the appropriate project located in one of these folders: \mcu\apollo4b\hal\mcu\gcc\ or \mcu\apollo4b\hal\mcu\iar\ or \mcu\apollo4b\hal\mcu\keil\
- This will generate a new HAL library file for each compiler, which will be linked into the main application project.
- If using a separate BSP project, rebuild the BSP before any application uses it.
- Rebuild application project(s) or example project(s) which should automatically use the new HAL library file.
|
Change # |
MCUs Impacted |
Defect and Fix |
Files |
|
1 |
Apollo4 and Apollo4 Blue |
This update has been superseded by change #3 release_sdk_4_0_0-update1 The function am_hal_pwrctrl_settings_restore() restores power workarounds (trims, etc.) to their reset settings so that one entity (e.g., a bootloader) can safely hand off to another (e.g., an application). |
https://ambiqmicro.zendesk.com/hc/article_attachments/4412188209549/am_hal_pwrctrl.c_4b https://ambiqmicro.zendesk.com/hc/article_attachments/4412188210829/am_hal_pwrctrl.h_4b
|
|
2 |
Apollo4 and Apollo4 Blue |
release_sdk_4_0_0-update2 Fix while and prime examples. Both examples adjust memory configuration to make sure that only 8 KB of TCM and no SRAM are configured. Both examples make minor changes to general power settings. The ‘while’ example is further updated to ensure 32-byte alignment of the while loop, providing much more consistent measurements across toolchains. Note that the examples are used as-is for any device or board. |
https://ambiqmicro.zendesk.com/hc/article_attachments/4412188211853/while.c https://ambiqmicro.zendesk.com/hc/article_attachments/4412179825933/prime.c
|
|
3 |
Apollo4 and Apollo4 Blue |
release_sdk_4_0_0-update3 Updates am_hal_pwrctrl.c to introduce the new function am_hal_pwrctrl_settings_restore() and fixes an earlier, limited release of the function. Also includes a couple other power updates. |
https://ambiqmicro.zendesk.com/hc/article_attachments/4412179838605/am_hal_pwrctrl.c https://ambiqmicro.zendesk.com/hc/article_attachments/4412188245773/am_hal_pwrctrl.h
|
|
4 |
Apollo4 Blue |
release_sdk_4_0_0-update4 For the Apollo4 Blue SoC, the BLE Controller firmware, v1.20.0.0 or later, generates a “no operation” code (NOP) HCI event after the BLE Controller wakes up from sleep mode. While in DTM mode, if the BLE Controller sleep is enabled, the DTM tester will also receive this NOP event code when it wakes up the BLE controller for a testing HCI command. The DTM tester may fail to recognize the NOP HCI event as a valid response to the command it sent. With the patch, the Apollo4 filters out the NOP code HCI event and prevents it from being sent to the external DTM tester. The effect of the patch can be observed when running the SDK’s uart_ble_bridge example, where the NOP HCI event is not sent to the DTM tester and therefore removes the risk of the DTM tester not recognizing or misinterpreting the NOP HCI event. |
https://ambiqmicro.zendesk.com/hc/article_attachments/4412520051725/dtm_main.c (Place in ambiq_ble\apps\dtm_module) |
|
5 |
Apollo4 Blue |
release_sdk_4_0_0-update5 About 0.3% TX signal loss has been observed during DTM testing due to the loss of BLE controller PLL lock. The updated ble_fw_image.h file solves the problem. The issue does not occur during normal BLE advertising/ connection. Cooper firmware v1.20.1.0 includes this fix. |
https://ambiqmicro.zendesk.com/hc/article_attachments/4418664024589/ble_fw_image.h |
|
6 |
Apollo4 Blue |
Corrections to the am_devices_cooper.c file and the am_hal_mcuctrl.c/.h files for the ability to update the 32MHz Crystal Trim values. Please see Apollo4 Blue SoC 32 MHz Crystal Calibration – Ambiq Support |
https://ambiqmicro.zendesk.com/hc/article_attachments/4423056699021/am_devices_cooper.c https://ambiqmicro.zendesk.com/hc/article_attachments/4423056688909/am_hal_mcuctrl.c https://ambiqmicro.zendesk.com/hc/article_attachments/4423056688653/am_hal_mcuctrl.h |
|
7 |
Apollo4 Blue |
release_sdk_4_0_0-update6 Enable device name characteristic in GAP service to fix the compatible issue with Windows BLE stack. Customer may change the device name to their expected name. |
https://ambiqmicro.zendesk.com/hc/article_attachments/4473226590989/svc_core.c |
|
8 |
Apollo4 Blue |
release_sdk_4_0_0-update7 Fixes the input data length validity check in BLE host stack APIs to prevent the memory operation error. FILE UPDATED 8Mar2022 |
Attachments:
Comments
0 comments
Article is closed for comments.