readme.txt
11. FW image names:
2 Production FW, for users:
3 rw61x_sb_wifi_a2.bin, for CPU1_wifi of redfinch a2 board
4 rw61x_sb_ble_a2.bin, for CPU2_ble of redfinch a2 board
5 rw61x_sb_ble_15d4_combo_a2.bin, for CPU2_ble_15.4_combo of redfinch a2 board
6
72. where to get FW image(Production and mfg_FW):
8 In the directory: /components/conn_fwloader/fw_bin
9
103. How to load FW(Production and mfg_FW):
11 Need to write the FW image to flash first, then the loadservice will download FW when power on.
12 For example, the CMD to write CPU1 image to flash in J-link window:
13 loadbin C:\xxx\rw61x_sb_wifi_xx.bin,0x08400000
14
15 The CMD to write CPU2_ble image to flash in J-link window:
16 loadbin C:\xxx\rw61x_sb_ble_xx.bin,0x08540000
17
18 The CMD to write CPU2_15.4 image to flash in J-link window:
19 loadbin C:\xxx\rw61x_sb_ble_15d4_combo_xx.bin,0x085e0000
20
214. How to generate the C files to be compiled in the monolithic binary:
22 In a shell go to directory /components/conn_fwloader. Enter the following command:
23 'python script/fw_bin2c_conv.py -t sb fw_bin'
24 or 'python script/fw_bin2c_conv.py -t raw fw_bin':
25 This results in generating the C files under fw_bin/A1 and fw_bin/A2 subdirectories.
26
275. Remap mechanism support
28 Whenever the remap feature is active, the flash should not be accessed in direct mode.
29 As a consequence, no structure cast should be done on flash direct addresses. Likewise memcpy operations
30 should be avoided. Instead all flash accesses must be done via staging buffers in RAM, that
31 get loaded using the mflash driver.
readme_rc.txt
11. FW image names:
2 Raw FW, for users:
3 rw610w_raw_cpu1_v0.bin, for CPU1_wifi of redfinch A0 board
4 rw610n_raw_cpu2_ble_v0.bin, for CPU2_ble of redfinch A0 board
5 rw610n_combo_raw_cpu2_ble_15_4_combo_v0.bin, for CPU2_ble_15.4_combo of redfinch A0 board
6
7 rw610w_raw_cpu1_v1.bin, for CPU1_wifi of redfinch A1 board
8 rw610n_raw_cpu2_ble_v1.bin, for CPU2_ble of redfinch A1 board
9 rw610n_combo_raw_cpu2_ble_15_4_combo_v1.bin, for CPU2_ble_15.4_combo of redfinch A1 board
10
11 rw610w_raw_cpu1_v2.bin, for CPU1_wifi of redfinch A2 board
12 rw610n_raw_cpu2_ble_v2.bin, for CPU2_ble of redfinch A2 board
13 rw610n_combo_raw_cpu2_ble_15_4_combo_v2.bin, for CPU2_ble_15.4_combo of redfinch A2 board
14 Production mfg_FW, for users:
15 rw610w_mfg_fw_cpu1.bin for mfg_fw_cpu1_wifi
16 rw610n_mfg_fw_cpu2.bin for mfg_fw_cpu2_ble
17 nbu_15_4_mfg.bin, for mfg_fw_cpu2_15.4
18
192. where to get FW image:
20 In the directory: /components/conn_fwloader/fw_bin
21
223. How to load FW:
23 Need to write the FW image to flash first, then the loadservice will download FW when power on.
24 For example, the CMD to write CPU1 image to flash in J-link window:
25 loadbin C:\xxx\rw610w_raw_cpu1_xx.bin,0x08400000
26
27 The CMD to write CPU2_ble image to flash in J-link window:
28 loadbin C:\xxx\rw610n_raw_cpu2_ble_xx.bin,0x08540000
29
30 The CMD to write CPU2_15.4 image to flash in J-link window:
31 loadbin C:\xxx\rw610n_combo_raw_cpu2_ble_15_4_combo_xx.bin,0x085e0000
32
33
