@Rebecca Cran yeah, when I said "not opened it yet", I meant the EEPROM socket :-)
@Rebecca Cran yeah, when I said "not opened it yet", I meant the EEPROM socket :-)
@Willy Tarreau Very helpfully, the EEPROMs on the carrier board are all socketed so you can either use an adapter to flash them in-place, or remove them and flash them outside the case.
@Rebecca Cran thanks for the info. We'll see, for now I don't have any DB40-to-FPC adapter. I understood that the upcoming 2.09 MMC code will support JP27-29 to allow to load EDK2 from the carrier ...
@Willy Tarreau @Jiaheng Wang was able to create an adapter to connect from a SPI programmer to the DB40 connector on the module, which might be useful?
Just to share some updates, I could reflash the MMC from the default image ipmitool as documented somewhere else in the wiki. So my understanding is that after the next update, it will be able to l...
Thank you! The problem I'm facing is: how will I be supposed to flash this given that I can't get past the BIOS anymore ? I do have a buspirate board at home with the SPI adapter for SOP-8, and hav...
A new MMC will be released this week. May be you can get it from staff in advance. The new 2.09 MMC will let you to use BIOS on carrier by setting JP27-29, maybe that can solve your problem.
Dear @Willy Tarreau, We took it down for a few days to reconstruct the repo. Now, we've opened it for you. Sorry for the inconvenience. Please downgrade your BIOS version to 2.04.100.10 which is th...
@Willy Tarreau The edk2_aadp repo was temporarily removed because they found problems where older hardware revisions could be bricked. They're updating the documentation and will make it visible ag...
@Willy Tarreau Apparently there will be a new MMC release coming soon that fixes being able to boot from the EEPROM on the carrier. From a different thread: > There will also be an update for t...
@Willy Tarreau Yeah, it's very unfortunate. I didn't think 2.09.100 was released yet. I've been running 2.04.100.10 and 2.04.100.11. Maybe a build of 2.09.100 was mistakenly created?
@Willy Tarreau responding to myself, it's indicated in this thread that the firmware images have been removed (!): https://www.ipi.wiki/community/forum/topic/119680/edk2-github-repo-disappear...
Likewise, I couldn't find any configuration that would present me a different version from the last I flashed, so I don't know if both copies were flashed at once last time or if the jumpers are ig...
Sadly the message says it all. That's what I'm getting after the "Press Escape for boot options" in EDK2 if I don't press anything. If I press Escape, then the machine hangs. I tried the following...
Btw, the edk2_aadp github repository above doesn't exist anymore. There are other ones, all older than 2.09.100, so I'm not sure ADLINK is uploading firmwares on github anymore.
@Rebecca Cran I'm confused, the image from November I found in the download section for AADK is a 2.04.100 while I'm on 2.09.100. Maybe there's a different download link that I didn't find ? Thanks!
@Rebecca Cran Hi Rebecca! Much appreciated, thank you. I'm willing to give it a try. Unfortunately the machine is refusing to boot again for an unknown reason ("synchronous exception at xxx"...
Hi Rebecca, MMC on module connect to the SMPro through pre-defined I2C bus. leverage it from Ampere Altra's reference design. it is capable of reading information. for example, by usi...
Yes that would work if you flash the SPI flash on the module through DB40 connector with a Dediprog. However if you would like to have a backup / recovery on the carrier SPI flash, that is p...
@Ruler of COM The 13MB version can also be burned via an eeprom programmer by specifying the offset to flash it at. e.g. dpcmd --spi-clk 0 -v -a 0x400000 -u edk2_fw.bin