-
Notifications
You must be signed in to change notification settings - Fork 0
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
Cannot boot MSI PRO Z690-A DDR5 after flashing v1.1.1 Dasharo firmware on a platform with v1.1.3 #793
Comments
@miczyg1 any idea what we could do to debug this? |
I guess, we need to flash a debug builds and see what happens on serial port... |
@miczyg1 do we have any or can you provide one? I will be working on MSI with osfv in next few days so I can check that |
@miczyg1 this is what I got https://paste.dasharo.com/?10c9291f9421ef77#DzYmFooRznUdgPjaV5Zy11wPFgunB32uKZLESkm7GfVy It looks like it tried to start three times and then gave up |
It looks like it restarts in the memory initialization in FSP... It will require some deeper investigation. Not sure though what causes it... |
@TomaszAIR what are the intervals between the restarts? Does the board do a power cycle? |
@miczyg1 ~126 seconds between attempts, logs with timestamps https://paste.dasharo.com/?9c8408a7e19a112a#Az5Zs6KMX2t7yMEwn98b5Ad6fMN3udYqyQ15FjMLmxma
I think it does, I can spot fan going down for a moment and then starting to work once again. |
CPU: 13th Gen Intel(R) Core(TM) i5-13600K 3.50GHz 1.1.1 is not intended to POST with Raptor Lake. Actually. the idea was that DTS should NOT allow you to flash 1.1.1 if there is a Raptor Lake installed because you will brick. |
@miczyg1 so it looks like we changed CPU in our lab for that platform? I would suspect that we did test v1.1.1 with DDR5 on some configuration.
@zirblazer I think that is still in DTS and it does not allow to flash with scripts. But in my case I flashed from the terminal using |
@zirblazer is right... We swapped CPU at a later time. V1.1.1 does not support 13th gen yet, that is why we have added a check for v1.1.1: #440 So basically going back to v1.1.1 with a CPU newer than 12th gen is forbidden |
1.2.21 just helpfully flashed 1.1.1 on my Z690-A with 13900K. Not sure if the check wasn't added yet or didn't trigger. Was a fully automated flash from DTS, I had entered my DES credentials but was receiving a network error on attempting to flash DES builds, attempted the community build to troubleshoot, it proceeded to flash and reboot. Bricked board till my CH431A arrives. |
It was fixed on the branch, but not part of a release under https://github.com/Dasharo/meta-dts/releases yet. EDIT: This check seems to be a part of this v1.2.21 already: https://github.com/Dasharo/meta-dts/releases/tag/v1.2.21. Perhaps the 13900K is not properly detected here? Can you please provide On our side, we have 13600k and 14700k, so should be verified on these. Can have it double-checked tomorrow. |
The check as written returns 1, but it doesn't seem to trigger the -ne 0 eval immediately after. Not sure why, haven't dug into it, as I'm no longer using DTS. I can burn a flash and test in DTS if that's needed, maybe add some checkpoints to see where it fails. Would like to avoid flashing 1.1.1 again if possible, my CH341A setup is annoying to attach. I'm able to build, flash, and run 1.1.2 and 1.1.3 without issue. |
Component
Dasharo firmware
Device
MSI Pro Z690-A
Dasharo version
v1.1.1
Dasharo Tools Suite version
v1.2.21
Brief summary
Platform does not boot after flashing bios region of v1.1.1 Dasharo firmware
How reproducible
Every time
How to reproduce
Flash Dasharo firmware v1.1.3 on MSI PRO Z690-A DDR5 using all regions
Flash bios region of Dasharo firmware v1.1.1 on MSI PRO Z690-A DDR5
Expected behavior
Platform works, can see Dasharo image at boot on connected display
Actual behavior
Nothing on display. CPU fan starts, also see some leds on ethernet port
Screenshots
No response
Additional context
No response
Solutions you've tried
Internal flash with DTS and external flash using RTE
Removing CMOS battery after flashing v1.1.1 to reset any settings
The text was updated successfully, but these errors were encountered: