UART Bootmode - application not running

Hi everyone, 

I am trying to load binary image to AWR1642 RAM over UART (UART Bootmode path from bootloader flow SWRA551 application note, shown below). 

I am running a Python script based on tools contained in Uniflash generated package. The script is able to flash the image (Vital Signs Demo binary file from Automotive Toolbox)
to the platform using WRITE FILE to SFLASH (0x24) command with META_IMAGE1 (4) file type and SFLASH (2) storage type.
After changing SOP settings to Functional mode, application is up and running properly.

Unfortunately, when I try to load image to RAM, application seems not running at all. 

According to application note: The bootloading over the UART also follows the same sequence as previously mentioned (WRITE command – 0x26). The META IMAGE received over the UART is interpreted and loaded to the appropriate memories.
Once the bootloading is complete, the ROM is eclipsed and execution control is passed to the application residing in MSS TCMA. The META IMAGE should not have the CRC32 appended (unlike the image to be flashed).

If I understand correctly, after loading image over UART using WRITE FILE to RAM (0x26) and sending CLOSE command, it should load itself into RAM and begin execution (without changing SOP configuration from Flashing to Functional). Application runs until device resets.
When I send the same binary file (without CRC32) using WRITE FILE to RAM (0x26) command with META_IMAGE1 (4) file type and SRAM (4) storage type nothing happens after sending last command CLOSE FILE.

There are a few differences between loading and flash programming mentioned:
- loading uses WRITE FILE to RAM (0x26) command;
- storage type for loading changes to SRAM (4);
- file image should not have CRC32 at the end of file for loading.
I am not sure if file has to be split to BSS patch and MSS/DSS (patch?) files as in flow chart or if it can be one image meta file. Bootloading part mentions only The META IMAGE should not have the CRC32 appended (unlike the image to be flashed) as if the only difference between images is presence of CRC32 at the EOF.

While I was looking through various documentation I found some differences between AWR1642 and IWR6843 and that there might be problem related to bootloader version.
- OPEN FILE command for AWR1642 has only FILE TYPE, while IWR6843 has STORAGE TYPE and FILE TYPE  
- CLOSE FILE command  for AWR1642 has FILE TYPE, while IWR6843 has STORAGE TYPE
Yet, loading did not work with any set of those commands.

1. Is there any step that I am missing? (as mentioned - flashing works properly)
2. Does the loaded file have to be split into two files?
3. How to ensure that program is up and running? Is there any way to debug this behavior?

Looking forward to your reply.

Thanks,
Marcelina