public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "memristor2 via groups.io" <memristor2=proton.me@groups.io>
To: devel@edk2.groups.io
Subject: Re: [edk2-devel] Serial Debug not working in JunctionCity Whitley Platform
Date: Sun, 21 Jul 2024 08:31:41 +0000	[thread overview]
Message-ID: <Ksl6cvHHvWzwYFPiPjz8Z6o1jHOs-YZxLxSEInwizt2Q93FQpDxOsZzNAcniQ_fxoGRYYCG0vci-dOrKZTmuMermDjavPmPBTyZZVW2v7NM=@proton.me> (raw)
In-Reply-To: <17DDB7983E5988BE.20740@groups.io>

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

Any thoughts on this?

On Sunday, June 30th, 2024 at 10:58 AM, memristor2 via groups.io <memristor2=proton.me@groups.io> wrote:

> Hello everyone,
> I'm trying to get the serial debug working on my platform but I don't know why i can't see the debug logs.
> This is the library use3d for SerialPortLIb inside the platform's dsc:
> SerialPortLib|WhitleyPkg/Library/SerialPortLib/SerialPortLib.inf
> Also these are the values of the debug Pcds:
> gEfiMdePkgTokenSpaceGuid.PcdFixedDebugPrintErrorLevel|0x802A00C7
> gEfiMdePkgTokenSpaceGuid.PcdDebugPropertyMask|0x2F
>
> gEfiMdePkgTokenSpaceGuid.PcdReportStatusCodePropertyMask|0x07
> gEfiMdeModulePkgTokenSpaceGuid.PcdStatusCodeUseSerial|TRUEgEfiSourceLevelDebugPkgTokenSpaceGuid.PcdDebugLoadImageMethod|0x2
> I don't know why I cant see the debug logs. Even though I'm sure the SerialPortInitialize function and all of its subroutines (this path SerialPortLib|WhitleyPkg/Library/SerialPortLib/SerialPortLib.inf ) are getting executed. I suspected that the ast2500 configuration isn't right (inside InitializeSio) but I double-checked it with the datasheet and everything seemed aligned to it.
> This is getting frustrating since I need the debug for further development.
> Any help is highly appreciated.
> Memristor
>
> 

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119997): https://edk2.groups.io/g/devel/message/119997
Mute This Topic: https://groups.io/mt/106956967/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 4297 bytes --]

       reply	other threads:[~2024-07-21  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17DDB7983E5988BE.20740@groups.io>
2024-07-21  8:31 ` memristor2 via groups.io [this message]
2024-08-18 11:42   ` [edk2-devel] Serial Debug not working in JunctionCity Whitley Platform memristor2 via groups.io
2024-06-30  7:28 memristor2 via groups.io

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='Ksl6cvHHvWzwYFPiPjz8Z6o1jHOs-YZxLxSEInwizt2Q93FQpDxOsZzNAcniQ_fxoGRYYCG0vci-dOrKZTmuMermDjavPmPBTyZZVW2v7NM=@proton.me' \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox