Skip to content
  1. Mar 23, 2022
  2. Mar 22, 2022
  3. Mar 04, 2022
    • Rohit Mathew's avatar
      sgi/common: rename uart output file names and shell variables. · 0055a95e
      Rohit Mathew authored
      
      
      Rename uart output file name (the file used to capture the uart output)
      and associated shell variables to match with the current uart
      configuration.
      
      TF-A boot, runtime and MM logs would be routed via secure port. The
      file name and shell variable associated with this port are prefixed
      accordingly. Likewise, uefi and OS logs would be routed via non-secure.
      The file name and shell variable associated with this port are also
      prefixed accordingly.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: Ibbf2599153620c92759942f9b7e40012d1250232
      0055a95e
    • Rohit Mathew's avatar
      rdn2cfg2/run_model: route uart logs via secure/non-secure uart · 8beba1fb
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css[0/1/2/3].pl011_s_uart_ap (secure port). UEFI and OS logs would be
      routed via css[0/1/2/3].pl011_ns_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: I0e8fa6c1b8e143cf316471a719c668b39734ef11
      8beba1fb
    • Rohit Mathew's avatar
      rdn2cfg1/run_model: route uart logs via secure/non-secure uart · a6bd0f23
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css.pl011_s_uart_ap (secure port). UEFI and OS logs would be routed
      via css.pl011_ns_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: I817290aa97d058e240c2712a1783932c37604f90
      a6bd0f23
    • Rohit Mathew's avatar
      rdn2/run_model: route uart logs via secure/non-secure uart · 23c6c765
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css.pl011_s_uart_ap (secure port). UEFI and OS logs would be routed
      via css.pl011_ns_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: Iddf81d0e93497cbc64c0abe02d4a18c56735c0d2
      23c6c765
    • Rohit Mathew's avatar
      rdedmunds/run_model: route uart logs via secure/non-secure uart · 483af2bf
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css.pl011_s_uart_ap (secure port). UEFI and OS logs would be routed
      via css.pl011_ns_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: I724e175ca23654e78369c556dd39f10c73b00c8d
      483af2bf
    • Rohit Mathew's avatar
      rdv1mc/run_model: route uart logs via secure/non-secure uart · c39a6c46
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css[0/1/2/3].pl011_uart1_ap (secure port). UEFI and OS logs would be
      routed via css[0/1/2/3].pl011_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: I179b3a4c3c2e394b3c3814867fea11840306ace1
      c39a6c46
    • Rohit Mathew's avatar
      rdv1/run_model: route uart logs via secure/non-secure uart · ff436b69
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css.pl011_uart1_ap (secure port). UEFI and OS logs would be routed via
      css.pl011_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: I2f413601a5b53fd33501183a9786e111dd9ab199
      ff436b69
    • Rohit Mathew's avatar
      rdn1edgex2/run_model: route uart logs via secure/non-secure uart · a3902ea4
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css[0/1].pl011_uart1_ap (secure port). UEFI and OS logs would be routed
      via css[0/1].pl011_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: I5d3ba4ddaa6b980dbb6745ecb2b6d8042917bcb6
      a3902ea4
    • Rohit Mathew's avatar
      rdn1edge/run_model: route uart logs via secure/non-secure uart · abdb9576
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css.pl011_uart1_ap (secure port). UEFI and OS logs would be routed via
      css.pl011_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: Ife044dd91c9308847f49082089ab7f85f7b8e3fc
      abdb9576
    • Rohit Mathew's avatar
      rde1edge/run_model: route uart logs via secure/non-secure uart · e12af7de
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css.pl011_uart1_ap (secure port). UEFI and OS logs would be routed via
      css.pl011_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: Iba08f707912147970b4a6d39be9d20eae98e72c8
      e12af7de
    • Rohit Mathew's avatar
      sgi575/run_model: route uart logs via secure/non-secure uart · 9b53c365
      Rohit Mathew authored
      
      
      Use secure and non-secure uarts in CSS instead of the uarts in SOC.
      TF-A boot, runtime and Standalone MM logs would be routed via
      css.pl011_uart1_ap (secure port). UEFI and OS logs would be routed via
      css.pl011_uart_ap (non-secure port)
      
      Additionally, as TF-A and MM logs would be routed via the same UART
      port, remove unused model parameters that are used for configuring uart
      port for capturing Standalone MM logs.
      
      Signed-off-by: Rohit Mathew's avatarRohit Mathew <rohit.mathew@arm.com>
      Change-Id: I9495b3d3a1852b87ac1c832ead5b64d917e828c6
      9b53c365
  4. Nov 30, 2021
  5. Nov 26, 2021
  6. Oct 28, 2021
  7. Oct 27, 2021
Loading