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, 18 Aug 2024 11:42:54 +0000 [thread overview]
Message-ID: <eLqq5X0ZMPNKHpVZXH4WNrsXstk9a8Yi8-WbM_tePXqj4YDSWty31k2tylIVZo8jesoRu7vTOPvsTGTSQakdPj-MtaHsp9wrsPVm3awlyBc=@proton.me> (raw)
In-Reply-To: <Ksl6cvHHvWzwYFPiPjz8Z6o1jHOs-YZxLxSEInwizt2Q93FQpDxOsZzNAcniQ_fxoGRYYCG0vci-dOrKZTmuMermDjavPmPBTyZZVW2v7NM=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]
It seemed that the InitializeSio routine was incomplete and the AST2500 wasn't being programmed properly for serial logging. I have fixed this issue by completing the the SIO initialization.
Sent with [Proton Mail](https://proton.me/) secure email.
On Sunday, July 21st, 2024 at 12:01 PM, memristor2 <memristor2@proton.me> wrote:
> 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 (#120363): https://edk2.groups.io/g/devel/message/120363
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: 5440 bytes --]
next prev parent reply other threads:[~2024-08-18 11:43 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 ` [edk2-devel] Serial Debug not working in JunctionCity Whitley Platform memristor2 via groups.io
2024-08-18 11:42 ` memristor2 via groups.io [this message]
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='eLqq5X0ZMPNKHpVZXH4WNrsXstk9a8Yi8-WbM_tePXqj4YDSWty31k2tylIVZo8jesoRu7vTOPvsTGTSQakdPj-MtaHsp9wrsPVm3awlyBc=@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