Other Parts Discussed in Thread: UNIFLASH, LP-AM263
Hello,
I have connected an S25FL256LAGMFI003 Flash memory to AM2634-Q1.
And I proceeded with the download using the MCU+SDK UART Uniflash TOOL.
The result is that only the following message is displayed, and the Bootloader Binary is not being executed.
[INFO] Parsing config file ... SUCCESS. Found 3 command(s) !!!
[INFO] Executing command 1 of 3 ...
[INFO] Found flash writer ... sending C:/ti/mcu_plus_sdk_am263x_09_00_00_35/examples/drivers/boot/sbl_uart_uniflash/am263x-lp/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash.release.tiimage
I previously conducted the test using the LP-AM263 EVL Board.
The LP-AM263 has a flash memory of S25FL128SAGNFI000.
The result at that time is as follows.
[INFO] Parsing config file ... SUCCESS. Found 3 command(s) !!!
[INFO] Executing command 1 of 3 ...
[INFO] Found flash writer ... sending C:/ti/mcu_plus_sdk_am263x_09_00_00_35/examples/drivers/boot/sbl_uart_uniflash/am263x-lp/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash.release.tiimage
[INFO] Sent flashwriter C:/ti/mcu_plus_sdk_am263x_09_00_00_35/examples/drivers/boot/sbl_uart_uniflash/am263x-lp/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash.release.tiimage of size 77617 bytes in 9.68s.
[INFO] Executing command 2 of 3 ...
[INFO] Command arguments : --file=C:/ti/mcu_plus_sdk_am263x_09_00_00_35/examples/drivers/boot/sbl_qspi/am263x-lp/r5fss0-0_nortos/ti-arm-clang/sbl_qspi.release.tiimage --operation=flash --flash-offset=0x0000
Question 1: Is this difference occurring due to the flash memory size?
Question 2: If that's the case, what steps should be taken when the flash memory is changed?
Question 3: If not, what is the reason for this?
