• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 186 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM2431: What is maximum available internal RAM memory that APPIMAGE can use?

Marek Sujak
Prodigy 60 points
Part Number: AM2431

Dear all,

We are trying to allocate maximum available ram for main firmware.

We are using two projects from SDK

1. sbl_ospi_am243x-lp_r5fss0-0_nortos_ti-arm-clang

MSRAM_0 : ORIGIN = 0x70000100 , LENGTH = 0x70000 - 0x100
MSRAM_1 : ORIGIN = 0x70070000 , LENGTH = 0x10000

2. empty_am243x-lp_r5fss0-0_freertos_ti-arm-clang

MSRAM     : ORIGIN = 0x70080000 , LENGTH = 0x40000

The point of interest is the beginning of RAM space. SBL is permanently occupying 512kB of RAM.
Is this necessary?  It is possible to overwrite SBL space during loading APPIMAGE?
What is the recommended approach to claim as mush RAM space as possible for EMPTY project?

Thank you.

BR,
ms

  • +1
    TI__Mastermind 25705 points

    Hi ,

    Marek Sujak said:
    The point of interest is the beginning of RAM space. SBL is permanently occupying 512kB of RAM.
    Is this necessary?  It is possible to overwrite SBL space during loading APPIMAGE?

    Do you intend to re-use the SBL memory region ? If yes, then my suggestion would be to use the SBL region as non-loadable regions like BSS for heap and stack.

    System flow for this would seem something like this (very top level)

    Marek Sujak said:
    What is the recommended approach to claim as mush RAM space as possible for EMPTY project?

    Entire 2MB of MSRAM is available for the customer.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    Prodigy 60 points

    Hi, 

    Thank you for response. Yes i want to re-use as much of SBL memory region as possible. BSS might work for us. 

    I thought it is just advertised as 2MB MSRAM device, but in reality customer get less.
    Can we claim full 0x701FFFFF ? Statement below from linker file stopped us from even thinking about it.
    It would mean 128kB extra features for us.  

    /*
NOTE: Below memory is reserved for DMSC usage
 - During Boot till security handoff is complete
   0x701E0000 - 0x701FFFFF (128KB)
 - After "Security Handoff" is complete (i.e at run time)
   0x701F4000 - 0x701FFFFF (48KB)

 Security handoff is complete when this message is sent to the DMSC,
   TISCI_MSG_SEC_HANDOVER

 This should be sent once all cores are loaded and all application
 specific firewall calls are setup.
*/

    Best regards,

    ms