This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM8148 Firmware Loader Memory Utilization Question

Hello,

I'm developing on the DM8148 using the TI_EZSDK_5_05_02_00. There is 512 MB's of memory available and I've followed the directions here to make all needed changes:

http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map#Changing_Memory_Map_For_512MB_DM814x_Board

The board boots and I can load the provided FW(dm814x_hdvicp.xem3 and dm814x_hdvpss.xem3) and can successfully run the sample code (encode_a8host_debug and decode_a8host_debug).

For the file system, I have created a RAM disk that is burned into flash and that is read out at bootup. I was planning on loading the firmware files and deleting them to free up space on the RAM disk for other files. After I do a firmware load, I delete the firmware files. When I see how much space is left on the filesystem, the filesystem size has not changed. If I boot up and delete the files without loading the firmware, the filesystem size changes as expected.

######### Loading FW First before delete ##########

root@dm814x-evm:/home# firmware_loader 1 dm814x_hdvicp.xem3 start
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop>           to start/stop the firmware
===Optional arguments===
-mmap                  input memory map bin file name
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
FIRMWARE: 1 start Successful
root@dm814x-evm:/home# firmware_loader 2 dm814x_hdvpss.xem3 start
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop>           to start/stop the firmware
===Optional arguments===
-mmap                  input memory map bin file name
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
FIRMWARE: 2 start Successful
root@dm814x-evm:/home# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                76345     70062      2341  97% /
devtmpfs                  1024        48       976   5% /dev
tmpfs                       40         0        40   0% /mnt/.splash
none                      1024        48       976   5% /dev
tmpfs                    16384        32     16352   0% /var/volatile
tmpfs                    86532         0     86532   0% /dev/shm
tmpfs                    16384         0     16384   0% /media/ram
192.168.0.143:/home/tidev/nfs_share
                      19737344  15305600   3429120  82% /mnt/nfs
root@dm814x-evm:/home# rm dm814x_hdv*
root@dm814x-evm:/home# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                76345     70062      2341  97% /
devtmpfs                  1024        48       976   5% /dev
tmpfs                       40         0        40   0% /mnt/.splash
none                      1024        48       976   5% /dev
tmpfs                    16384        32     16352   0% /var/volatile
tmpfs                    86532         0     86532   0% /dev/shm
tmpfs                    16384         0     16384   0% /media/ram
192.168.0.143:/home/tidev/nfs_share
                      19737344  15305600   3429120  82% /mnt/nfs
root@dm814x-evm:/home#

######### Delete FW before loading #########

root@dm814x-evm:/home# ls
dm814x_hdvicp.xem3  dm814x_hdvpss.xem3  root
root@dm814x-evm:/home# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                76345     70062      2341  97% /
devtmpfs                  1024        48       976   5% /dev
tmpfs                       40         0        40   0% /mnt/.splash
none                      1024        48       976   5% /dev
tmpfs                    16384        24     16360   0% /var/volatile
tmpfs                    86532         0     86532   0% /dev/shm
tmpfs                    16384         0     16384   0% /media/ram
192.168.0.143:/home/tidev/nfs_share
                      19737344  15305600   3429120  82% /mnt/nfs
root@dm814x-evm:/home# rm dm814x_hdv*
root@dm814x-evm:/home# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                76345     33012     39391  46% /
devtmpfs                  1024        48       976   5% /dev
tmpfs                       40         0        40   0% /mnt/.splash
none                      1024        48       976   5% /dev
tmpfs                    16384        24     16360   0% /var/volatile
tmpfs                    86532         0     86532   0% /dev/shm
tmpfs                    16384         0     16384   0% /media/ram
192.168.0.143:/home/tidev/nfs_share
                      19737344  15305600   3429120  82% /mnt/nfs
root@dm814x-evm:/home#

 

I am wondering why this is happening. From the looks of the memory map in the link above, there is room dedicated for the firmware to reside in. Is this expected behavior? Is there anything I can do to change it?