Skip to content
  1. Mar 28, 2022
  2. Mar 27, 2022
    • Rohit Mathew's avatar
      sgi/common: rename uart output file names and shell variables. · d85efc63
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      d85efc63
    • Rohit Mathew's avatar
      rdn2cfg2/run_model: route uart logs via secure/non-secure uart · 87a2e6a1
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      87a2e6a1
    • Rohit Mathew's avatar
      rdn2cfg1/run_model: route uart logs via secure/non-secure uart · fca0701b
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      fca0701b
    • Rohit Mathew's avatar
      rdn2/run_model: route uart logs via secure/non-secure uart · edf13045
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      edf13045
    • Rohit Mathew's avatar
      rdedmunds/run_model: route uart logs via secure/non-secure uart · 385133e4
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      385133e4
    • Rohit Mathew's avatar
      rdv1mc/run_model: route uart logs via secure/non-secure uart · 653177c9
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      653177c9
    • Rohit Mathew's avatar
      rdv1/run_model: route uart logs via secure/non-secure uart · 26e246ea
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      26e246ea
    • Rohit Mathew's avatar
      rdn1edgex2/run_model: route uart logs via secure/non-secure uart · 29789d75
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      29789d75
    • Rohit Mathew's avatar
      rdn1edge/run_model: route uart logs via secure/non-secure uart · b09b0fc4
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      b09b0fc4
    • Rohit Mathew's avatar
      rde1edge/run_model: route uart logs via secure/non-secure uart · a7a74d12
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      a7a74d12
    • Rohit Mathew's avatar
      sgi575/run_model: route uart logs via secure/non-secure uart · 124a256d
      Rohit Mathew authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      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
      124a256d
    • Pranav Madhu's avatar
      run_model: Add parameters to improve FVP's timing precisition · 0bbc1679
      Pranav Madhu authored and Thomas Abraham's avatar Thomas Abraham committed
      
      
      For supporting ACS SBSA compiance, and to support hotplug functionality,
      it is required to improve the timing precisition of FVP. Add parameters
      for the same.
      
      Change-Id: Iec23af51ab376ee378ad12f9f6715dd5cb32d325
      Signed-off-by: Pranav Madhu's avatarPranav Madhu <pranav.madhu@arm.com>
      0bbc1679
    • Thomas Abraham's avatar
      infra: remove spaces from the displayed model command line · 3eda6e47
      Thomas Abraham authored
      
      
      The parameters used to launch the model is displayed when the model is
      launched. There are redundant spaces displayed in the displayed model
      parameters. Remove those redundant spaces.
      
      Signed-off-by: Thomas Abraham's avatarThomas Abraham <thomas.abraham@arm.com>
      Change-Id: I3eeda07accdd88ee8e5444945f94ea4a993eee21
      3eda6e47
  3. Nov 30, 2021
  4. Nov 26, 2021
  5. Oct 28, 2021
  6. Oct 27, 2021
Loading