Menu
▾
▴
efidevkit-devel — EFI Dev Kit (EDK) developer discussions
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(8) |
Jun
(11) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
(12) |
Nov
(5) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
(13) |
Aug
(17) |
Sep
(9) |
Oct
(6) |
Nov
(6) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(3) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Rodrigo L. d. S. <Rod...@at...> - 2010-10-30 22:59:44
|
Good evening! Well, my duet has an "issue" with Apple's boot.efi. I can boot 10.4 boot.efi (it crashes later, LoL), but, I can't do the same with 10.5/.6 boot.efi. The same happens with the graphical rEFIt (refit.efi). I'm using EDK 1.x. The error says the executable is not valid. Any idea? Thanx! Rodrigo Lemes dos Santos Atento | Operação Telefônica Tel. 55 11 3241 9534 | 0*17 59534 | 0*17 48259 | 0*17 11315 rod...@at... Brasil. Central São Bento www.atento.com.br ________________________________ Esta mensagem de correio eletrônico e seus documentos anexos estão dirigidos EXCLUSIVAMENTE aos destinatários especificados. A informação contida pode ser CONFIDENCIAL e/ou estar LEGALMENTE PROTEGIDA e não necessariamente reflete a opinião da ATENTO. Se você receber esta mensagem por ENGANO, por favor, comunique imediatamente ao remetente e ELIMINE-A já que você NÃO ESTA AUTORIZADO ao uso, revelação, distribuição, impressão ou cópia de toda ou alguma parte da informação contida. Obrigado. This e-mail message and any attached files are intended SOLELY for the addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY PRIVILEGED information and may not necessarily represent the opinion of ATENTO. If you receive this message in ERROR, please immediately notify the sender and DELETE it since you ARE NOT UTHORIZED to use,disclose, distribute, print or copy all or part of the contained information. Thank you. |
|
From: Rodrigo L. d. S. <Rod...@at...> - 2010-10-20 17:40:17
|
Well, Intel Red-Fort CRB is the chipset. I need the model (eg: ASUS P5K-SE). Another thing, the EFI only works with a primary legacy BIOS (or firmware, in Mac's). Look this first: http://www.intel.com/technology/efi/ It says: Hardware>Firmware>EFI>Operating System ;) Well, your mobo is for Core i* Processors, but we need know the model. If you don't know, you can run everest toy see it. Rodrigo Lemes dos Santos Atento | Operação Telefônica Tel. 55 11 3241 9534 | 0*17 59534 | 0*17 48259 | 0*17 11315 rod...@at... Brasil. Central São Bento www.atento.com.br Esta mensagem de correio eletrônico e seus documentos anexos estão dirigidos EXCLUSIVAMENTE aos destinatários especificados. A informação contida pode ser CONFIDENCIAL e/ou estar LEGALMENTE PROTEGIDA e não necessariamente reflete a opinião da ATENTO. Se você receber esta mensagem por ENGANO, por favor, comunique imediatamente ao remetente e ELIMINE-A já que você NÃO ESTA AUTORIZADO ao uso, revelação, distribuição, impressão ou cópia de toda ou alguma parte da informação contida. Obrigado. This e-mail message and any attached files are intended SOLELY for the addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY PRIVILEGED information and may not necessarily represent the opinion of ATENTO. If you receive this message in ERROR, please immediately notify the sender and DELETE it since you ARE NOT UTHORIZED to use,disclose, distribute, print or copy all or part of the contained information. Thank you. -----Mensagem original----- De: James DellaMorte [mailto:ji...@de...] Enviada em: segunda-feira, 18 de outubro de 2010 12:18 Para: efi...@li... Assunto: Re: [edk] RES: Ok, It Built...Now What Hi Rodrigo, The motherboard is an Intel Red-Fort CRB. What I ultimately want to do is to load this onto a bare metal chassis. I have the Intel code for initializing the chipset, and I've integrated it. What I'm wondering is about getting the initial boot up and running. Is there code out there for that. James DellaMorte delResearch LLC. ji...@de... 508 275 3032 http://www.delresearch.com On Oct 15, 2010, at 3:10 PM, Rodrigo Lemes dos Santos wrote: > Well, only some mobos can use EFI roms, but, if your mobo haven't a builtin EFI from scratch, you can't use the EFI on your EPROM (just like X58 Mobos). > Show-me your mobo model, if it can't support EFI rom, you can use DUET, Duet is a EFI emulation for usb pen drives, but it have some issues, like "kernel panic" using some efi apps, or efi lilo =/. > Send us your mobo specifications for better instructions =) > > Rodrigo Lemes dos Santos > Atento | Operação Telefônica > Tel. 55 11 3241 9534 | 0*17 59534 | 0*17 48259 | 0*17 11315 > rod...@at... > > Brasil. Central São Bento > www.atento.com.br > > > > Esta mensagem de correio eletrônico e seus documentos anexos estão dirigidos EXCLUSIVAMENTE aos destinatários especificados. A informação contida pode ser CONFIDENCIAL e/ou estar LEGALMENTE PROTEGIDA e não necessariamente reflete a opinião da ATENTO. Se você receber esta mensagem por ENGANO, por favor, comunique imediatamente ao remetente e ELIMINE-A já que você NÃO ESTA AUTORIZADO ao uso, revelação, distribuição, impressão ou cópia de toda ou alguma parte da informação contida. Obrigado. > > This e-mail message and any attached files are intended SOLELY for the addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY PRIVILEGED information and may not necessarily represent the opinion of ATENTO. If you receive this message in ERROR, please immediately notify the sender and DELETE it since you ARE NOT UTHORIZED to use,disclose, distribute, print or copy all or part of the contained information. Thank you. > > -----Mensagem original----- > De: James DellaMorte [mailto:ji...@de...] > Enviada em: sexta-feira, 15 de outubro de 2010 13:32 > Para: efi...@li... > Assunto: [edk] Ok, It Built...Now What > > Hi all, > I have a build of the EFI source tree for my target platform (CoreI7 and Qm57). My system is a bare-metal system with not installed bios, and I want to get the very startup code rommed. It is not clear to me which of the Bazillion object files that I've created contains the reset vectors. I've browsed a bunch of documentation, and I'm still coming up short. Any pointers ? > James DellaMorte > delResearch LLC. > ji...@de... > 508 275 3032 > http://www.delresearch.com > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ efidevkit-devel mailing list efi...@li... https://lists.sourceforge.net/lists/listinfo/efidevkit-devel |
|
From: Chen, M. <min...@au...> - 2010-10-20 01:24:45
|
No, I want those mails in the year 2009, 2008, 2007, ... (I mean those sent to de...@ed...) From SourceForge.net > Projects > EFI Dev Kit > Mail > Archive, I can only find the mails sent after the transition. Thanks, Ming -----Original Message----- From: Jordan Justen [mailto:jlj...@gm...] Sent: 2010年10月20日 0:55 To: efi...@li... Subject: Re: [edk] Where are the old (tianocore.org) archives of the EDK "Dev" mailing list? Is this the email you are looking for? http://sourceforge.net/mailarchive/forum.php?thread_name=d516a67d1002010408i648cd65fuda23c422568a12d6%40mail.gmail.com&forum_name=efidevkit-devel -Jordan 2010/10/19 Chen, Ming <min...@au...>: > Thank you Michael. > > > > But I cannot find the older Mail messages from the links you provides. The > very beginning email is "[edk] build grub2 for UEFI" sent on 2010-02-01. > > > > Can you tell me where is the archive that you mentioned? > > > > Best regards, > > Ming > > > > From: Krau, Michael P [mailto:mic...@in...] > Sent: 2010年10月19日 0:28 > To: efi...@li... > Subject: Re: [edk] Where are the old (tianocore.org) archives of the EDK > "Dev" mailing list? > > > > When the UEFI Open Source Community Website changed hosting to Source Forge, > the older Mail messages were transferred into an archive. Nothing was lost > in the transition, however, the mail messages were archived to take > advantage of the "new start". > > > > The link the mailing lists in general can be found at: > > http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Mailing_Lists > > > > The link for the Mail list fact sheet for the EDK project is at: > > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > > > While the EDK-Developer mail archive can be found at: > > http://sourceforge.net/mailarchive/forum.php?forum_name=efidevkit-devel > > > > > > Thank you > > > > > > > > Michael Krau > > > > Administrator: UEFI Open Source Community Website > > www.Tianocore.org > > > > While I am an Intel employee, I do not represent Intel and am not authorized > to speak for Intel. > > ________________________________ > > From: Chen, Ming [mailto:min...@au...] > Sent: Sunday, October 17, 2010 6:42 PM > To: efi...@li... > Subject: [edk] Where are the old (tianocore.org) archives of the EDK "Dev" > mailing list? > > > > Hi all, > > > > I tried to look for some old mails (before the transition) of the EDK "Dev" > discussion but no luck. Anybody know where they have been moved? > > > > Thanks in advance. > > Ming > > > > > > NOTE: The information in this message is intended for the personal and > confidential use of the designated recipient(s) named above. To the extent > the recipient(s) is/are bound by a non-disclosure agreement, or other > agreement that contains an obligation of confidentiality, with AuthenTec, > then this message and/or any attachments shall be considered confidential > information and subject to the confidentiality terms of that agreement. If > the reader of this message is not the intended recipient named above, you > are notified that you have received this document in error, and any review, > dissemination, distribution or copying of this message is strictly > prohibited. If you have received this document in error, please delete the > original message and notify the sender immediately. > > > > AuthenTec, Inc. http://www.authentec.com > > > > -- > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ efidevkit-devel mailing list efi...@li... https://lists.sourceforge.net/lists/listinfo/efidevkit-devel NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately. Thank You! AuthenTec, Inc. http://www.authentec.com/ |
|
From: Jordan J. <jlj...@gm...> - 2010-10-19 16:55:02
|
Is this the email you are looking for? http://sourceforge.net/mailarchive/forum.php?thread_name=d516a67d1002010408i648cd65fuda23c422568a12d6%40mail.gmail.com&forum_name=efidevkit-devel -Jordan 2010/10/19 Chen, Ming <min...@au...>: > Thank you Michael. > > > > But I cannot find the older Mail messages from the links you provides. The > very beginning email is "[edk] build grub2 for UEFI" sent on 2010-02-01. > > > > Can you tell me where is the archive that you mentioned? > > > > Best regards, > > Ming > > > > From: Krau, Michael P [mailto:mic...@in...] > Sent: 2010年10月19日 0:28 > To: efi...@li... > Subject: Re: [edk] Where are the old (tianocore.org) archives of the EDK > "Dev" mailing list? > > > > When the UEFI Open Source Community Website changed hosting to Source Forge, > the older Mail messages were transferred into an archive. Nothing was lost > in the transition, however, the mail messages were archived to take > advantage of the "new start". > > > > The link the mailing lists in general can be found at: > > http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Mailing_Lists > > > > The link for the Mail list fact sheet for the EDK project is at: > > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > > > While the EDK-Developer mail archive can be found at: > > http://sourceforge.net/mailarchive/forum.php?forum_name=efidevkit-devel > > > > > > Thank you > > > > > > > > Michael Krau > > > > Administrator: UEFI Open Source Community Website > > www.Tianocore.org > > > > While I am an Intel employee, I do not represent Intel and am not authorized > to speak for Intel. > > ________________________________ > > From: Chen, Ming [mailto:min...@au...] > Sent: Sunday, October 17, 2010 6:42 PM > To: efi...@li... > Subject: [edk] Where are the old (tianocore.org) archives of the EDK "Dev" > mailing list? > > > > Hi all, > > > > I tried to look for some old mails (before the transition) of the EDK "Dev" > discussion but no luck. Anybody know where they have been moved? > > > > Thanks in advance. > > Ming > > > > > > NOTE: The information in this message is intended for the personal and > confidential use of the designated recipient(s) named above. To the extent > the recipient(s) is/are bound by a non-disclosure agreement, or other > agreement that contains an obligation of confidentiality, with AuthenTec, > then this message and/or any attachments shall be considered confidential > information and subject to the confidentiality terms of that agreement. If > the reader of this message is not the intended recipient named above, you > are notified that you have received this document in error, and any review, > dissemination, distribution or copying of this message is strictly > prohibited. If you have received this document in error, please delete the > original message and notify the sender immediately. > > > > AuthenTec, Inc. http://www.authentec.com > > > > -- > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > |
|
From: Chen, M. <min...@au...> - 2010-10-19 09:23:44
|
Thank you Michael. But I cannot find the older Mail messages from the links you provides. The very beginning email is “[edk] build grub2 for UEFI” sent on 2010-02-01. Can you tell me where is the archive that you mentioned? Best regards, Ming From: Krau, Michael P [mailto:mic...@in...] Sent: 2010年10月19日 0:28 To: efi...@li... Subject: Re: [edk] Where are the old (tianocore.org) archives of the EDK "Dev" mailing list? When the UEFI Open Source Community Website changed hosting to Source Forge, the older Mail messages were transferred into an archive. Nothing was lost in the transition, however, the mail messages were archived to take advantage of the “new start”. The link the mailing lists in general can be found at: http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Mailing_Lists The link for the Mail list fact sheet for the EDK project is at: https://lists.sourceforge.net/lists/listinfo/efidevkit-devel While the EDK-Developer mail archive can be found at: http://sourceforge.net/mailarchive/forum.php?forum_name=efidevkit-devel Thank you Michael Krau Administrator: UEFI Open Source Community Website www.Tianocore.org While I am an Intel employee, I do not represent Intel and am not authorized to speak for Intel. ________________________________ From: Chen, Ming [mailto:min...@au...] Sent: Sunday, October 17, 2010 6:42 PM To: efi...@li... Subject: [edk] Where are the old (tianocore.org) archives of the EDK "Dev" mailing list? Hi all, I tried to look for some old mails (before the transition) of the EDK “Dev” discussion but no luck. Anybody know where they have been moved? Thanks in advance. Ming NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately. AuthenTec, Inc. http://www.authentec.com<http://www.authentec.com/> NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately. Thank You! AuthenTec, Inc. http://www.authentec.com/ |
|
From: Krau, M. P <mic...@in...> - 2010-10-18 16:28:21
|
When the UEFI Open Source Community Website changed hosting to Source Forge, the older Mail messages were transferred into an archive. Nothing was lost in the transition, however, the mail messages were archived to take advantage of the "new start". The link the mailing lists in general can be found at: http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Mailing_Lists The link for the Mail list fact sheet for the EDK project is at: https://lists.sourceforge.net/lists/listinfo/efidevkit-devel While the EDK-Developer mail archive can be found at: http://sourceforge.net/mailarchive/forum.php?forum_name=efidevkit-devel Thank you Michael Krau Administrator: UEFI Open Source Community Website www.Tianocore.org While I am an Intel employee, I do not represent Intel and am not authorized to speak for Intel. ________________________________ From: Chen, Ming [mailto:min...@au...] Sent: Sunday, October 17, 2010 6:42 PM To: efi...@li... Subject: [edk] Where are the old (tianocore.org) archives of the EDK "Dev" mailing list? Hi all, I tried to look for some old mails (before the transition) of the EDK "Dev" discussion but no luck. Anybody know where they have been moved? Thanks in advance. Ming NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately. AuthenTec, Inc. http://www.authentec.com<http://www.authentec.com/> |
|
From: James D. <ji...@de...> - 2010-10-18 14:18:43
|
Hi Rodrigo, The motherboard is an Intel Red-Fort CRB. What I ultimately want to do is to load this onto a bare metal chassis. I have the Intel code for initializing the chipset, and I've integrated it. What I'm wondering is about getting the initial boot up and running. Is there code out there for that. James DellaMorte delResearch LLC. ji...@de... 508 275 3032 http://www.delresearch.com On Oct 15, 2010, at 3:10 PM, Rodrigo Lemes dos Santos wrote: > Well, only some mobos can use EFI roms, but, if your mobo haven't a builtin EFI from scratch, you can't use the EFI on your EPROM (just like X58 Mobos). > Show-me your mobo model, if it can't support EFI rom, you can use DUET, Duet is a EFI emulation for usb pen drives, but it have some issues, like "kernel panic" using some efi apps, or efi lilo =/. > Send us your mobo specifications for better instructions =) > > Rodrigo Lemes dos Santos > Atento | Operação Telefônica > Tel. 55 11 3241 9534 | 0*17 59534 | 0*17 48259 | 0*17 11315 > rod...@at... > > Brasil. Central São Bento > www.atento.com.br > > > > Esta mensagem de correio eletrônico e seus documentos anexos estão dirigidos EXCLUSIVAMENTE aos destinatários especificados. A informação contida pode ser CONFIDENCIAL e/ou estar LEGALMENTE PROTEGIDA e não necessariamente reflete a opinião da ATENTO. Se você receber esta mensagem por ENGANO, por favor, comunique imediatamente ao remetente e ELIMINE-A já que você NÃO ESTA AUTORIZADO ao uso, revelação, distribuição, impressão ou cópia de toda ou alguma parte da informação contida. Obrigado. > > This e-mail message and any attached files are intended SOLELY for the addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY PRIVILEGED information and may not necessarily represent the opinion of ATENTO. If you receive this message in ERROR, please immediately notify the sender and DELETE it since you ARE NOT UTHORIZED to use,disclose, distribute, print or copy all or part of the contained information. Thank you. > > -----Mensagem original----- > De: James DellaMorte [mailto:ji...@de...] > Enviada em: sexta-feira, 15 de outubro de 2010 13:32 > Para: efi...@li... > Assunto: [edk] Ok, It Built...Now What > > Hi all, > I have a build of the EFI source tree for my target platform (CoreI7 and Qm57). My system is a bare-metal system with not installed bios, and I want to get the very startup code rommed. It is not clear to me which of the Bazillion object files that I've created contains the reset vectors. I've browsed a bunch of documentation, and I'm still coming up short. Any pointers ? > James DellaMorte > delResearch LLC. > ji...@de... > 508 275 3032 > http://www.delresearch.com > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel |
|
From: Chen, M. <min...@au...> - 2010-10-18 01:57:57
|
Hi all, I tried to look for some old mails (before the transition) of the EDK "Dev" discussion but no luck. Anybody know where they have been moved? Thanks in advance. Ming NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately. Thank You! AuthenTec, Inc. http://www.authentec.com/ |
|
From: Rodrigo L. d. S. <Rod...@at...> - 2010-10-15 19:23:25
|
Well, only some mobos can use EFI roms, but, if your mobo haven't a builtin EFI from scratch, you can't use the EFI on your EPROM (just like X58 Mobos). Show-me your mobo model, if it can't support EFI rom, you can use DUET, Duet is a EFI emulation for usb pen drives, but it have some issues, like "kernel panic" using some efi apps, or efi lilo =/. Send us your mobo specifications for better instructions =) Rodrigo Lemes dos Santos Atento | Operação Telefônica Tel. 55 11 3241 9534 | 0*17 59534 | 0*17 48259 | 0*17 11315 rod...@at... Brasil. Central São Bento www.atento.com.br Esta mensagem de correio eletrônico e seus documentos anexos estão dirigidos EXCLUSIVAMENTE aos destinatários especificados. A informação contida pode ser CONFIDENCIAL e/ou estar LEGALMENTE PROTEGIDA e não necessariamente reflete a opinião da ATENTO. Se você receber esta mensagem por ENGANO, por favor, comunique imediatamente ao remetente e ELIMINE-A já que você NÃO ESTA AUTORIZADO ao uso, revelação, distribuição, impressão ou cópia de toda ou alguma parte da informação contida. Obrigado. This e-mail message and any attached files are intended SOLELY for the addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY PRIVILEGED information and may not necessarily represent the opinion of ATENTO. If you receive this message in ERROR, please immediately notify the sender and DELETE it since you ARE NOT UTHORIZED to use,disclose, distribute, print or copy all or part of the contained information. Thank you. -----Mensagem original----- De: James DellaMorte [mailto:ji...@de...] Enviada em: sexta-feira, 15 de outubro de 2010 13:32 Para: efi...@li... Assunto: [edk] Ok, It Built...Now What Hi all, I have a build of the EFI source tree for my target platform (CoreI7 and Qm57). My system is a bare-metal system with not installed bios, and I want to get the very startup code rommed. It is not clear to me which of the Bazillion object files that I've created contains the reset vectors. I've browsed a bunch of documentation, and I'm still coming up short. Any pointers ? James DellaMorte delResearch LLC. ji...@de... 508 275 3032 http://www.delresearch.com ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ efidevkit-devel mailing list efi...@li... https://lists.sourceforge.net/lists/listinfo/efidevkit-devel |
|
From: James D. <ji...@de...> - 2010-10-15 16:32:36
|
Hi all, I have a build of the EFI source tree for my target platform (CoreI7 and Qm57). My system is a bare-metal system with not installed bios, and I want to get the very startup code rommed. It is not clear to me which of the Bazillion object files that I've created contains the reset vectors. I've browsed a bunch of documentation, and I'm still coming up short. Any pointers ? James DellaMorte delResearch LLC. ji...@de... 508 275 3032 http://www.delresearch.com |
|
From: Rodrigo L. d. S. <Rod...@at...> - 2010-08-12 22:27:37
|
Hello! God evening! I found you googling with a friend on qemu forums (GMANE). My name is Rodrigo, I have a question about DUET EFI Emulator. Well, I have builded my DUET with Tiano Core EDK MS VSC ++ 2005, MASM 611 and the latest Win DDK. My DUET works fine, but, I can't boot the latest rEFIt. I guess this happen because some graphical .efi driver is disabled, or some option on config.env. I can boot only the oldies rEFIts (text mode). Can you help-me? Thanks a lot! Att. Rodrigo Lemes dos Santos Atento Brasil | Padronização e desenvolvimento operacional Tel. 55 11 3241-9534 / 0*17 59534 / 59455 / 48259 www.atento.com.br |
|
From: Jordan J. <jlj...@gm...> - 2010-07-22 22:12:52
|
All, Does anyone know if the EFI python port supports the python 'socket' module? Thanks, -Jordan On Thu, Jul 22, 2010 at 09:07, Duane Voth <du...@gm...> wrote: > Alright, let me focus on one thing. > Python uses dynamically loaded libraries to provide additional module > support (I'm specifically interested in the network support provided via > "import socket"). I havent seen any of these for the EFI environment. > There should be a Lib directory in the Python source tree... Where can I > get these libraries/modules for EFI Python? > Duane > On Wed, Jul 14, 2010 at 5:14 PM, Jordan Justen <jlj...@gm...> wrote: >> >> On Fri, Jul 9, 2010 at 19:57, Duane Voth <du...@gm...> wrote: >> > While I have your attention... how do we use all these tools? I don't >> > see >> > any docs and many (especially the drivers) are not intuitive. Python >> > isn't >> > usable without its libraries - is there a socket.dxe et.al. for python? >> >> Sorry, but which tools/drivers are you referring too? >> * edk2-buildtools/BaseTools >> * efi-toolkit (which has a Python efi-app port) >> * the efi-apps under edk2/EdkShellBinPkg >> * the drivers under the edk2 tree >> >> -Jordan >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > edk2-devel mailing list > edk...@li... > https://lists.sourceforge.net/lists/listinfo/edk2-devel > > |
|
From: freevanx Q <fre...@gm...> - 2010-07-03 06:06:11
|
If you don't have the complete source code of BIOS, you may need: 1. Initial your Com port of SuperIo (Optional) 2. Setting Com port parameters 3. Use EfiDebugPrint function directly or define some macro likes DEBUG, such as #define MY_DEBUG(arg) EfiDebugPrint arg Jensen On Sat, Jul 3, 2010 at 9:49 AM, Alex Xin <xin...@gm...> wrote: > DEBUG() macro is only supported in debug build. You cannot use that macro in > a production build. > I suggest that you can try to direct write your debug message to serial > port. > > On Sat, Jul 3, 2010 at 2:42 AM, rangasai C <ran...@gm...> wrote: >> >> Hi all, >> I am working on PCIe option ROM development. My driver works fine as long >> as I load it from the shell. This mean, I can load from the shell and talk >> to my drive. However, when I convert my driver (.efi file) into a .rom file >> (using efirom.exe utility) and then flash my card with this image and reboot >> my target system, I am seeing all kinds of issues (like no video, or video >> comes and system reboots etc. ).. With some elementary debugging techniques >> (since I can't use Prints at this stage), I could verify that the option ROM >> image is shadowed properly but looks like there are some issues with the >> initialization code. What I am missing is a good debugging environment, to >> root cause the issue. >> I don't have an ITP but from the spec, I read that I could use the DEBUG() >> macro. >> Could anybody explain how I could use this macro to output my debug prints >> onto a COM port and see it in hyperterminal ? >> My Target system is an Intel DG43GT motherboard. I tried connecting the >> 9pin serial port header to my host system via a Null cable and USB to COM >> connector but no luck. Also I don't see any option to do serial redirection. >> When I type "sermode" in shell, it can't find any devices. >> Is this motherboard a good test bench for option ROM development or should >> I think of changing it. >> Any pointers would be very helpful. >> Thanks in advance. >> Regards, >> Sai Chaganty >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> efidevkit-devel mailing list >> efi...@li... >> https://lists.sourceforge.net/lists/listinfo/efidevkit-devel >> > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > |
|
From: Alex X. <xin...@gm...> - 2010-07-03 01:49:56
|
DEBUG() macro is only supported in debug build. You cannot use that macro in a production build. I suggest that you can try to direct write your debug message to serial port. On Sat, Jul 3, 2010 at 2:42 AM, rangasai C <ran...@gm...> wrote: > Hi all, > I am working on PCIe option ROM development. My driver works fine as long > as I load it from the shell. This mean, I can load from the shell and talk > to my drive. However, when I convert my driver (.efi file) into a .rom file > (using efirom.exe utility) and then flash my card with this image and reboot > my target system, I am seeing all kinds of issues (like no video, or video > comes and system reboots etc. ).. With some elementary debugging techniques > (since I can't use Prints at this stage), I could verify that the option ROM > image is shadowed properly but looks like there are some issues with the > initialization code. What I am missing is a good debugging environment, to > root cause the issue. > I don't have an ITP but from the spec, I read that I could use the DEBUG() > macro. > Could anybody explain how I could use this macro to output my debug prints > onto a COM port and see it in hyperterminal ? > > My Target system is an Intel DG43GT motherboard. I tried connecting the > 9pin serial port header to my host system via a Null cable and USB to COM > connector but no luck. Also I don't see any option to do serial redirection. > When I type "sermode" in shell, it can't find any devices. > Is this motherboard a good test bench for option ROM development or should > I think of changing it. > > Any pointers would be very helpful. > > Thanks in advance. > > Regards, > Sai Chaganty > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > |
|
From: rangasai C <ran...@gm...> - 2010-07-02 18:42:15
|
Hi all, I am working on PCIe option ROM development. My driver works fine as long as I load it from the shell. This mean, I can load from the shell and talk to my drive. However, when I convert my driver (.efi file) into a .rom file (using efirom.exe utility) and then flash my card with this image and reboot my target system, I am seeing all kinds of issues (like no video, or video comes and system reboots etc. ).. With some elementary debugging techniques (since I can't use Prints at this stage), I could verify that the option ROM image is shadowed properly but looks like there are some issues with the initialization code. What I am missing is a good debugging environment, to root cause the issue. I don't have an ITP but from the spec, I read that I could use the DEBUG() macro. Could anybody explain how I could use this macro to output my debug prints onto a COM port and see it in hyperterminal ? My Target system is an Intel DG43GT motherboard. I tried connecting the 9pin serial port header to my host system via a Null cable and USB to COM connector but no luck. Also I don't see any option to do serial redirection. When I type "sermode" in shell, it can't find any devices. Is this motherboard a good test bench for option ROM development or should I think of changing it. Any pointers would be very helpful. Thanks in advance. Regards, Sai Chaganty |
|
From: Jiangbo W <jia...@gm...> - 2010-06-24 01:48:30
|
Hi, All,
I have a question:
In PeiMain.c file, after the MemoryDiscoveredPPI installed, it did not call
ProcessNotifyList() function. In current code the ProcessNofiyList()
function will not be called until a new PEIM be dispatched (in
PeiDispatcher() function Dispatcher.c file). it can not cover this
situation: I register a notify with NOTIFY_DISPTCH type on
MemoryDiscoveredPPI and hope it be dispatched before the next PEIM, so i
think it should call ProcessNotifyList() after MemoryDiscoveredPpi installed
instantly.
any comment?
EDK1.06 PeiMain.c file Line247-252
//
// Alert any listeners that there is permanent memory available
//
PEI_PERF_START (&PrivateData.PS,L"DisMem", NULL, 0);
Status = PeiInstallPpi (&PrivateData.PS, &mMemoryDiscoveredPpi);
ProcessNotifyList(); //it should process the Notify list and dispatch
any notifies for MemoryDiscoveredPpi instantly.
PEI_PERF_END (&PrivateData.PS,L"DisMem", NULL, 0);
BRs
wjb
|
|
From: ktckd <kt...@gm...> - 2010-06-23 14:01:27
|
It is working now. Thank you very much. On Wed, Jun 23, 2010 at 7:17 AM, Tian, Hot <hot...@in...> wrote: > You can try to re-download the EDK1.06 now. > > > > *From:* Tian, Hot [mailto:hot...@in...] > *Sent:* Wednesday, June 23, 2010 10:11 AM > > *To:* efi...@li... > *Subject:* Re: [edk] Build error on EDK 1.06 > > > > Please update the following line in “Sample\Version.env”: > > EDK_BUILD_VERSION = Edk 1.06 > > To > > EDK_BUILD_VERSION = Edk1.06 > > > > We will update the official snapshot to remove this space. > > > > Thanks, > > Hot > > > > *From:* ktckd [mailto:kt...@gm...] > *Sent:* Wednesday, June 23, 2010 6:38 AM > *To:* efi...@li... > *Subject:* [edk] Build error on EDK 1.06 > > > > > I am getting the following error while building EDK 1.06 on my unit. > > > C:\Edk_1.06\Sample\Platform\DUET\Build\Tools\StrGather -scan -vdbr -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageStrings.sdb > -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Strings.sdb > -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmString.sdb > -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerStrings.sdb > -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerStrings.sdb > -ppflag "/nologo /W4 /WX /EHs-c- /GR- /Gy /D USE_VC8 /c > /FoC:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\Bds.sdb > -I C:\Edk_1.06\Foundation -I C:\Edk_1.06\Foundation\Efi -I > C:\Edk_1.06\Foundation\Framework -I > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds -I > C:\Edk_1.06\Foundation\Include -I C:\Edk_1.06\Foundation\Include\IA32 -I > C:\Edk_1.06\Foundation\Efi\Include -I > C:\Edk_1.06\Foundation\Framework\Include -I > C:\Edk_1.06\Foundation\Include\IndustryStandard -I > C:\Edk_1.06\Foundation\Core\Dxe -I C:\Edk_1.06\Foundation\Core\Dxe\IA32 -I > C:\Edk_1.06\Foundation\Library\Dxe\Include -I > C:\Edk_1.06\Foundation\Library\Dxe\Include\IA32 -I > C:\Edk_1.06\Foundation\Library\Dxe\UefiEfiIfrSupportLib -I > C:\Edk_1.06\Foundation\Cpu\Pentium\Include -I > C:\Edk_1.06\Sample\Platform\Generic\Pei\Capsule -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\GenericBds -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\GenericBds\IA32 -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\BootMngr -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\BootMaint -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr -I > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds > /Zi /Gm > /FdC:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\BdsObj > /D EFI_SPECIFICATION_VERSION=0x0002000A /D > PI_SPECIFICATION_VERSION=0x00010000 /D TIANO_RELEASE_VERSION=0x00080006 /D > EFI_BUILD_VERSION="L\"Edk 1.06\"" /D > EFI_FIRMWARE_VENDOR="L\"TianoCore.org\"" /D USB_LEGACY_OFF /D EFI_DEBUG /D > EFI_PEI_PERFORMANCE /D EFI_DXE_PERFORMANCE /D EFI_DXE_PERFORMANCE /D EFI32 > /O1 /X" -oh > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\BdsStrDefs.h > -od > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\Bds.sdb > -skipext .uni -skipext .h > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\PlatformData.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\BdsPlatform.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BdsEntry.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPage.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageStrings.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageVfr.vfr > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Language.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\String.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Strings.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Capsules.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\MemoryTest.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Hotkey.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmString.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\bm.vfr > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmLib.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BootOption.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\ConsoleOption.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\Data.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\Variable.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\UpdatePage.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BBSsupport.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BootMaint.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\FileExplorer.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\FE.vfr > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManager.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerStrings.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerVfr.Vfr > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManager.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerStrings.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerVfr.Vfr > StrGather : error E0000: must specify string defines file name to > preprocess before scan > StrGather v1.2 - Intel UEFI String Gather Utility > Copyright (C), 2004 - 2008 Intel Corporation > Built from Edk 1.06, project of TianoCore.org > > Usage: > StrGather -parse [OPTION] FILE > StrGather -scan [OPTION] FILE > StrGather -dump [OPTION] > Description: > Process unicode strings file. > Common options include: > -h or -? for this help information > -db Database required name of output/input database file > -bn BaseName for use in the .h and .c output files > Default = BaseName > -v for verbose output > -vdbw for verbose output when writing database > -vdbr for verbose output when reading database > -od FileName to specify an output database file name > Parse options include: > -i IncludePath add IncludePath to list of search paths > -dep FileName to specify an output dependency file name > -newdb to not read in existing database file > -uqs to indicate that unquoted strings are used > FileNames name of one or more unicode files to parse > Scan options include: > -scan scan text file(s) for STRING_TOKEN() usage > -skipext .ext to skip scan of files with .ext filename extension > -ppflag "Flags" to specify the C preprocessor flags > -oh FileName to specify string defines file name for preprocessor > -ignorenotfound ignore if a given STRING_TOKEN(STR) is not > found in the database > FileNames one or more files to scan > Dump options include: > -oc FileName write string data to FileName > -oh FileName write string defines to FileName > -ou FileName dump database to unicode file FileName > -lang Lang only dump for the language 'Lang' > use ';' to separate multiple languages > -if FileName to specify an indirection file > -hpk FileName to create an HII export pack of the strings > > The expected process is to parse a unicode string file to create an initial > database of string identifier names and string definitions. Then text files > should be scanned for STRING_TOKEN() usages, and the referenced > strings will be tagged as used in the database. After all files have been > scanned, then the database should be dumped to create the necessary output > files. > > NMAKE : fatal error U1077: > 'C:\Edk_1.06\Sample\Platform\DUET\Build\Tools\StrGather.EXE' : return code > '0x2' > Stop. > > > > > > Can someone please throw some light? > > Thanks, > > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > |
|
From: Tian, H. <hot...@in...> - 2010-06-23 12:20:42
|
You can try to re-download the EDK1.06 now. From: Tian, Hot [mailto:hot...@in...] Sent: Wednesday, June 23, 2010 10:11 AM To: efi...@li... Subject: Re: [edk] Build error on EDK 1.06 Please update the following line in "Sample\Version.env": EDK_BUILD_VERSION = Edk 1.06 To EDK_BUILD_VERSION = Edk1.06 We will update the official snapshot to remove this space. Thanks, Hot From: ktckd [mailto:kt...@gm...] Sent: Wednesday, June 23, 2010 6:38 AM To: efi...@li... Subject: [edk] Build error on EDK 1.06 I am getting the following error while building EDK 1.06 on my unit. C:\Edk_1.06\Sample\Platform\DUET\Build\Tools\StrGather -scan -vdbr -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageStrings.sdb -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Strings.sdb -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmString.sdb -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerStrings.sdb -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerStrings.sdb -ppflag "/nologo /W4 /WX /EHs-c- /GR- /Gy /D USE_VC8 /c /FoC:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\Bds.sdb -I C:\Edk_1.06\Foundation -I C:\Edk_1.06\Foundation\Efi -I C:\Edk_1.06\Foundation\Framework -I C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds -I C:\Edk_1.06\Foundation\Include -I C:\Edk_1.06\Foundation\Include\IA32 -I C:\Edk_1.06\Foundation\Efi\Include -I C:\Edk_1.06\Foundation\Framework\Include -I C:\Edk_1.06\Foundation\Include\IndustryStandard -I C:\Edk_1.06\Foundation\Core\Dxe -I C:\Edk_1.06\Foundation\Core\Dxe\IA32 -I C:\Edk_1.06\Foundation\Library\Dxe\Include -I C:\Edk_1.06\Foundation\Library\Dxe\Include\IA32 -I C:\Edk_1.06\Foundation\Library\Dxe\UefiEfiIfrSupportLib -I C:\Edk_1.06\Foundation\Cpu\Pentium\Include -I C:\Edk_1.06\Sample\Platform\Generic\Pei\Capsule -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\GenericBds -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\GenericBds\IA32 -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\BootMngr -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\BootMaint -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr -I C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds /Zi /Gm /FdC:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\BdsObj /D EFI_SPECIFICATION_VERSION=0x0002000A /D PI_SPECIFICATION_VERSION=0x00010000 /D TIANO_RELEASE_VERSION=0x00080006 /D EFI_BUILD_VERSION="L\"Edk 1.06\"" /D EFI_FIRMWARE_VENDOR="L\"TianoCore.org\"" /D USB_LEGACY_OFF /D EFI_DEBUG /D EFI_PEI_PERFORMANCE /D EFI_DXE_PERFORMANCE /D EFI_DXE_PERFORMANCE /D EFI32 /O1 /X" -oh C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\BdsStrDefs.h -od C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\Bds.sdb -skipext .uni -skipext .h C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\PlatformData.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\BdsPlatform.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BdsEntry.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPage.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageStrings.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageVfr.vfr C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Language.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\String.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Strings.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Capsules.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\MemoryTest.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Hotkey.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmString.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\bm.vfr C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmLib.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BootOption.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\ConsoleOption.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\Data.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\Variable.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\UpdatePage.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BBSsupport.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BootMaint.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\FileExplorer.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\FE.vfr C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManager.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerStrings.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerVfr.Vfr C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManager.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerStrings.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerVfr.Vfr StrGather : error E0000: must specify string defines file name to preprocess before scan StrGather v1.2 - Intel UEFI String Gather Utility Copyright (C), 2004 - 2008 Intel Corporation Built from Edk 1.06, project of TianoCore.org Usage: StrGather -parse [OPTION] FILE StrGather -scan [OPTION] FILE StrGather -dump [OPTION] Description: Process unicode strings file. Common options include: -h or -? for this help information -db Database required name of output/input database file -bn BaseName for use in the .h and .c output files Default = BaseName -v for verbose output -vdbw for verbose output when writing database -vdbr for verbose output when reading database -od FileName to specify an output database file name Parse options include: -i IncludePath add IncludePath to list of search paths -dep FileName to specify an output dependency file name -newdb to not read in existing database file -uqs to indicate that unquoted strings are used FileNames name of one or more unicode files to parse Scan options include: -scan scan text file(s) for STRING_TOKEN() usage -skipext .ext to skip scan of files with .ext filename extension -ppflag "Flags" to specify the C preprocessor flags -oh FileName to specify string defines file name for preprocessor -ignorenotfound ignore if a given STRING_TOKEN(STR) is not found in the database FileNames one or more files to scan Dump options include: -oc FileName write string data to FileName -oh FileName write string defines to FileName -ou FileName dump database to unicode file FileName -lang Lang only dump for the language 'Lang' use ';' to separate multiple languages -if FileName to specify an indirection file -hpk FileName to create an HII export pack of the strings The expected process is to parse a unicode string file to create an initial database of string identifier names and string definitions. Then text files should be scanned for STRING_TOKEN() usages, and the referenced strings will be tagged as used in the database. After all files have been scanned, then the database should be dumped to create the necessary output files. NMAKE : fatal error U1077: 'C:\Edk_1.06\Sample\Platform\DUET\Build\Tools\StrGather.EXE' : return code '0x2' Stop. Can someone please throw some light? Thanks, |
|
From: Tian, H. <hot...@in...> - 2010-06-23 02:12:46
|
Please update the following line in "Sample\Version.env": EDK_BUILD_VERSION = Edk 1.06 To EDK_BUILD_VERSION = Edk1.06 We will update the official snapshot to remove this space. Thanks, Hot From: ktckd [mailto:kt...@gm...] Sent: Wednesday, June 23, 2010 6:38 AM To: efi...@li... Subject: [edk] Build error on EDK 1.06 I am getting the following error while building EDK 1.06 on my unit. C:\Edk_1.06\Sample\Platform\DUET\Build\Tools\StrGather -scan -vdbr -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageStrings.sdb -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Strings.sdb -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmString.sdb -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerStrings.sdb -db C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerStrings.sdb -ppflag "/nologo /W4 /WX /EHs-c- /GR- /Gy /D USE_VC8 /c /FoC:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\Bds.sdb -I C:\Edk_1.06\Foundation -I C:\Edk_1.06\Foundation\Efi -I C:\Edk_1.06\Foundation\Framework -I C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds -I C:\Edk_1.06\Foundation\Include -I C:\Edk_1.06\Foundation\Include\IA32 -I C:\Edk_1.06\Foundation\Efi\Include -I C:\Edk_1.06\Foundation\Framework\Include -I C:\Edk_1.06\Foundation\Include\IndustryStandard -I C:\Edk_1.06\Foundation\Core\Dxe -I C:\Edk_1.06\Foundation\Core\Dxe\IA32 -I C:\Edk_1.06\Foundation\Library\Dxe\Include -I C:\Edk_1.06\Foundation\Library\Dxe\Include\IA32 -I C:\Edk_1.06\Foundation\Library\Dxe\UefiEfiIfrSupportLib -I C:\Edk_1.06\Foundation\Cpu\Pentium\Include -I C:\Edk_1.06\Sample\Platform\Generic\Pei\Capsule -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\GenericBds -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\GenericBds\IA32 -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\BootMngr -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\BootMaint -I C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr -I C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds /Zi /Gm /FdC:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\BdsObj /D EFI_SPECIFICATION_VERSION=0x0002000A /D PI_SPECIFICATION_VERSION=0x00010000 /D TIANO_RELEASE_VERSION=0x00080006 /D EFI_BUILD_VERSION="L\"Edk 1.06\"" /D EFI_FIRMWARE_VENDOR="L\"TianoCore.org\"" /D USB_LEGACY_OFF /D EFI_DEBUG /D EFI_PEI_PERFORMANCE /D EFI_DXE_PERFORMANCE /D EFI_DXE_PERFORMANCE /D EFI32 /O1 /X" -oh C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\BdsStrDefs.h -od C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\Bds.sdb -skipext .uni -skipext .h C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\PlatformData.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\BdsPlatform.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BdsEntry.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPage.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageStrings.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageVfr.vfr C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Language.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\String.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Strings.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Capsules.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\MemoryTest.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Hotkey.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmString.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\bm.vfr C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmLib.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BootOption.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\ConsoleOption.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\Data.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\Variable.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\UpdatePage.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BBSsupport.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BootMaint.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\FileExplorer.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\FE.vfr C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManager.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerStrings.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerVfr.Vfr C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManager.c C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerStrings.uni C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerVfr.Vfr StrGather : error E0000: must specify string defines file name to preprocess before scan StrGather v1.2 - Intel UEFI String Gather Utility Copyright (C), 2004 - 2008 Intel Corporation Built from Edk 1.06, project of TianoCore.org Usage: StrGather -parse [OPTION] FILE StrGather -scan [OPTION] FILE StrGather -dump [OPTION] Description: Process unicode strings file. Common options include: -h or -? for this help information -db Database required name of output/input database file -bn BaseName for use in the .h and .c output files Default = BaseName -v for verbose output -vdbw for verbose output when writing database -vdbr for verbose output when reading database -od FileName to specify an output database file name Parse options include: -i IncludePath add IncludePath to list of search paths -dep FileName to specify an output dependency file name -newdb to not read in existing database file -uqs to indicate that unquoted strings are used FileNames name of one or more unicode files to parse Scan options include: -scan scan text file(s) for STRING_TOKEN() usage -skipext .ext to skip scan of files with .ext filename extension -ppflag "Flags" to specify the C preprocessor flags -oh FileName to specify string defines file name for preprocessor -ignorenotfound ignore if a given STRING_TOKEN(STR) is not found in the database FileNames one or more files to scan Dump options include: -oc FileName write string data to FileName -oh FileName write string defines to FileName -ou FileName dump database to unicode file FileName -lang Lang only dump for the language 'Lang' use ';' to separate multiple languages -if FileName to specify an indirection file -hpk FileName to create an HII export pack of the strings The expected process is to parse a unicode string file to create an initial database of string identifier names and string definitions. Then text files should be scanned for STRING_TOKEN() usages, and the referenced strings will be tagged as used in the database. After all files have been scanned, then the database should be dumped to create the necessary output files. NMAKE : fatal error U1077: 'C:\Edk_1.06\Sample\Platform\DUET\Build\Tools\StrGather.EXE' : return code '0x2' Stop. Can someone please throw some light? Thanks, |
|
From: ktckd <kt...@gm...> - 2010-06-22 22:37:59
|
> > > I am getting the following error while building EDK 1.06 on my unit. > > > C:\Edk_1.06\Sample\Platform\DUET\Build\Tools\StrGather -scan -vdbr -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageStrings.sdb > -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Strings.sdb > -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmString.sdb > -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerStrings.sdb > -db > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerStrings.sdb > -ppflag "/nologo /W4 /WX /EHs-c- /GR- /Gy /D USE_VC8 /c > /FoC:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\Bds.sdb > -I C:\Edk_1.06\Foundation -I C:\Edk_1.06\Foundation\Efi -I > C:\Edk_1.06\Foundation\Framework -I > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds -I > C:\Edk_1.06\Foundation\Include -I C:\Edk_1.06\Foundation\Include\IA32 -I > C:\Edk_1.06\Foundation\Efi\Include -I > C:\Edk_1.06\Foundation\Framework\Include -I > C:\Edk_1.06\Foundation\Include\IndustryStandard -I > C:\Edk_1.06\Foundation\Core\Dxe -I C:\Edk_1.06\Foundation\Core\Dxe\IA32 -I > C:\Edk_1.06\Foundation\Library\Dxe\Include -I > C:\Edk_1.06\Foundation\Library\Dxe\Include\IA32 -I > C:\Edk_1.06\Foundation\Library\Dxe\UefiEfiIfrSupportLib -I > C:\Edk_1.06\Foundation\Cpu\Pentium\Include -I > C:\Edk_1.06\Sample\Platform\Generic\Pei\Capsule -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\GenericBds -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\GenericBds\IA32 -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\BootMngr -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\BootMaint -I > C:\Edk_1.06\Sample\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr -I > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds > /Zi /Gm > /FdC:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\BdsObj > /D EFI_SPECIFICATION_VERSION=0x0002000A /D > PI_SPECIFICATION_VERSION=0x00010000 /D TIANO_RELEASE_VERSION=0x00080006 /D > EFI_BUILD_VERSION="L\"Edk 1.06\"" /D > EFI_FIRMWARE_VENDOR="L\"TianoCore.org\"" /D USB_LEGACY_OFF /D EFI_DEBUG /D > EFI_PEI_PERFORMANCE /D EFI_DXE_PERFORMANCE /D EFI_DXE_PERFORMANCE /D EFI32 > /O1 /X" -oh > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\BdsStrDefs.h > -od > C:\EDK_1.06\Sample\Platform\DUET\Build\IA32\Sample\Platform\DUET\Dxe\PlatformBds\Bds.sdb > -skipext .uni -skipext .h > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\PlatformData.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\BdsPlatform.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BdsEntry.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPage.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageStrings.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\FrontPageVfr.vfr > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Language.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\String.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Strings.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Capsules.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\MemoryTest.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\Hotkey.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmString.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\bm.vfr > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BmLib.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BootOption.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\ConsoleOption.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\Data.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\Variable.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\UpdatePage.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BBSsupport.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\BootMaint.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\FileExplorer.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMaint\FE.vfr > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManager.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerStrings.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\BootMngr\BootManagerVfr.Vfr > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManager.c > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerStrings.uni > C:\Edk_1.06\Sample\Platform\DUET\Dxe\PlatformBds\..\..\..\..\Platform\Generic\Dxe\UefiPlatformBds\DeviceMngr\DeviceManagerVfr.Vfr > StrGather : error E0000: must specify string defines file name to > preprocess before scan > StrGather v1.2 - Intel UEFI String Gather Utility > Copyright (C), 2004 - 2008 Intel Corporation > Built from Edk 1.06, project of TianoCore.org > > Usage: > StrGather -parse [OPTION] FILE > StrGather -scan [OPTION] FILE > StrGather -dump [OPTION] > Description: > Process unicode strings file. > Common options include: > -h or -? for this help information > -db Database required name of output/input database file > -bn BaseName for use in the .h and .c output files > Default = BaseName > -v for verbose output > -vdbw for verbose output when writing database > -vdbr for verbose output when reading database > -od FileName to specify an output database file name > Parse options include: > -i IncludePath add IncludePath to list of search paths > -dep FileName to specify an output dependency file name > -newdb to not read in existing database file > -uqs to indicate that unquoted strings are used > FileNames name of one or more unicode files to parse > Scan options include: > -scan scan text file(s) for STRING_TOKEN() usage > -skipext .ext to skip scan of files with .ext filename extension > -ppflag "Flags" to specify the C preprocessor flags > -oh FileName to specify string defines file name for preprocessor > -ignorenotfound ignore if a given STRING_TOKEN(STR) is not > found in the database > FileNames one or more files to scan > Dump options include: > -oc FileName write string data to FileName > -oh FileName write string defines to FileName > -ou FileName dump database to unicode file FileName > -lang Lang only dump for the language 'Lang' > use ';' to separate multiple languages > -if FileName to specify an indirection file > -hpk FileName to create an HII export pack of the strings > > The expected process is to parse a unicode string file to create an initial > database of string identifier names and string definitions. Then text files > should be scanned for STRING_TOKEN() usages, and the referenced > strings will be tagged as used in the database. After all files have been > scanned, then the database should be dumped to create the necessary output > files. > > NMAKE : fatal error U1077: > 'C:\Edk_1.06\Sample\Platform\DUET\Build\Tools\StrGather.EXE' : return code > '0x2' > Stop. > > > > > > Can someone please throw some light? > > Thanks, > |
|
From: KESHAV P.R. <sko...@gm...> - 2010-06-20 16:25:18
|
Since 16-bit MASM does not work in Windows x64 versions, it is impossible to compile the DUET bootsectors in EDK leading to build failure. I modified the Efildr makefiles ( http://www.4shared.com/file/mT2sXwpO/Modified_files_for_compiling_E.html - gmail's not allowing executables in attachments) to use the pre-compiled bootsector binaries from EDK2-DuetPkg instead ( copied to Edk\Sample\Platform\DUET\Loader\BootSector\bin\ folder ). Please apply the modified makefiles patch to edk svn repo. Regards. |
|
From: rangasai C <ran...@gm...> - 2010-06-12 01:56:20
|
Thank you 2010/6/11 Alex Xin <xin...@gm...> > Every IBV has their own debug tools, contact your IBV for details. If you'r > looking for a hardware emulator, contact American Arium for their XDP > emulator. > > 2010/6/12 libeili <li...@12...> > >> Hi,Sai >> >> About the debugger I think some companies have there own debug tools,you >> can bug it. >> >> About the hardware you can have try intel series MB,such as INTEL >> DG43NB,and this is my test platform for EFI option ROM development. >> >> sky >> 在2010-06-11 09:08:47，"rangasai C" <ran...@gm...> 写道： >> >> Hi Everyone, >> Can anyone suggest which debugger can be used for source level debugging >> for option ROM (legacy and UEFI) development ? >> If there are any hardware requirements (e.g. MB etc.) please provide the >> details. >> >> Thanks in advance. >> >> Regards, >> Sai >> >> >> >> ------------------------------ >> 网易为中小企业免费提供企业邮箱（自主域名） <http://ym.163.com/?from=od3> >> >> ------------------------------------------------------------------------------ >> ThinkGeek and WIRED's GeekDad team up for the Ultimate >> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the >> lucky parental unit. See the prize list and enter to win: >> http://p.sf.net/sfu/thinkgeek-promo >> _______________________________________________ >> efidevkit-devel mailing list >> efi...@li... >> https://lists.sourceforge.net/lists/listinfo/efidevkit-devel >> >> > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > |
|
From: Alex X. <xin...@gm...> - 2010-06-12 01:47:43
|
Every IBV has their own debug tools, contact your IBV for details. If you'r looking for a hardware emulator, contact American Arium for their XDP emulator. 2010/6/12 libeili <li...@12...> > Hi,Sai > > About the debugger I think some companies have there own debug tools,you > can bug it. > > About the hardware you can have try intel series MB,such as INTEL > DG43NB,and this is my test platform for EFI option ROM development. > > sky > 在2010-06-11 09:08:47，"rangasai C" <ran...@gm...> 写道： > > Hi Everyone, > Can anyone suggest which debugger can be used for source level debugging > for option ROM (legacy and UEFI) development ? > If there are any hardware requirements (e.g. MB etc.) please provide the > details. > > Thanks in advance. > > Regards, > Sai > > > > ------------------------------ > 网易为中小企业免费提供企业邮箱（自主域名） <http://ym.163.com/?from=od3> > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > |
|
From: libeili <li...@12...> - 2010-06-12 01:29:36
|
Hi,Sai About the debugger I think some companies have there own debug tools,you can bug it. About the hardware you can have try intel series MB,such as INTEL DG43NB,and this is my test platform for EFI option ROM development. sky 在2010-06-11 09:08:47，"rangasai C" <ran...@gm...> 写道： Hi Everyone, Can anyone suggest which debugger can be used for source level debugging for option ROM (legacy and UEFI) development ? If there are any hardware requirements (e.g. MB etc.) please provide the details. Thanks in advance. Regards, Sai |
|
From: rangasai C <ran...@gm...> - 2010-06-11 23:55:25
|
Hi all, I have couple of questions regarding Efi Device Driver. 1. How can I convert an image (.efi) into an option ROM image (.rom) ? I have tried efirom.exe for that and I just want to confirm if that is all is required. 2. In case of legacy option ROM, we used to define a separate header to indicate that it is a PnP controller (with the "PnP" signature and other details). How do we do the same in case of EFI option ROM ? Thank you. Regards, Sai |
3 messages has been excluded from this view by a project administrator.
