SBL should avoid hardcoding 0xBAD00000 in many places

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • PDK
    • PDK-11084
    • PROCESSOR_SDK_08.01.00
    • PROCESSOR_SDK_08.02.00
    • Hide
      j721e-evm
      j7200-evm
      j721s2-evm
      am65xx-evm
      Show
      j721e-evm j7200-evm j721s2-evm am65xx-evm

      • Following params in sblSlaveCoreInfo_t structure are of type int32_t
        • proc_id,
        • dev_id,
        • clk_id,
        • clk_freq
      • In sbl_soc_cfg.h, these params #define for invalid cores are defined as 0xBAD00000
      • This results in C++ build failure
        • error: constant expression evaluates to 3134193664 which cannot be narrowed to type 'int32_t' (aka 'int') [-Wc++11-narrowing]

      *SBL in many places uses the hardcoding 0xBAD00000 to check for invalids*

      To avoid the narrowing issues, SBL lib needs to be fixed properly to avoid use hardcoding in many places
      and use an appropriate invalid macro(which can be used everywhere)

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-3320 - SBL should avoid hardcoding 0xBAD00...
                SYNCHRONIZED
                • Last Sync Date: