Reset from post BDS pahse to PEI phase

Reset from post BDS pahse to PEI phase

[Amit kumar]

Hi ,
I have been facing some problem with blockIO reads even after reconnect and update map. when i try to do dblk on some of my blocks it returns with EFI_INVALID_PARAMETER. 
Is there a way to reinitialize the EFI platform from post bds phase or post dxe phase without putting the board in power-off mode( like in the case of shell reset command or system restart). 

Thanks and Regards 
Amit 

Re: Reset from post BDS pahse to PEI phase

[Andrew Fish]

> On Mar 28, 2017, at 5:23 AM, Amit kumar <akamit91@hotmail.com> wrote:
> 
> 
> Hi ,
> I have been facing some problem with blockIO reads even after reconnect and update map. when i try to do dblk on some of my blocks it returns with EFI_INVALID_PARAMETER. 
> Is there a way to reinitialize the EFI platform from post bds phase or post dxe phase without putting the board in power-off mode( like in the case of shell reset command or system restart). 
> 

Amit,

If you look in the UEFI Spec you will see there is a Runtime Service called ResetSystem(). It supports different reset types, but it is up the platform to define what they are. For example a EfiWarmReset could end up being the same as EfiResetCold in a given implementation. I would assume the shell reset command maps directly into this call, so you can get background from reading the spec. on options to the shell reset command. 

I'd recommend looking in the UEFI Spec for the Block IO Protocol function definitions as the define a standardized set of return codes. 

For example ReadBlocks() EFI_INVALID_PARAMETER implies:
The read request contains LBAs that are not valid, or the buffer is not on proper alignment.

The information used by these checks comes from the Block IO protocol Media data (EFI_BLOCK_IO_MEDIA). EFI_BLOCK_IO_MEDIA.IoAlign would define buffer alignment requirements for the call, and  EFI_BLOCK_IO_MEDIA.LastBlock should define the valid LBA range. 

Maybe there is a strange alignment requirement and there is a bug in the Shell? Maybe the driver is not reporting a proper LastBlock?


Thanks,

Andrew Fish

> Thanks and Regards 
> Amit 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel