coreboot April 2016

coreboot@coreboot.org

49 participants
97 discussions

Re: [coreboot] ERROR: Ramstage region _postram_cbfs_cache overlapped
by Julius Werner 05 Apr '16

05 Apr '16

This is a recently added warning (see https://review.coreboot.org/13949) that tells you that you are trying to use a payload which would overlap the parts of coreboot that are loading it (risking random corruption errors and such). The fix is to link your payload to a different base address which does not overlap the POSTRAM_CBFS_CACHE region in the memlayout.ld of your board/chipset. Which board are you building for and which payload are you trying to use?

1 0

ERROR: Ramstage region _postram_cbfs_cache overlapped
by Sid R 04 Apr '16

04 Apr '16

Hello, While compiling coreboot, I get the following error - any ideas on how to address this: Performing operation on 'BOOTBLOCK' region... W: Written area will abut bottom of target region: any unused space will keep its current contents Performing operation on 'COREBOOT' region... Performing operation on 'COREBOOT' region... CBFS fallback/romstage Performing operation on 'COREBOOT' region... CBFS fallback/ramstage Performing operation on 'COREBOOT' region... CBFS fallback/payload Performing operation on 'COREBOOT' region... CBFS config Performing operation on 'COREBOOT' region... CBFS revision Performing operation on 'COREBOOT' region... CBFS payload_config Performing operation on 'COREBOOT' region... CBFS payload_revision Performing operation on 'COREBOOT' region... Performing operation on 'COREBOOT' region... ERROR: Ramstage region _postram_cbfs_cache overlapped by: fallback/payload make: *** [check-ramstage-overlaps] Error 1 Thanks Sid

1 0

ASUS F2A85-M: Richland-APU A10-6800k supported?
by Daniel Kulesz 04 Apr '16

04 Apr '16

Hi, with the Richland-patches being available, did someone already try to run one of the "high-end" Richland APUs like the A10-6800k in the F2A85-M with Coreboot? Cheers, Daniel

1 0

Re: [coreboot] Is windows driver for EHCI DEBUG available.
by Chris Roberts 04 Apr '16

04 Apr '16

I recently worked with Kyosti to update the EHCI Debug cable. You can find an updated version of the cable here, under examples/debugdev_full_duplex. https://github.com/night199uk/fx2lib <https://github.com/night199uk/fx2lib> There is a .PDF with a build spec based on the newer version of the FX2LP boards that are easily available from taobao or eBay. It should work with the old ones too. It is a slightly modified version of Kyosti’s original (excellent) spec that got me started. The new cable/firmware complies with the 8-byte packet requirement of the EHCI Debug Device specification to avoid overrunning the EHCI Debug port buffers. Also in theory it should be faster (perhaps if you remove the 8-byte packetization) due to the use of GPIF streaming. The EHCI Debug cable implements the CDC ACM spec - I didn’t modify that part at all, but in theory it should appear as a standard serial port under Windows. I’ve tested it with Linux and OS X and both support it natively through CDC ACM drivers and I believe a friend of mine tested it working as such. Also EDK2 supports it for SourceLevelDebugPkg. That needs some minor patches as EDK2 hard-codes the USB endpoint numbers for Ajays - I may contribute back patches to read those from the descriptor at some point but it’s an easy modification to make manually. Regards, Chris. > On 4 Apr 2016, at 13:00, Kyösti Mälkki <kyosti.malkki(a)gmail.com> wrote: > > > ---------- Forwarded message ---------- > From: Zheng Bao <fishbaoz(a)hotmail.com <mailto:fishbaoz@hotmail.com>> > Date: Fri, Mar 18, 2016 at 4:01 PM > Subject: [coreboot] Is windows driver for EHCI DEBUG available. > To: "coreboot(a)coreboot.org <mailto:coreboot@coreboot.org>" <coreboot(a)coreboot.org <mailto:coreboot@coreboot.org>> > > > Hi, all, > http://www.coreboot.org/DIY_EHCI_debug_dongle <https://www.coreboot.org/DIY_EHCI_debug_dongle> > http://www.coreboot.org/EHCI_debug_dongle <https://www.coreboot.org/EHCI_debug_dongle> > I want to build a EHCI debug dongle based on above links. > I am wondering if the windows driver of the dongle is available. > I google it but can not find it. I assume it is a generic driver. > Who knows about that? > > Thanks. > > Zheng > > -- > coreboot mailing list: coreboot(a)coreboot.org <mailto:coreboot@coreboot.org> > https://www.coreboot.org/mailman/listinfo/coreboot <https://www.coreboot.org/mailman/listinfo/coreboot> >

2 1

ASUS KGPE-D16: Increase in boot time by 1 second
by Paul Menzel 04 Apr '16

04 Apr '16

Dear Timothy, dear Damien, looking through the board status data, I noticed the boot time increased by one second for the ASUS KGPE-D16. ``` asus/kgpe-d16/4.3-584-gcc9963e/2016-03-25T19_52_04Z/coreboot_timestamps.txt:Total Time: 18,389,685 asus/kgpe-d16/4.3-587-gec38c3d/2016-03-26T21_40_56Z/coreboot_timestamps.txt:Total Time: 19,425,140 ``` Did the hardware configuration change, or did commit ec38c3d9 (nb/amd/amdmct: Select max_lanes based on ECC presence or absence) [1] do that? Maybe the command below shows you some pointers in the board status repository. ``` diff -ru asus/kgpe-d16/4.3-584-gcc9963e/2016-03-25T19_52_04Z asus/kgpe-d16/4.3-587-gec38c3d/2016-03-26T21_40_56Z/ ``` Thanks, Paul [1] https://review.coreboot.org/13725 PS: Here the differences of the time stamps. ``` --- asus/kgpe-d16/4.3-584-gcc9963e/2016-03-25T19_52_04Z/coreboot_timestamps.txt 2016-03-28 10:50:03.751723776 +0200 +++ asus/kgpe-d16/4.3-587-gec38c3d/2016-03-26T21_40_56Z/coreboot_timestamps.txt 2016-03-28 10:50:03.843726364 +0200 @@ -1,21 +1,21 @@ 16 entries total: - 0:1st timestamp 106,862 - 1:start of rom stage 109,067 (2,204) - 2:before ram initialization 703,897 (594,830) - 3:after ram initialization 16,416,242 (15,712,345) - 4:end of romstage 16,507,764 (91,521) - 10:start of ramstage 16,564,607 (56,842) - 30:device enumeration 16,564,610 (3) - 40:device configuration 18,026,405 (1,461,794) - 50:device enable 18,033,787 (7,381) - 60:device initialization 18,035,132 (1,345) - 70:device setup done 18,459,042 (423,910) - 75:cbmem post 18,459,045 (2) - 80:write tables 18,459,046 (1) - 90:load payload 18,470,351 (11,304) - 15:starting LZMA decompress (ignore for x86) 18,470,708 (357) - 16:finished LZMA decompress (ignore for x86) 18,496,547 (25,839) - 99:selfboot jump 18,496,555 (7) + 0:1st timestamp 107,007 + 1:start of rom stage 108,992 (1,984) + 2:before ram initialization 720,604 (611,612) + 3:after ram initialization 17,449,260 (16,728,655) + 4:end of romstage 17,541,247 (91,986) + 10:start of ramstage 17,598,146 (56,899) + 30:device enumeration 17,598,150 (3) + 40:device configuration 19,061,426 (1,463,275) + 50:device enable 19,068,442 (7,015) + 60:device initialization 19,069,861 (1,419) + 70:device setup done 19,494,645 (424,784) + 75:cbmem post 19,494,647 (1) + 80:write tables 19,494,648 (1) + 90:load payload 19,505,952 (11,303) + 15:starting LZMA decompress (ignore for x86) 19,506,309 (357) + 16:finished LZMA decompress (ignore for x86) 19,532,149 (25,839) + 99:selfboot jump 19,532,157 (7) -Total Time: 18,389,685 +Total Time: 19,425,140 ```

2 1

building SPD: How to decide Trfc by spec
by Zheng Bao 04 Apr '16

04 Apr '16

DDR3-1066 DDR3-1333 DDR3-1600 DDR3-1866 unit 7-7-7 9-9-9 11-11-11 13-13-13 nRFC-1 Gb 59 74 88 103 nCK nRFC- 2 Gb 86 107 128 150 nCK nRFC- 4 Gb 160 200 240 281 nCK nRFC- 8 Gb 187 234 280 328 nCK Hi, All, Above text is extracted from the spec of a DDR3 chip. I am trying to decide the Trfc. What does "-x Gb" mean? How do I know which row in the table I should use? Thanks. Zheng

2 1

New Defects reported by Coverity Scan for coreboot
by scan-admin＠coverity.com 01 Apr '16

01 Apr '16

Hi, Please find the latest report on new defect(s) introduced to coreboot found with Coverity Scan. 2 new defect(s) introduced to coreboot found with Coverity Scan. 334 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 2 of 2 defect(s) ** CID 1353736: Control flow issues (NO_EFFECT) /3rdparty/arm-trusted-firmware/plat/mediatek/mt8173/plat_pm.c: 386 in plat_affinst_suspend() ________________________________________________________________________________________________________ *** CID 1353736: Control flow issues (NO_EFFECT) /3rdparty/arm-trusted-firmware/plat/mediatek/mt8173/plat_pm.c: 386 in plat_affinst_suspend() 380 381 mmio_write_32(rv, sec_entrypoint); 382 383 if (afflvl < MPIDR_AFFLVL2) 384 spm_mcdi_prepare_for_off_state(mpidr, afflvl); 385 >>> CID 1353736: Control flow issues (NO_EFFECT) >>> This greater-than-or-equal-to-zero comparison of an unsigned value is always true. "afflvl >= 0U". 386 if (afflvl >= MPIDR_AFFLVL0) 387 mt_platform_save_context(mpidr); 388 389 /* Perform the common cluster specific operations */ 390 if (afflvl >= MPIDR_AFFLVL1) { 391 /* Disable coherency if this cluster is to be turned off */ ** CID 1353737: Control flow issues (NO_EFFECT) /3rdparty/arm-trusted-firmware/plat/mediatek/mt8173/plat_pm.c: 459 in plat_affinst_suspend_finish() ________________________________________________________________________________________________________ *** CID 1353737: Control flow issues (NO_EFFECT) /3rdparty/arm-trusted-firmware/plat/mediatek/mt8173/plat_pm.c: 459 in plat_affinst_suspend_finish() 453 /* Perform the common cluster specific operations */ 454 if (afflvl >= MPIDR_AFFLVL1) { 455 /* Enable coherency if this cluster was off */ 456 plat_cci_enable(); 457 } 458 >>> CID 1353737: Control flow issues (NO_EFFECT) >>> This greater-than-or-equal-to-zero comparison of an unsigned value is always true. "afflvl >= 0U". 459 if (afflvl >= MPIDR_AFFLVL0) 460 mt_platform_restore_context(mpidr); 461 462 if (afflvl < MPIDR_AFFLVL2) 463 spm_mcdi_finish_for_on_state(mpidr, afflvl); 464 ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/coreboot?tab=overview To manage Coverity Scan email notifications for "coreboot(a)coreboot.org", click https://scan.coverity.com/subscriptions/edit?email=coreboot%40coreboot.org&…

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot April 2016