Re: [flashrom] [coreboot] [LinuxBoot] FOSDEM 2019 deadline today
by Carl-Daniel Hailfinger
In that case, I'd also like to point you to the deadline for submitting
main track talks which is tomorrow(!).
https://fosdem.org/2019/news/2018-08-10-call-for-participation/
Having a coreboot/LinuxBoot talk there would be awesome. Ron/David,
could you submit something or do you have someone in mind who can do that?
There's also lightning talks, deadline is a bit later.
OK, I'm submitting a request for a stand. I need a backup contact for
the stand. Who is willing to do that? AFAICS we can still change the
backup contact later if life happens.
Regards,
Carl-Daniel
On 02.11.2018 20:48, David Hendricks wrote:
>
>
> On Fri, Nov 2, 2018 at 9:15 AM 'Ron Minnich' via linuxboot
> <linuxboot(a)googlegroups.com <mailto:linuxboot@googlegroups.com>> wrote:
>
> I"m leaning to yes, by which I mean if you do it, I'll show up.
>
> I can't believe I said that.
> On Fri, Nov 2, 2018 at 7:20 AM Carl-Daniel Hailfinger
> <c-d.hailfinger.devel.2006(a)gmx.net
> <mailto:c-d.hailfinger.devel.2006@gmx.net>> wrote:
> >
> > Hi!
> >
> > FOSDEM next year will be on 2 & 3 February 2019.
> > The deadline for applying for a stand is today.
> > Do we want a coreboot/flashrom/LinuxBoot stand/booth?
>
>
> Same as what Ron said. I think someone from FB can be there to talk
> about coreboot/LinuxBoot stuff and perhaps bring some hardware to demo.
>
>
4 months, 3 weeks
80/100/132 column line width policy
by Carl-Daniel Hailfinger
Hi,
we're hitting the 80 column limit in our code in ways which actually
reduce readability for the code. Examples are various multiline messages
and complicated nested code where refactoring to a separate function
doesn't make sense.
Keeping the old 80 column limit is not really an option anymore.
Standard terminal sizes have one of 80, 100 or 132 columns.
Given the monitor resolutions many people have nowadays, I think it is
safe to say that you can fit two xterms with 100 columns horizonally
next to each other. 100 columns should also be sufficient for a msg_p*
of roughly 80 columns of text.
132 columns provide more leeway, but IMHO that would be too wide for
good readability (and my screen can't fit two xterms side-by-side anymore).
Of course some files have sections where any column limit is not
acceptable (board lists etc.), but the column limit violations should be
limited to the affected file sections, not whole files.
Comments?
I'd like to get this decided today or tomorrow so we know where we need
line breaks in Stefan Tauner's new struct flashchip patch.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
6 months, 1 week
FOSDEM Hardware Enablement Devroom
by Paul Kocialkowski
A Hardware Enablement devroom will be taking place at FOSDEM this year,
on Sunday 10 December 2017. This newly-created devroom is the result of
3 proposals that were merged together. It is co-organized by several
individuals.
The devroom covers all aspects related to hardware enablement and
support with free software, including aspects related to boot software,
firmwares, drivers and userspace tools and adaptation.
Proposals for talks related to these topics are welcome and can be
submitted until Sunday 26 November 2017 via the pentabarf interface.
Short talks are encouraged over longer ones in order to cover a wide
range of topics.
The announcement for the devroom, that contains all the useful
information, was published at:
https://lists.fosdem.org/pipermail/fosdem/2017-October/002649.html
Cheers and see you at FOSDEM!
--
Paul Kocialkowski, developer of free digital technology and hardware
support
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
6 months, 2 weeks
Question about SIL3114 board with a N28F010-120 flash chip on it
by Peter Cost
Dear Reader,
I have a SIL3114 PCI board with an Intel N28F010-120 flash chip on it,
and I can't reprogram it since it lacks the 12V Vpp. I checked that
there is no +12V connection on the PCI edge connector of the board and
the VPP pin seems to be unconnected.
My question is this. When I apply 12V Vpp to the chip will I then be
able to reprogram the board with the Lattice (Silicon Image) dos utility
or the flashrom utility.
I am an experienced engineer, but my eprom day's are from way back in
the 80's and early 90's and I have never done anything with flash proms
other than reprogramming boards with the supplied software.
Thanks for any response.
Kind regards,
Peter Cost
6 months, 3 weeks
Heads Up: Ongoing layout-support work
by Nico Huber
Dear fellow flashrom contributors,
I'll likely work on flashrom's layout support in the next few weeks.
Part of it will be to finalize the work on per-region file arguments.
There were multiple proposals for the command-line syntax without a
real consent so far, [1] sums it up. If you have any preferences,
please comment soon before things are set in stone.
Nico
[1] https://www.flashrom.org/Per_region_file_arguments
6 months, 3 weeks
Researching Lenovo IdeaPad 300-15ISK for Possible Future Support with FlashROM, and Later, CoreBoot
by moriel5
The title pretty much sums it up, however here are the details.
I have managed to get a hold of my laptop's schematics due to them being leaked.I am currently working with someone over at Bios-Mods to modify the firmware ("unlocking it").Interestingly, this laptop (which I had already updated it's firmware), has no WiFi whitelist, and I had bought brand-new, about a month after it came out.
The EC controller, an ITE IT8586E-LQFP, is connected via the LCP bus, and the touchpad, internal keyboard, and the NCT7718W thermal sensor are all connected to it, according to the schematics.I forget whether I have the same exact chip (though I believe it to be so) on my laptop, as 99% of the details match my laptop.
The schematics refer to 2 SPI chips, an 8MB W25Q64FVSSIQ_SO8 on UC3 as the main SPI chip, and an 4MB W25Q32FVSSIQ_SO8 on UC6 as backup.I have only one SPI chip, an 8MB W25Q64FVS1011532 on UC3, with the UC6 solder point existing, so I could theoretically solder a backup SPI chip.A TPM chip, the Z32H320TC, also sits on the LCP bus, with a direct connection to the chipset, unlike the touchpad, internal keyboard and the thermal sensor, according to the schematics.I forget whether I have this TPM chip, but once again, I believe that it is so.
The IdeaPad 300-15's motherboard is codenamed "Paris".
It also (optionally) comes with an AMD dGPU, without direct connection to any graphical output.My specific model only has no dGPU.
Can anyone help me with my research? I'm still not very experienced with the actual work regarding electronics, most of my experience is with researching them.If there is any more information required from the schematics, I'll gladly share them, and if anyone wants the schematics, I can send them over.
6 months, 3 weeks
Output of motherboard Acer EM61SM/EM61PM
by Roberto Masutti
flashrom v0.9.5.2-r1546 on Linux 3.2.0-4-amd64 (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org
flashrom was built with libpci 3.1.7, GCC 4.6.2, little endian
Command line (1 args): flashrom -V
Calibrating delay loop... OS timer resolution is 1 usecs, 870M loops per second, 10 myus = 11 us, 100 myus = 101 us, 1000 myus = 1000 us, 10000 myus = 10016 us, 4 myus = 5 us, OK.
Initializing internal programmer
No coreboot table found.
DMI string system-manufacturer: "Acer"
DMI string system-product-name: "Aspire T180"
DMI string system-version: "R01-B4"
DMI string baseboard-manufacturer: "Acer"
DMI string baseboard-product-name: "EM61SM/EM61PM "
DMI string baseboard-version: " "
DMI string chassis-type: "Desktop"
Found ITE Super I/O, ID 0x8726 on port 0x2e
Found chipset "NVIDIA MCP61" with PCI ID 10de:03e0. Enabling flash write... This chipset is not really supported yet. Guesswork...
ISA/LPC bridge reg 0x8a contents: 0x00, bit 6 is 0, bit 5 is 0
Flash bus type is LPC
Found SMBus device 10de:03eb at 00:01:1
MCP SPI BAR is at 0x00000000
MCP SPI is not used.
Please send the output of "flashrom -V" to flashrom(a)flashrom.org with
your board name: flashrom -V as the subject to help us finish support for your
chipset. Thanks.
OK.
Super I/O ID 0x8726 is not on the list of flash capable controllers.
The following protocols are supported: LPC.
Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x26, id2 0xff, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Found SST flash chip "SST49LF040B" (512 kB, LPC) at physical address 0xfff80000.
Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x50
Found SST flash chip "SST49LF040B" (512 kB, LPC).
No operations were specified.
Restoring PCI config space for 00:01:0 reg 0x6d
Restoring PCI config space for 00:01:0 reg 0x90
Restoring PCI config space for 00:01:0 reg 0x8c
Restoring PCI config space for 00:01:0 reg 0x88
6 months, 3 weeks
[PATCH] Do not abuse cs_bit
by Vicente Bergas
"cs_bit[s]" variable stores the bit location for Chip Select, as implied by the name.
A new variable "cfg" is added for static configuration bits, like Output Enables.
If outputs are disabled during operation, then the result will depend on the
target having proper pull-up resistors, which is not always guaranteed.
Signed-off-by: Vicente Bergas <vicencb(a)gmail.com>
---
ft2232_spi.c | 33 +++++++++++++++------------------
1 file changed, 15 insertions(+), 18 deletions(-)
diff --git a/ft2232_spi.c b/ft2232_spi.c
index 95584aa..fe7fcf8 100644
--- a/ft2232_spi.c
+++ b/ft2232_spi.c
@@ -84,18 +84,19 @@ const struct dev_entry devs_ft2232spi[] = {
#define BITMODE_BITBANG_NORMAL 1
#define BITMODE_BITBANG_SPI 2
-/* The variables cs_bits and pindir store the values for the "set data bits low byte" MPSSE command that
+/* The variables cs_bit, cfg and pindir store the values for the "set data bits low byte" MPSSE command that
* sets the initial state and the direction of the I/O pins. The pin offsets are as follows:
* SCK is bit 0.
* DO is bit 1.
* DI is bit 2.
- * CS is bit 3.
+ * CS is at cs_bit. Default is bit 3.
*
* The default values (set below) are used for most devices:
* value: 0x08 CS=high, DI=low, DO=low, SK=low
* dir: 0x0b CS=output, DI=input, DO=output, SK=output
*/
-static uint8_t cs_bits = 0x08;
+static uint8_t cs_bit = 0x08;
+static uint8_t cfg = 0x00;
static uint8_t pindir = 0x0b;
static struct ftdi_context ftdic_context;
@@ -209,10 +210,9 @@ int ft2232_spi_init(void)
ft2232_type = AMONTEC_JTAGKEY_PID;
channel_count = 2;
/* JTAGkey(2) needs to enable its output via Bit4 / GPIOL0
- * value: 0x18 OE=high, CS=high, DI=low, DO=low, SK=low
- * dir: 0x1b OE=output, CS=output, DI=input, DO=output, SK=output */
- cs_bits = 0x18;
- pindir = 0x1b;
+ * value: 0x08 #OE=low, CS=high, DI=low, DO=low, SK=low
+ * dir: 0x1b #OE=output, CS=output, DI=input, DO=output, SK=output */
+ pindir |= 0x10;
} else if (!strcasecmp(arg, "picotap")) {
ft2232_vid = GOEPEL_VID;
ft2232_type = GOEPEL_PICOTAP_PID;
@@ -229,8 +229,7 @@ int ft2232_spi_init(void)
/* In its default configuration it is a jtagkey clone */
ft2232_type = FTDI_FT2232H_PID;
channel_count = 2;
- cs_bits = 0x18;
- pindir = 0x1b;
+ pindir |= 0x10;
} else if (!strcasecmp(arg, "openmoko")) {
ft2232_vid = FIC_VID;
ft2232_type = OPENMOKO_DBGBOARD_PID;
@@ -242,8 +241,7 @@ int ft2232_spi_init(void)
/* arm-usb-ocd(-h) has an output buffer that needs to be enabled by pulling ADBUS4 low.
* value: 0x08 #OE=low, CS=high, DI=low, DO=low, SK=low
* dir: 0x1b #OE=output, CS=output, DI=input, DO=output, SK=output */
- cs_bits = 0x08;
- pindir = 0x1b;
+ pindir |= 0x10;
} else if (!strcasecmp(arg, "arm-usb-tiny")) {
ft2232_vid = OLIMEX_VID;
ft2232_type = OLIMEX_ARM_TINY_PID;
@@ -253,8 +251,7 @@ int ft2232_spi_init(void)
ft2232_type = OLIMEX_ARM_OCD_H_PID;
channel_count = 2;
/* See arm-usb-ocd */
- cs_bits = 0x08;
- pindir = 0x1b;
+ pindir |= 0x10;
} else if (!strcasecmp(arg, "arm-usb-tiny-h")) {
ft2232_vid = OLIMEX_VID;
ft2232_type = OLIMEX_ARM_TINY_H_PID;
@@ -338,8 +335,8 @@ int ft2232_spi_init(void)
return -2;
} else {
unsigned int pin = temp + 4;
- cs_bits |= 1 << pin;
- pindir |= 1 << pin;
+ cs_bit = 1 << pin;
+ pindir = (pindir & ~0x08) | cs_bit;
}
}
free(arg);
@@ -425,7 +422,7 @@ int ft2232_spi_init(void)
msg_pdbg("Set data bits\n");
buf[0] = SET_BITS_LOW;
- buf[1] = cs_bits;
+ buf[1] = cfg | cs_bit;
buf[2] = pindir;
if (send_buf(ftdic, buf, 3)) {
ret = -8;
@@ -480,7 +477,7 @@ static int ft2232_spi_send_command(struct flashctx *flash,
*/
msg_pspew("Assert CS#\n");
buf[i++] = SET_BITS_LOW;
- buf[i++] = 0 & ~cs_bits; /* assertive */
+ buf[i++] = cfg & ~cs_bit;
buf[i++] = pindir;
if (writecnt) {
@@ -521,7 +518,7 @@ static int ft2232_spi_send_command(struct flashctx *flash,
msg_pspew("De-assert CS#\n");
buf[i++] = SET_BITS_LOW;
- buf[i++] = cs_bits;
+ buf[i++] = cfg | cs_bit;
buf[i++] = pindir;
ret = send_buf(ftdic, buf, i);
failed |= ret;
--
2.19.1
6 months, 4 weeks
