11.Examples that support monolithic image download do not need the steps 2-5 to load fw:
2 Wi-Fi examples: wifi_cli, wifi_wpa_supplicant, wifi_cert, wifi_webconfig
3 ncp examples: ncp_device
4 coex examples: coex_cli, coex_supplicant_cli
5
6 These examples can load cpu1/2 fw automatically, don't need to load them seperatly.
7
82. FW image names:
9 Production FW, for users:
10 rw61x_sb_wifi_a2.bin, for CPU1_wifi of redfinch a2 board
11 rw61x_sb_ble_a2.bin, for CPU2_ble of redfinch a2 board
12 rw61x_sb_ble_15d4_combo_a2.bin, for CPU2_ble_15.4_combo of redfinch a2 board
13
143. where to get FW image(Production and mfg_FW):
15 In the directory: /components/conn_fwloader/fw_bin
16
174. How to load FW(Production and mfg_FW):
18 Need to write the FW image to flash first, then the loadservice will download FW when power on.
19 For example, the CMD to write CPU1 image to flash in J-link window:
20 loadbin C:\xxx\rw61x_sb_wifi_xx.bin,0x08400000
21
22 The CMD to write CPU2_ble image to flash in J-link window:
23 loadbin C:\xxx\rw61x_sb_ble_xx.bin,0x08540000
24
25 The CMD to write CPU2_15.4 image to flash in J-link window:
26 loadbin C:\xxx\rw61x_sb_ble_15d4_combo_xx.bin,0x085e0000
27
285. Remap mechanism support
29 Whenever the remap feature is active, the flash should not be accessed in direct mode.
30 As a consequence, no structure cast should be done on flash direct addresses. Likewise memcpy operations
31 should be avoided. Instead all flash accesses must be done via staging buffers in RAM, that
32 get loaded using the mflash driver.
