Hello there, I have a question regarding coreboot.
I was wondering if work was still being done to port coreboot to the Dell OptiPlex 7010. I was looking at commit 882d3c3574cc24f1bcf16b71c5090cc71ef725a6, but it seems the board didn’t boot at that stage in time. I have also not found much information regarding 4f19f4a7ebe7783830343d5ffc917142266fabf9 either, so I was wondering if work was still being done to port coreboot to the OptiPlex 7010, given its stock firmware doesn’t really work that great (I'd be happy to elaborate), even at revision A29, so I wanted to replace it with coreboot.
Thanks.
在 2018/12/25 上午3:05, Kumonie Williams 写道:
Hello there, I have a question regarding coreboot.
I was wondering if work was still being done to port coreboot to the Dell OptiPlex 7010. I was looking at commit 882d3c3574cc24f1bcf16b71c5090cc71ef725a6, but it seems the board didn’t boot at that stage in time. I have also not found much information regarding 4f19f4a7ebe7783830343d5ffc917142266fabf9 either, so I was wondering if work was still being
The upstream coreboot repository doesn't have these two commits. What source tree are you using? OptiPlex 7010 is still on gerrit https://review.coreboot.org/c/coreboot/+/25095.
done to port coreboot to the OptiPlex 7010, given its stock firmware doesn’t really work that great (I'd be happy to elaborate), even at revision A29, so I wanted to replace it with coreboot.
Thanks.
On 12/24/18 8:05 PM, Kumonie Williams wrote:
Hi Kumonie,
Hello there, I have a question regarding coreboot.
I was wondering if work was still being done to port coreboot to the Dell OptiPlex 7010. I was looking at commit 882d3c3574cc24f1bcf16b71c5090cc71ef725a6, but it seems the board didn’t boot at that stage in time. I have also not found much information regarding 4f19f4a7ebe7783830343d5ffc917142266fabf9 either, so I was wondering if work was still being done to port coreboot to the OptiPlex 7010, given its stock firmware doesn’t really work that great (I'd be happy to elaborate), even at revision A29, so I wanted to replace it with coreboot.
In 3mdeb we have couple of those and definitely coreboot enabling is on our roadmap. Is there any way you can support that effort (eg. coding, testing, sponsoring) ? This would definitely rise priority of that work.
Best Regards,
Hello, I would be more than willing to help test coreboot for the Dell OptiPlex 7010, however, I cannot provide assistance for much else at this time. Though, I do have a question I was hoping you'd be able to answer: The Dell OptiPlex 7010 has a service mode jumper, and, from my understanding, two ROM chips for two firmware images, the primary one used when the service mode jumper is not set, and the secondary one used when the service mode jumper has been set, with an immutable firmware image. My question is, given I only have one PC at the moment, my OptiPlex 7010, if I, say, flash a coreboot image that won't boot, would it be possible for me to simply set the service mode jumper from that point to safely use the second ROM chip? If so, it would make testing much easier. Thanks.
On Thu, Dec 27, 2018 at 5:06 PM Piotr Król piotr.krol@3mdeb.com wrote:
On 12/24/18 8:05 PM, Kumonie Williams wrote:
Hi Kumonie,
Hello there, I have a question regarding coreboot.
I was wondering if work was still being done to port coreboot to the Dell OptiPlex 7010. I was looking at commit 882d3c3574cc24f1bcf16b71c5090cc71ef725a6, but it seems the board didn’t boot at that stage in time. I have also not found much information regarding 4f19f4a7ebe7783830343d5ffc917142266fabf9 either, so I was wondering if work was still being done to port coreboot to the OptiPlex 7010, given its stock firmware doesn’t really work that great (I'd be happy to elaborate), even at revision A29, so I wanted to replace it with coreboot.
In 3mdeb we have couple of those and definitely coreboot enabling is on our roadmap. Is there any way you can support that effort (eg. coding, testing, sponsoring) ? This would definitely rise priority of that work.
Best Regards,
Piotr Król Embedded Systems Consultant https://3mdeb.com | @3mdeb_com _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
On 2018-12-29 10:39 a.m., Kumonie Williams wrote:
...
Though, I do have a question I was hoping you'd be able to answer: The Dell OptiPlex 7010 has a service mode jumper, and, from my understanding, two ROM chips for two firmware images, the primary one used when the service mode jumper is not set, and the secondary one used when the service mode jumper has been set, with an immutable firmware image. My question is, given I only have one PC at the moment, my OptiPlex 7010, if I, say, flash a coreboot image that won't boot, would it be possible for me to simply set the service mode jumper from that point to safely use the second ROM chip? If so, it would make testing much easier.
FYI, I have a 7010 that I bricked doing a Dell firmware update. The jumper didn't help me recover (yet?). I have one other that updated successfully.
I did notice that Linux failed to set a hi-res text mode properly, there was a kernel error message, and Linux thought there were more lines than actually got displayed... you could work on a "hidden" part of the screen below the monitor! That was the motivation for the firmware upgrade. If anyone has a fix for either issue, let me know.
Regards,
Jeremy
Thanks, I'll keep that in mind.
On Sat, Dec 29, 2018 at 9:47 AM Jeremy Jackson jerj@coplanar.net wrote:
On 2018-12-29 10:39 a.m., Kumonie Williams wrote:
...
Though, I do have a question I was hoping you'd be able to answer: The Dell OptiPlex 7010 has a service mode jumper, and, from my understanding, two ROM chips for two firmware images, the primary one used when the service mode jumper is not set, and the secondary one used when the service mode jumper has been set, with an immutable firmware image. My question is, given I only have one PC at the moment, my OptiPlex 7010, if I, say, flash a coreboot image that won't boot, would it be possible for me to simply set the service mode jumper from that point to safely use the second ROM chip? If so, it would make testing much easier.
FYI, I have a 7010 that I bricked doing a Dell firmware update. The jumper didn't help me recover (yet?). I have one other that updated successfully.
I did notice that Linux failed to set a hi-res text mode properly, there was a kernel error message, and Linux thought there were more lines than actually got displayed... you could work on a "hidden" part of the screen below the monitor! That was the motivation for the firmware upgrade. If anyone has a fix for either issue, let me know.
Regards,
Jeremy _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 12/29/18 4:47 PM, Jeremy Jackson wrote:
On 2018-12-29 10:39 a.m., Kumonie Williams wrote:
Hi Kumonie, Jeremy, adding Paul and Lynxis to CC as they were initial contributors of change s.
...
Though, I do have a question I was hoping you'd be able to answer: The Dell OptiPlex 7010 has a service mode jumper, and, from my understanding, two ROM chips for two firmware images, the primary one used when the service mode jumper is not set, and the secondary one used when the service mode jumper has been set, with an immutable firmware image. My question is, given I only have one PC at the moment, my OptiPlex 7010, if I, say, flash a coreboot image that won't boot, would it be possible for me to simply set the service mode jumper from that point to safely use the second ROM chip? If so, it would make testing much easier.
FYI, I have a 7010 that I bricked doing a Dell firmware update. The jumper didn't help me recover (yet?). I have one other that updated successfully.
I'm not sure about what jumper you talking. There are 2 close to BIOS chips RTCRST and PSWD - neither would help directly in recover form bric k.
I took a picture of 2 chips [1][2]. First seems to be SPI which contain BIOS and second I would say is storage for Dell bloatware that can run various hardware tests and display useless messages [3]. I will insepct SOIC8 later today, but SOIC16 requires special clip which I don't have at this point.
@Paul,Lynxis, if you flashed anything on those devices please let me know if there is any special treatment.
Apparently [1] seems to be MX25L3206E [4] - which is well supported by flashrom. Second seems to MX25L6406E [5] - I wonder how much of that we will need - it would be great to have additional 8MB of space.
I hope to take a look at it today night - will let you know about the progress.
[1] https://www.instagram.com/p/Br-p_2klRVL/?utm_source=ig_web_button_share_ sheet [2] https://www.instagram.com/p/Br-pt8jFX5Y/?utm_source=ig_web_button_share_ sheet [3] https://twitter.com/pietrushnic/status/1071384206603939843 [4] https://www.netcheif.com/Reviews/PLA5405/PDF/MX25L3206E.pdf [5] http://www.macronix.com/Lists/Datasheet/Attachments/7370/MX25L6406E,%203 V,%2064Mb,%20v1.9.pdf
Best Regards, - -- Piotr Król Embedded Systems Consultant https://3mdeb.com | @3mdeb_com
Hello, Upon further inspection, I cannot find any reference to the SERVICE_MODE jumper on Dell's website, only the two you mentioned, RTCRST and PSWD. It appears it may only be present on the mid tower form factor model of the Dell OptiPlex 7010, on which, it is directly under the PCI-e x16 (wired as x4) slot, to the left of INT_USB. A photo with the jumper circled in yellow has been made available for clarity here: https://imgur.com/a/Bn0yuin I heard from a post on a public forum ( https://www.bios-mods.com/forum/Thread-PSA-Dell-Service-Mode-jumper-on-Optip...) that the service mode jumper would allow you to use an "auxiliary BIOS" in case the "BIOS flash" (assumed they meant the chip with the firmware on it) was damaged, however, after Jeremy's comment on the matter, I believe either that post was incorrect, or the "auxiliary" BIOS is on a different region of the same chip.
On Sat, Dec 29, 2018 at 11:35 AM Piotr Król piotr.krol@3mdeb.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 12/29/18 4:47 PM, Jeremy Jackson wrote:
On 2018-12-29 10:39 a.m., Kumonie Williams wrote:
Hi Kumonie, Jeremy, adding Paul and Lynxis to CC as they were initial contributors of change s.
...
Though, I do have a question I was hoping you'd be able to answer: The Dell OptiPlex 7010 has a service mode jumper, and, from my understanding, two ROM chips for two firmware images, the primary one used when the service mode jumper is not set, and the secondary one used when the service mode jumper has been set, with an immutable firmware image. My question is, given I only have one PC at the moment, my OptiPlex 7010, if I, say, flash a coreboot image that won't boot, would it be possible for me to simply set the service mode jumper from that point to safely use the second ROM chip? If so, it would make testing much easier.
FYI, I have a 7010 that I bricked doing a Dell firmware update. The jumper didn't help me recover (yet?). I have one other that updated successfully.
I'm not sure about what jumper you talking. There are 2 close to BIOS chips RTCRST and PSWD - neither would help directly in recover form bric k.
I took a picture of 2 chips [1][2]. First seems to be SPI which contain BIOS and second I would say is storage for Dell bloatware that can run various hardware tests and display useless messages [3]. I will insepct SOIC8 later today, but SOIC16 requires special clip which I don't have at this point.
@Paul,Lynxis, if you flashed anything on those devices please let me know if there is any special treatment.
Apparently [1] seems to be MX25L3206E [4] - which is well supported by flashrom. Second seems to MX25L6406E [5] - I wonder how much of that we will need - it would be great to have additional 8MB of space.
I hope to take a look at it today night - will let you know about the progress.
[1] https://www.instagram.com/p/Br-p_2klRVL/?utm_source=ig_web_button_share_ sheet [2] https://www.instagram.com/p/Br-pt8jFX5Y/?utm_source=ig_web_button_share_ sheet [3] https://twitter.com/pietrushnic/status/1071384206603939843 [4] https://www.netcheif.com/Reviews/PLA5405/PDF/MX25L3206E.pdf [5] http://www.macronix.com/Lists/Datasheet/Attachments/7370/MX25L6406E,%203 V,%2064Mb,%20v1.9.pdf http://www.macronix.com/Lists/Datasheet/Attachments/7370/MX25L6406E,%203V,%2064Mb,%20v1.9.pdf
Best Regards,
Piotr Król Embedded Systems Consultant https://3mdeb.com | @3mdeb_com -----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE4DCbLYWmfoRjKeNLsu5x6WeqnkwFAlwnsAkACgkQsu5x6Weq nkzcjhAAjqojKNISVasyIGSDqTLN8rCaWudrSz6+XdoN5u0ZmnbfFj72/rDn1wgu Tm1wJvmb6QYSi8gbsyIEmhRFH15DJwicWE02bSbY6uzKJzOas4LvxUV7n5XD1zJs LOjPhdJur97TOmw2iLsF3993bjQQoYqg/8iaT9aenb5bDJkocuGAwVVmrXihabos TVPBDv1lMw4jSO6/ZQyAl8JZXGIktjGiPE3X4fFJHiar8uykjBcAzgr6K6TYP+fp s0RjDnmpxet2WpJowbUiE+UEeletHy/HWSRbtTXhSWEiMFBeBcMCGsklHRqr3mSr SqiklexiaKAXHz4EMtWJ56FR66o4rOCQUOBcPGiqJi3dOvm/4bTagXA1yCrgSprl ojGcu4AdHm8NeXgz7JVh8HrR3VkM31L9iD5/xYmdD0KD1d0S73OkAw08hskYUMph LxwP9o5ITHG2gKc8OtC4o5dI5irdBmdF7gHxKjvl+KMr0LBx/4dQAJl+iFl5v/u3 SNl88WvjwQHDygLlkbBEGUNIaXexVeL6FgML1tqRIxN1GcETL3P5xPxSzbTi71RY bkYP+vD2R7nG/UuW5AKaJdM41Gc4m22xHHyFz9bjVdQXolBQE0eAQYBdaFjj57iq ljzk4HIHjirpBfaATZBFUid20eT3AMwL/SalMsi7mqJucrTIZlI= =ruqN -----END PGP SIGNATURE----- _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
On 12/30/18 4:22 AM, Kumonie Williams wrote:
Hello,
Hi Kumonie,
Upon further inspection, I cannot find any reference to the SERVICE_MODE jumper on Dell's website, only the two you mentioned, RTCRST and PSWD. It appears it may only be present on the mid tower form factor model of the Dell OptiPlex 7010, on which, it is directly under the PCI-e x16 (wired as x4) slot, to the left of INT_USB. A photo with the jumper circled in yellow has been made available for clarity here: https://imgur.com/a/Bn0yuin
My board definitely looks different in area of SPI flashes. It seems like Dell OptiPlex 7010 had various little bit different designs - service mode jumper [1] and different PCB layout around SPI flashes [2].
There is seem to be different revisions of this mainboard.
I heard from a post on a public forum (https://www.bios-mods.com/forum/Thread-PSA-Dell-Service-Mode-jumper-on-Optip...) that the service mode jumper would allow you to use an "auxiliary BIOS" in case the "BIOS flash" (assumed they meant the chip with the firmware on it) was damaged, however, after Jeremy's comment on the matter, I believe either that post was incorrect, or the "auxiliary" BIOS is on a different region of the same chip.
It looks like much better explanation is on win-raid forum [3], but thread is pretty long and I didn't digest all information there.
I'm still looks for advise how this SPI was flashed, I suspect internal programmer since both paths on gerrit have 12MB and SPI1_1 has just 4MB. Also it looks like doesn't contain full BIOS but just part of it. For those interested in helping binary from SPI1_1 [4].
[1] https://www.instagram.com/p/BsA6eeQFfaw/?utm_source=ig_web_button_share_shee... [2] https://www.instagram.com/p/BsA7zX3FxzT/?utm_source=ig_web_button_share_shee... [3] https://www.win-raid.com/t1053f39-Optiplex-and-VPro-AMT-ME.html#msg18356 [4] https://cloud.3mdeb.com/index.php/s/XxyRfeKRxWNTJ7P
Best Regards,
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi all, after playing little bit I found correct combination that gives ability to read whole 12MB - binary is here [1]. Couple things that people have to know (probably should be contributed to docs): 1. enable SERVICE_MODE (by shorting using jumper) - this unlocks flash descriptor 2. if you want to read in Linux (Debian in my case) pass iomem=relaxed during boot - otherwise accessing /dev/mem give operation not permitted
This mainboard is little bit weird since bios region is spread across 2 SPI chips. Layout: 00000000:00000fff fd 00600000:00bfffff bios 00005000:005fffff me 00001000:00004fff gbe
It looks like there is no way to proceed without second Pomona clip for SOIC16. Luckily SPI debug console compiled in without problems after rebasing Paul's patches. I will continue reporting my experience on gerrit [2] - when it will get back since it has problems now.
[1] https://cloud.3mdeb.com/index.php/s/DJxMQ6YFeee4J3Q [2] https://review.coreboot.org/c/coreboot/+/25095
Best Regards, - -- Piotr Król Embedded Systems Consultant https://3mdeb.com | @3mdeb_com
-
Iru Cai -
Jeremy Jackson -
Kumonie Williams -
Piotr Król