Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apu4_v4.6.9.rom gives motherboard mismatch on apu4. #96

Open
michaelprice opened this Issue Jun 5, 2018 · 8 comments

Comments

Projects
None yet
4 participants
@michaelprice
Copy link

michaelprice commented Jun 5, 2018

http://pcengines.ch/file/apu4_v4.6.9.rom.tar.gz gives a motherboard mismatch warning when attempting to flash to an apu4 currently running 4.6.4.

Is this a known issue and a force is ok or am I missing something important?

@DennisEdlund

This comment has been minimized.

Copy link

DennisEdlund commented Jun 5, 2018

I think there is a config error in a string of the build of the apu4 that you already have in the board that gives a reply of apu2 to the flashrom.
For me this worked:
flashrom -w apu4_v4.6.9.rom -p internal:boardmismatch=force

@michaelprice

This comment has been minimized.

Copy link
Author

michaelprice commented Jun 6, 2018

Found some courage and went ahead and forced it. Went well. Used the sysutils/flashrom port in OpenBSD rather than booting tinycore linux.

@pietrushnic pietrushnic self-assigned this Jun 7, 2018

@pietrushnic

This comment has been minimized.

Copy link
Member

pietrushnic commented Jun 7, 2018

@michaelprice I'm sorry I didn't get back to you. What is your opinion would be the best place to inform users about this problem? We see this kind of issues repeat itself all the time.

@DennisEdlund

This comment has been minimized.

Copy link

DennisEdlund commented Jun 7, 2018

@pietrushnic Sorry to cut in but if there could be an info/doc page for APU2, APU3 & APU4 individually regarding specific info about that board and just a link on each page that pointed to a general page about common issues and solutions?
About this specific issue, I think I saw in the bootrom build code a string for the APU4 that said hardware idstring=apu2.

@pietrushnic

This comment has been minimized.

Copy link
Member

pietrushnic commented Jun 7, 2018

@DennisEdlund we think about couple things:

  1. Feature set website with test results, known issues and tracking ids here
  2. apu2/3/4/5 are not that specific to have separate pages I think, btw we have pcengines.github.io which we can extend

Any community input is welcome, so "cut in" is fine :)

@michaelprice

This comment has been minimized.

Copy link
Author

michaelprice commented Jun 7, 2018

I would have noticed a comment on this issue were it on the wiki or the github.io page where the newer firmwares are linked.

Another thing I think would be helpful is a reference to the md5 checksums of the firmwares on the github.io page especially since the download links aren’t https.

@DennisEdlund

This comment has been minimized.

Copy link

DennisEdlund commented Jun 7, 2018

I was just thinking about this apu2-document subpage.
There would be ground for the setup of a apu3 & apu4 page, where you could get specific help for the boards or if there would be a named page for all boards.
Then you now where to address issues and find info for your board like links for specific devices, drivers packages and builds.

@miczyg1

This comment has been minimized.

Copy link
Contributor

miczyg1 commented Jun 14, 2018

@michaelprice the problem with board mismatch is related to wrong SMBIOS table entries. In v4.6.7 we have switched to short names i.e. PC Engines apu4 -> apu4 for partnumber entry. This is correct form which should be used. The information about it was published here: https://pcengines.github.io/
These wrong entries caused certain modules specific for apu not being loaded on LEDE or OpenWrt etc.
flashrom detects mainboard by reading the partnumber, so if it is different in the system and coreboot image, it yields warning.

Adding -p internal:boardmismatch=force will let You flash the BIOS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.