Re: [U-Boot] Building u-boot.rom for Minnowboard
Hi Saket,
On Sun, May 31, 2015 at 2:19 PM, Saket Sinha saket.sinha89@gmail.com wrote:
Hi Bin,
If you can have a look at this issue.
I am currently stuck on this issue with u-boot.rom not giving me any output on the serial.
When I am flashing MinnowBoard.MAX.X64.080.D01.bin I get the all the UEFI prompt and the booting messages but when I flash u-boot.rom, I do not get anything on the serial port.
Let me know if I am missing out something in the build process of u-boot.rom
While running the following commands, I seem to get the errors-
c) ./tools/ifdtool -x BayleyBay/SPI.bin root@saket-HP-PC:# /u-boot-x86/tools/ifdtool -x BayleyBay/SPI.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00fff000 - 00000fff (unused) Error while writing: Bad address Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
AND
a)./tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin root@saket-PC:# /u-boot-x86/tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00000000 - 00000fff Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
These may be the reason for the u-boot.rom not getting built properly.
I have described the entire build process for u-boot.rom int my previous mail below -
I am building u-boot.rom for MinnowboardMax as per the steps mentioned in the README.x86.
- Downloading BAY_TRAIL_FSP_KIT_GOLD3.tgz
a) copying BAYTRAIL_FSP_GOLD_003_16-SEP-2014.fd as board/intel/minnowmax/fsp.bin
b) copying Vga.dat as board/intel/minnowmax/vga.bin
c) ./tools/ifdtool -x BayleyBay/SPI.bin
From the generted files, copying flashregion_2_intel_me.bin as board/intel/minnowmax/me.bin
Though the o/p files are generated, I get the following error after this command - root@saket-HP-PC:# /u-boot-x86/tools/ifdtool -x BayleyBay/SPI.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00fff000 - 00000fff (unused) Error while writing: Bad address Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
I've seen this error before. It is a bug of the ifdtool, but I think it can be ignored. I have a patch sent out. Please check http://patchwork.ozlabs.org/patch/478590/
- Downloading 2014-WW42.4-MinnowBoardMax.73-64-bit.bin_Release.zip
a)./tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin From the generted files, copying flashregion_0_flashdescriptor.bin as board/intel/minnowmax/descriptor.bin
Though the o/p files are generated, I get the following error after this command - root@saket-PC:# /u-boot-x86/tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00000000 - 00000fff Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
- Building u-boot.rom
export BUILD_ROM=y make minnowmax_defconfig make all
Looks that your instructions are correct according to README.x86
- Flashing u-boot.rom to Minnowmax by desiprog sf100
./flashrom -p dediprog -w u-boot.rom
Can you confirm that you have setup the flashrom tool correctly? I don't use flashrom on Linux as I normally do the SPI flash programming on a Windows machine. Can you dump the whole SPI flash image back after you program the u-boot.rom and compare the dumped file with the u-boot.rom you generated to see whether they are exactly the same?
- Now when I am powering Minnowmax and collecting the output on serial -
Nothing appears.
Kindly let me know, if I am missing something here.
Sorry but I don't have a MinnowMax board here, so cannot try it on my side.
Regards, Bin
Hi Saket,
On May 31, 2015 1:08 AM, "Bin Meng" bmeng.cn@gmail.com wrote:
Hi Saket,
On Sun, May 31, 2015 at 2:19 PM, Saket Sinha saket.sinha89@gmail.com
wrote:
Hi Bin,
If you can have a look at this issue.
I am currently stuck on this issue with u-boot.rom not giving me any output on the serial.
When I am flashing MinnowBoard.MAX.X64.080.D01.bin I get the all the UEFI prompt and the booting messages but when I flash u-boot.rom, I do not get anything on the serial port.
Let me know if I am missing out something in the build process of
u-boot.rom
While running the following commands, I seem to get the errors-
c) ./tools/ifdtool -x BayleyBay/SPI.bin root@saket-HP-PC:# /u-boot-x86/tools/ifdtool -x BayleyBay/SPI.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00fff000 - 00000fff (unused) Error while writing: Bad address Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
AND
a)./tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin root@saket-PC:# /u-boot-x86/tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00000000 - 00000fff Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
These may be the reason for the u-boot.rom not getting built properly.
I have described the entire build process for u-boot.rom int my previous mail below -
I am building u-boot.rom for MinnowboardMax as per the steps mentioned in the README.x86.
- Downloading BAY_TRAIL_FSP_KIT_GOLD3.tgz
a) copying BAYTRAIL_FSP_GOLD_003_16-SEP-2014.fd as board/intel/minnowmax/fsp.bin
b) copying Vga.dat as board/intel/minnowmax/vga.bin
c) ./tools/ifdtool -x BayleyBay/SPI.bin
From the generted files, copying flashregion_2_intel_me.bin as board/intel/minnowmax/me.bin
Though the o/p files are generated, I get the following error after this command - root@saket-HP-PC:# /u-boot-x86/tools/ifdtool -x BayleyBay/SPI.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00fff000 - 00000fff (unused) Error while writing: Bad address Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
I've seen this error before. It is a bug of the ifdtool, but I think it can be ignored. I have a patch sent out. Please check http://patchwork.ozlabs.org/patch/478590/
- Downloading 2014-WW42.4-MinnowBoardMax.73-64-bit.bin_Release.zip
a)./tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin From the generted files, copying flashregion_0_flashdescriptor.bin as board/intel/minnowmax/descriptor.bin
Though the o/p files are generated, I get the following error after this command - root@saket-PC:# /u-boot-x86/tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00000000 - 00000fff Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
- Building u-boot.rom
export BUILD_ROM=y make minnowmax_defconfig make all
Looks that your instructions are correct according to README.x86
- Flashing u-boot.rom to Minnowmax by desiprog sf100
./flashrom -p dediprog -w u-boot.rom
Can you confirm that you have setup the flashrom tool correctly? I don't use flashrom on Linux as I normally do the SPI flash programming on a Windows machine. Can you dump the whole SPI flash image back after you program the u-boot.rom and compare the dumped file with the u-boot.rom you generated to see whether they are exactly the same?
- Now when I am powering Minnowmax and collecting the output on
serial -
Nothing appears.
Kindly let me know, if I am missing something here.
Sorry but I don't have a MinnowMax board here, so cannot try it on my
side.
I'm on holiday but should be able to try this on Monday or Tuesday.
Regards, Simon
Hi Bin,
Please find my response inline.
root@saket-HP-PC:# /u-boot-x86/tools/ifdtool -x BayleyBay/SPI.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00fff000 - 00000fff (unused) Error while writing: Bad address Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
a)./tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin From the generted files, copying flashregion_0_flashdescriptor.bin as board/intel/minnowmax/descriptor.bin
Though the o/p files are generated, I get the following error after this command - root@saket-PC:# /u-boot-x86/tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00000000 - 00000fff Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
I've seen this error before. It is a bug of the ifdtool, but I think it can be ignored. I have a patch sent out. Please check http://patchwork.ozlabs.org/patch/478590/
Your patch fixes the Error message but still I do not get any o/p on serial with the resulting u-boot.rom
- Flashing u-boot.rom to Minnowmax by desiprog sf100
./flashrom -p dediprog -w u-boot.rom
Can you confirm that you have setup the flashrom tool correctly? I don't use flashrom on Linux as I normally do the SPI flash programming on a Windows machine. Can you dump the whole SPI flash image back after you program the u-boot.rom and compare the dumped file with the u-boot.rom you generated to see whether they are exactly the same?
I only way I have dumped SPI flash has been through flashrom only. How else can I do it on Linux?
As of now I am trying to burn u-boot.rom with SPI programmer/software on Windows to check the sanity of my flashrom setup.
- Now when I am powering Minnowmax and collecting the output on serial
Nothing appears.
Kindly let me know, if I am missing something here.
Sorry but I don't have a MinnowMax board here, so cannot try it on my side.
I'm on holiday but should be able to try this on Monday or Tuesday.
Thanks Simon.
Regards, Saket Sinha
Hi Saket,
On 31 May 2015 at 22:55, Saket Sinha saket.sinha89@gmail.com wrote:
Hi Bin,
Please find my response inline.
root@saket-HP-PC:# /u-boot-x86/tools/ifdtool -x BayleyBay/SPI.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00fff000 - 00000fff (unused) Error while writing: Bad address Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
a)./tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin From the generted files, copying flashregion_0_flashdescriptor.bin as board/intel/minnowmax/descriptor.bin
Though the o/p files are generated, I get the following error after this command - root@saket-PC:# /u-boot-x86/tools/ifdtool -x MNW2MAX1.X64.0073.R02.1409160934.bin Flash Region 0 (Flash Descriptor): 00000000 - 00000fff Flash Region 1 (BIOS): 00500000 - 007fffff Flash Region 2 (Intel ME): 00001000 - 004fffff Flash Region 3 (GbE): 00000000 - 00000fff Flash Region 4 (Platform Data): 00fff000 - 00000fff (unused) Error while writing: Bad address
I've seen this error before. It is a bug of the ifdtool, but I think it can be ignored. I have a patch sent out. Please check http://patchwork.ozlabs.org/patch/478590/
Your patch fixes the Error message but still I do not get any o/p on serial with the resulting u-boot.rom
- Flashing u-boot.rom to Minnowmax by desiprog sf100
./flashrom -p dediprog -w u-boot.rom
Can you confirm that you have setup the flashrom tool correctly? I don't use flashrom on Linux as I normally do the SPI flash programming on a Windows machine. Can you dump the whole SPI flash image back after you program the u-boot.rom and compare the dumped file with the u-boot.rom you generated to see whether they are exactly the same?
I only way I have dumped SPI flash has been through flashrom only. How else can I do it on Linux?
As of now I am trying to burn u-boot.rom with SPI programmer/software on Windows to check the sanity of my flashrom setup.
- Now when I am powering Minnowmax and collecting the output on serial
Nothing appears.
Kindly let me know, if I am missing something here.
Sorry but I don't have a MinnowMax board here, so cannot try it on my side.
I'm on holiday but should be able to try this on Monday or Tuesday.
Thanks Simon.
It seems to boot OK for me. See details and download link below:
md5sum board/intel/minnowmax/*.bin ffda9a3b94df5b74323afb328d51e6b4 board/intel/minnowmax/descriptor.bin 69f65b9a580246291d20d08cbef9d7c5 board/intel/minnowmax/fsp.bin 894a97d371544ec21de9c3e8e1716c4b board/intel/minnowmax/me.bin a2588537da387da592a27219d56e9962 board/intel/minnowmax/vga.bin
md5sum b/minnowmax/u-boot.rom a0e48653fd7e5e91dda6064e7b5ddacb b/minnowmax/u-boot.rom
Download u-boot.rom from:
https://drive.google.com/file/d/0B7WYZbZ9zd-3eDFaNHpFN2JrcUE/view?usp=sharin...
(I use em100pro to download the image) sudo em100 -s -p LOW -d b/minnowmax/u-boot.rom -c W25Q64DW -r
U-Boot 2015.07-rc1-00408-g012681b (Jun 01 2015 - 09:20:06 -0600)
CPU: x86_64, vendor Intel, device 30673h DRAM: 2 GiB MMC: ValleyView SDHCI: 0, ValleyView SDHCI: 1 Using default environment
Video: 1280x1024x16 Model: Intel Minnowboard Max SCSI: SATA link 0 timeout. Target spinup took 0 ms. AHCI 0001.0300 32 slots 2 ports 3 Gbps 0x3 impl SATA mode flags: 64bit ncq stag pm led clo pio slum part sxs scanning bus for devices... Device 0: (1:0) Vendor: ATA Prod.: ADATA SP310 Rev: 5.2 Type: Hard Disk Capacity: 30533.8 MB = 29.8 GB (62533296 x 512) Found 1 device(s). Net: RTL8169#0 Warning: RTL8169#0 using MAC address from net device
Please can you check your binary blobs and send md5 sums?
Regards, Simon
Hi Simon,
- Now when I am powering Minnowmax and collecting the output on serial
Nothing appears.
It seems to boot OK for me. See details and download link below: Download u-boot.rom from: https://drive.google.com/file/d/0B7WYZbZ9zd-3eDFaNHpFN2JrcUE/view?usp=sharin...
With this image also, I do not get any output on my serial port(though two blue leds D1 & D2 are lighted up) which I run by "screen /dev/ttyUSB0 115200" using USB to Serial TTL Level sent to me by John.
When I flash MinnowBoard.MAX.X64.079.R01.bin instead of the u-boot.rom, I get all the UEFI outputs on the same setup.
Can you confirm that you have setup the flashrom tool correctly?
As of now I am trying to burn u-boot.rom with SPI programmer/software on Windows to check the sanity of my flashrom setup.
I have tried flashing both the u-boot.rom and MinnowBoard.MAX.X64.079.R01.bin with the Dediprog Engineering software on Windows with exactly same results for both the cases as with flashrom so atleast flashrom setup is correct.
Regards, Saket Sinha
+John
Hi Saket,
On 1 June 2015 at 13:45, Saket Sinha saket.sinha89@gmail.com wrote:
Hi Simon,
> 5. Now when I am powering Minnowmax and collecting the output on serial > Nothing appears. >
It seems to boot OK for me. See details and download link below: Download u-boot.rom from: https://drive.google.com/file/d/0B7WYZbZ9zd-3eDFaNHpFN2JrcUE/view?usp=sharin...
With this image also, I do not get any output on my serial port(though two blue leds D1 & D2 are lighted up) which I run by "screen /dev/ttyUSB0 115200" using USB to Serial TTL Level sent to me by John.
When I flash MinnowBoard.MAX.X64.079.R01.bin instead of the u-boot.rom, I get all the UEFI outputs on the same setup.
Can you confirm that you have setup the flashrom tool correctly?
As of now I am trying to burn u-boot.rom with SPI programmer/software on Windows to check the sanity of my flashrom setup.
I have tried flashing both the u-boot.rom and MinnowBoard.MAX.X64.079.R01.bin with the Dediprog Engineering software on Windows with exactly same results for both the cases as with flashrom so atleast flashrom setup is correct.
Yes. I'm not sure what to do here sorry. That image works for me. Is it possible that you have a different board variant to me? Is it the dual core one?
Regards, Simon
Shouldn't be an appreciable differences in the boards, how are you flashing it? Can you punt me a copy of the image so I can try it here and double check?
- John
On 06/01/2015 01:10 PM, Simon Glass wrote:
+John
Hi Saket,
On 1 June 2015 at 13:45, Saket Sinha saket.sinha89@gmail.com wrote:
Hi Simon,
>> 5. Now when I am powering Minnowmax and collecting the output on serial >> Nothing appears. >>
It seems to boot OK for me. See details and download link below: Download u-boot.rom from: https://drive.google.com/file/d/0B7WYZbZ9zd-3eDFaNHpFN2JrcUE/view?usp=sharin...
With this image also, I do not get any output on my serial port(though two blue leds D1 & D2 are lighted up) which I run by "screen /dev/ttyUSB0 115200" using USB to Serial TTL Level sent to me by John.
When I flash MinnowBoard.MAX.X64.079.R01.bin instead of the u-boot.rom, I get all the UEFI outputs on the same setup.
Can you confirm that you have setup the flashrom tool correctly?
As of now I am trying to burn u-boot.rom with SPI programmer/software on Windows to check the sanity of my flashrom setup.
I have tried flashing both the u-boot.rom and MinnowBoard.MAX.X64.079.R01.bin with the Dediprog Engineering software on Windows with exactly same results for both the cases as with flashrom so atleast flashrom setup is correct.
Yes. I'm not sure what to do here sorry. That image works for me. Is it possible that you have a different board variant to me? Is it the dual core one?
Regards, Simon
Hi John,
On Jun 1, 2015 3:21 PM, "John Hawley" john.hawley@intel.com wrote:
Shouldn't be an appreciable differences in the boards, how are you flashing it? Can you punt me a copy of the image so I can try it here and double check?
- John
Please see below for the drive link.
- Simon
On 06/01/2015 01:10 PM, Simon Glass wrote:
+John
Hi Saket,
On 1 June 2015 at 13:45, Saket Sinha saket.sinha89@gmail.com wrote:
Hi Simon,
>>> 5. Now when I am powering Minnowmax and collecting the output on
serial
>>> Nothing appears. >>>
It seems to boot OK for me. See details and download link below: Download u-boot.rom from:
https://drive.google.com/file/d/0B7WYZbZ9zd-3eDFaNHpFN2JrcUE/view?usp=sharin...
With this image also, I do not get any output on my serial port(though two blue leds D1 & D2 are lighted up) which I run by "screen /dev/ttyUSB0 115200" using USB to Serial TTL Level sent to me by John.
When I flash MinnowBoard.MAX.X64.079.R01.bin instead of the u-boot.rom, I get all the UEFI outputs on the same setup.
> > Can you confirm that you have setup the flashrom tool correctly?
As of now I am trying to burn u-boot.rom with SPI programmer/software on Windows to check the sanity of my flashrom setup.
I have tried flashing both the u-boot.rom and MinnowBoard.MAX.X64.079.R01.bin with the Dediprog Engineering software on Windows with exactly same results for both the cases as with flashrom so atleast flashrom setup is correct.
Yes. I'm not sure what to do here sorry. That image works for me. Is it possible that you have a different board variant to me? Is it the dual core one?
Regards, Simon
Are we assuming a serial port being 11520n8 on ttyS0 (I.E. the same port we normally use for early serial)?
- John
On 06/01/2015 02:27 PM, Simon Glass wrote:
Hi John,
On Jun 1, 2015 3:21 PM, "John Hawley" <john.hawley@intel.com mailto:john.hawley@intel.com> wrote:
Shouldn't be an appreciable differences in the boards, how are you flashing it? Can you punt me a copy of the image so I can try it here and double check?
- John
Please see below for the drive link.
- Simon
On 06/01/2015 01:10 PM, Simon Glass wrote:
+John
Hi Saket,
On 1 June 2015 at 13:45, Saket Sinha <saket.sinha89@gmail.com
mailto:saket.sinha89@gmail.com> wrote:
Hi Simon,
>>>> 5. Now when I am powering Minnowmax and collecting the output
on serial
>>>> Nothing appears. >>>>
It seems to boot OK for me. See details and download link below: Download u-boot.rom from:
https://drive.google.com/file/d/0B7WYZbZ9zd-3eDFaNHpFN2JrcUE/view?usp=sharin...
With this image also, I do not get any output on my serial port(though two blue leds D1 & D2 are lighted up) which I run by "screen /dev/ttyUSB0 115200" using USB to Serial TTL Level sent to me by John.
When I flash MinnowBoard.MAX.X64.079.R01.bin instead of the u-boot.rom, I get all the UEFI outputs on the same setup.
>> >> Can you confirm that you have setup the flashrom tool correctly?
As of now I am trying to burn u-boot.rom with SPI programmer/software on Windows to check the sanity of my flashrom setup.
I have tried flashing both the u-boot.rom and MinnowBoard.MAX.X64.079.R01.bin with the Dediprog Engineering software on Windows with exactly same results for both the cases as with flashrom so atleast flashrom setup is correct.
Yes. I'm not sure what to do here sorry. That image works for me. Is it possible that you have a different board variant to me? Is it the dual core one?
Regards, Simon
Hi John,
Are we assuming a serial port being 11520n8 on ttyS0 (I.E. the same port we normally use for early serial)?
I access my serial port through "screen /dev/ttyUSB0 115200" using USB to Serial TTL Level cable. When I flash MinnowBoard.MAX.X64.079.R01.bin, I get all the UEFI outputs but with u-boot.rom sent by Simon, I do not get any output with the same setup.
Shouldn't be an appreciable differences in the boards, how are you flashing it?
I have tried flashing both the u-boot.rom and MinnowBoard.MAX.X64.079.R01.bin with flashrom on Linux and the Dediprog Engineering software on Windows with exactly same results.
Regards, Saket Sinha
Hi John,
Can you punt me a copy of the image so I can try it here and double check?
Please see below for the drive link.
https://drive.google.com/file/d/0B7WYZbZ9zd-3eDFaNHpFN2JrcUE/view?usp=sharin...
Are you able to see any output with Simon's u-boot.rom shared above on the serial?
Regards, Saket Sinha
Hi Saket,
On 2 June 2015 at 09:44, Saket Sinha saket.sinha89@gmail.com wrote:
Hi John,
Can you punt me a copy of the image so I can try it here and double check?
Please see below for the drive link.
https://drive.google.com/file/d/0B7WYZbZ9zd-3eDFaNHpFN2JrcUE/view?usp=sharin...
Are you able to see any output with Simon's u-boot.rom shared above on the serial?
Also do you know which MinnowMAX board you have? I think there are two versions.
I might be able to create an image that prints out post_code() calls.
Will wait to hear from John.
Regards, Simon
Hi Simon,
Also do you know which MinnowMAX board you have? I think there are two versions.
The pcb does not speak of any particular versions.
I found there are two hardware revisions - http://www.elinux.org/Minnowboard:Hardware_Revisions#MinnowMax
But I would not be able to tell my minnowmax belongs to which revision without the Multimeter and other stuff which currently I am not possessing.
Moreover, the changes are not of the nature to have stopped the u-boot from booting.
I might be able to create an image that prints out post_code() calls.
That would be a real help.
Will wait to hear from John.
Same here.
Regards, Saket Sinha
Hi Saket,
On 2 June 2015 at 11:02, Saket Sinha saket.sinha89@gmail.com wrote:
Hi Simon,
Also do you know which MinnowMAX board you have? I think there are two versions.
The pcb does not speak of any particular versions.
I found there are two hardware revisions - http://www.elinux.org/Minnowboard:Hardware_Revisions#MinnowMax
But I would not be able to tell my minnowmax belongs to which revision without the Multimeter and other stuff which currently I am not possessing.
Moreover, the changes are not of the nature to have stopped the u-boot from booting.
I might be able to create an image that prints out post_code() calls.
That would be a real help.
Will wait to hear from John.
Same here.
I added a debug UART image here:
https://drive.google.com/folderview?id=0B7WYZbZ9zd-3flBfMEk3WHRSclJDWHFxOWlQ...
I'll send the patch to the mailing list soon so you can build it. It should output an 'a' character after setting up the FSP.
Are you able to progress by using qemu in the meantime?
Regards, Simon
Hi Simon,
I might be able to create an image that prints out post_code() calls.
I added a debug UART image here: https://drive.google.com/folderview?id=0B7WYZbZ9zd-3flBfMEk3WHRSclJDWHFxOWlQ...
The results are identical as that of previous image. I still get no output on serial. Tried flashing the image with both falshrom(Linux) and Dediprog software(Windows).
I even began to doubt my serial connection on Linux so switched to Teraterm on Windows but still no output on serial.
Are you able to progress by using qemu in the meantime?
Yes. My first approach was to extract the acpi tables from fw_cfg. That is failing for u-boot but works for coreboot. I have discussed this issue with Bin.
Now I am trying to write ACPI tables(i.e. builtin ACPI) for qemu-x86. This is case that should be generic and would be hit for minnowmax also.
Will wait to hear from John.
Just had a word with John.....he seems to get identical results as me for both the images that you shared. Would like to quote him -
"so my suspicion is that Simon is building the firmware with a slightly older FSP specifically an FSP that doesn't support the newer stepping on the CPU.
I just flashed the debug one on an A0 (ancient board obviously) and I get some output. I get nothing on my newer A2 w/ a D0 stepped CPU .
All that needs to happen is to use a newer FSP. The board you have I'm pretty sure is an A2 board with a D0 stepping cpu.
It's possible that Simon got his board long enough ago that he's got an A1 or A2 with a B3 stepping cpu I.E. that explains why it works for him, and not you.
I'm 99% sure that's the issue. try with FSP 3 gold."
I am now trying to build the u-boot.rom from FSP 3 gold and would let you know about the results ASAP.
Regards, Saket Sinha
Hi,
I'm 99% sure that's the issue. try with FSP 3 gold."
I am now trying to build the u-boot.rom from FSP 3 gold and would let you know about the results ASAP.
u-boot.rom prepared from FSP3-Gold dowmloaded from https://downloadcenter.intel.com/download/24496 doesn't work with the minnowmax I have.
Regards, Saket Sinha
Ok some more data points. I tested with the FSP3 Gold that Saket built, and it continues to work on the A0, but it continues to not work on the A2 D0 board I have. I'm guessing this is something between the steppings in the CPU and the FSP, but I'm not sure.
Adding Vincent to this, as I'm guessing there is something going on here with the interaction with the FSP (since it works on an A0 B3, but not an A2 D0)
- John
On 06/03/2015 01:24 PM, Saket Sinha wrote:
Hi,
I'm 99% sure that's the issue. try with FSP 3 gold."
I am now trying to build the u-boot.rom from FSP 3 gold and would let you know about the results ASAP.
u-boot.rom prepared from FSP3-Gold dowmloaded from https://downloadcenter.intel.com/download/24496 doesn't work with the minnowmax I have.
Regards, Saket Sinha
Hi,
On Thu, Jun 4, 2015 at 5:44 AM, John Hawley john.hawley@intel.com wrote:
Ok some more data points. I tested with the FSP3 Gold that Saket built, and it continues to work on the A0, but it continues to not work on the A2 D0 board I have. I'm guessing this is something between the steppings in the CPU and the FSP, but I'm not sure.
Adding Vincent to this, as I'm guessing there is something going on here with the interaction with the FSP (since it works on an A0 B3, but not an A2 D0)
- John
On 06/03/2015 01:24 PM, Saket Sinha wrote:
Hi,
I'm 99% sure that's the issue. try with FSP 3 gold."
I am now trying to build the u-boot.rom from FSP 3 gold and would let you know about the results ASAP.
u-boot.rom prepared from FSP3-Gold dowmloaded from https://downloadcenter.intel.com/download/24496 doesn't work with the minnowmax I have.
Regards, Saket Sinha
Given even with Simon's debug UART WIP patch, the A2 D0 board still has nothing output, I suspect that the FspTempRamInit() call failed due to the microcode loading. Could it be the problem that the microcode passed to the FSP is a little bit old that it does not support the D0 stepping. Can you try some newer version microcode to see if there is any luck?
Regards, Bin
Hi John,
On 3 June 2015 at 18:13, Bin Meng bmeng.cn@gmail.com wrote:
Hi,
On Thu, Jun 4, 2015 at 5:44 AM, John Hawley john.hawley@intel.com wrote:
Ok some more data points. I tested with the FSP3 Gold that Saket built, and it continues to work on the A0, but it continues to not work on the A2 D0 board I have. I'm guessing this is something between the steppings in the CPU and the FSP, but I'm not sure.
Adding Vincent to this, as I'm guessing there is something going on here with the interaction with the FSP (since it works on an A0 B3, but not an A2 D0)
- John
On 06/03/2015 01:24 PM, Saket Sinha wrote:
Hi,
I'm 99% sure that's the issue. try with FSP 3 gold."
I am now trying to build the u-boot.rom from FSP 3 gold and would let you know about the results ASAP.
u-boot.rom prepared from FSP3-Gold dowmloaded from https://downloadcenter.intel.com/download/24496 doesn't work with the minnowmax I have.
Regards, Saket Sinha
Given even with Simon's debug UART WIP patch, the A2 D0 board still has nothing output, I suspect that the FspTempRamInit() call failed due to the microcode loading. Could it be the problem that the microcode passed to the FSP is a little bit old that it does not support the D0 stepping. Can you try some newer version microcode to see if there is any luck?
I was using the Gold3 version. Is there a new microcode we could try?
Regards, Simon
Hi Saket,
On Thu, Jun 4, 2015 at 11:23 AM, Simon Glass sjg@chromium.org wrote:
Hi John,
On 3 June 2015 at 18:13, Bin Meng bmeng.cn@gmail.com wrote:
Hi,
On Thu, Jun 4, 2015 at 5:44 AM, John Hawley john.hawley@intel.com wrote:
Ok some more data points. I tested with the FSP3 Gold that Saket built, and it continues to work on the A0, but it continues to not work on the A2 D0 board I have. I'm guessing this is something between the steppings in the CPU and the FSP, but I'm not sure.
Adding Vincent to this, as I'm guessing there is something going on here with the interaction with the FSP (since it works on an A0 B3, but not an A2 D0)
- John
On 06/03/2015 01:24 PM, Saket Sinha wrote:
Hi,
I'm 99% sure that's the issue. try with FSP 3 gold."
I am now trying to build the u-boot.rom from FSP 3 gold and would let you know about the results ASAP.
u-boot.rom prepared from FSP3-Gold dowmloaded from https://downloadcenter.intel.com/download/24496 doesn't work with the minnowmax I have.
Regards, Saket Sinha
Given even with Simon's debug UART WIP patch, the A2 D0 board still has nothing output, I suspect that the FspTempRamInit() call failed due to the microcode loading. Could it be the problem that the microcode passed to the FSP is a little bit old that it does not support the D0 stepping. Can you try some newer version microcode to see if there is any luck?
I was using the Gold3 version. Is there a new microcode we could try?
I've created two patches to include a D0 stepping microcode for BayTrail-I. The microcode was generated from the microcode header in the coreboot source tree.
The first patch is waiting for the list moderator's approval as it exceeds the mailing list size. The second patch is at http://patchwork.ozlabs.org/patch/480673/ I will send the first patch to you offline. Please have a try.
Regards, Bin
Hi Bin,
I've created two patches to include a D0 stepping microcode for BayTrail-I. The microcode was generated from the microcode header in the coreboot source tree.
The first patch is waiting for the list moderator's approval as it exceeds the mailing list size. The second patch is at http://patchwork.ozlabs.org/patch/480673/ I will send the first patch to you offline. Please have a try.
After applying both the patches, I am able to get the u-boot prompt with u-boot.rom .
Please find the logs below -
U-Boot 2015.07-rc1-20956-g5d3c2c5-dirty (Jun 04 2015 - 19:27:32 +0530)
CPU: x86_64, vendor Intel, device 30679h DRAM: 2 GiB MMC: ValleyView SDHCI: 0, ValleyView SDHCI: 1 Using default environment
Video: 1280x1024x16 Model: Intel Minnowboard Max SCSI: SATA link 0 timeout. SATA link 1 timeout. AHCI 0001.0300 32 slots 2 ports 3 Gbps 0x3 impl SATA mode flags: 64bit ncq stag pm led clo pio slum part sxs scanning bus for devices... Found 0 device(s). Net: RTL8169#0 Warning: RTL8169#0 using MAC address from net device
=>
Thanks for these wonderful patches.
Regards, Saket Sinha
Hi Saket,
On Thu, Jun 4, 2015 at 10:05 PM, Saket Sinha saket.sinha89@gmail.com wrote:
Hi Bin,
I've created two patches to include a D0 stepping microcode for BayTrail-I. The microcode was generated from the microcode header in the coreboot source tree.
The first patch is waiting for the list moderator's approval as it exceeds the mailing list size. The second patch is at http://patchwork.ozlabs.org/patch/480673/ I will send the first patch to you offline. Please have a try.
After applying both the patches, I am able to get the u-boot prompt with u-boot.rom .
Please find the logs below -
U-Boot 2015.07-rc1-20956-g5d3c2c5-dirty (Jun 04 2015 - 19:27:32 +0530)
CPU: x86_64, vendor Intel, device 30679h DRAM: 2 GiB MMC: ValleyView SDHCI: 0, ValleyView SDHCI: 1 Using default environment
Video: 1280x1024x16 Model: Intel Minnowboard Max SCSI: SATA link 0 timeout. SATA link 1 timeout. AHCI 0001.0300 32 slots 2 ports 3 Gbps 0x3 impl SATA mode flags: 64bit ncq stag pm led clo pio slum part sxs scanning bus for devices... Found 0 device(s). Net: RTL8169#0 Warning: RTL8169#0 using MAC address from net device
=>
Thanks for these wonderful patches.
This is good news! I believe you can continue your work for the ACPI support now :)
Regards, Bin
Great progress If you are looking for ASL support there is some BSD-licensed code at https://svn.code.sf.net/p/edk2/code/trunk/edk2/Vlv2DeviceRefCodePkg/AcpiTabl... for example. ASL should be reasonable portable across various boot loader infrastructure codebase technologies - edkII, coreboot, uboot,.... Vincent
-----Original Message----- From: Bin Meng [mailto:bmeng.cn@gmail.com] Sent: Thursday, June 4, 2015 7:16 AM To: Saket Sinha Cc: Simon Glass; Hawley, John; U-Boot Mailing List; Zimmer, Vincent Subject: Re: Building u-boot.rom for Minnowboard
Hi Saket,
On Thu, Jun 4, 2015 at 10:05 PM, Saket Sinha saket.sinha89@gmail.com wrote:
Hi Bin,
I've created two patches to include a D0 stepping microcode for BayTrail-I. The microcode was generated from the microcode header in the coreboot source tree.
The first patch is waiting for the list moderator's approval as it exceeds the mailing list size. The second patch is at http://patchwork.ozlabs.org/patch/480673/ I will send the first patch to you offline. Please have a try.
After applying both the patches, I am able to get the u-boot prompt with u-boot.rom .
Please find the logs below -
U-Boot 2015.07-rc1-20956-g5d3c2c5-dirty (Jun 04 2015 - 19:27:32 +0530)
CPU: x86_64, vendor Intel, device 30679h DRAM: 2 GiB MMC: ValleyView SDHCI: 0, ValleyView SDHCI: 1 Using default environment
Video: 1280x1024x16 Model: Intel Minnowboard Max SCSI: SATA link 0 timeout. SATA link 1 timeout. AHCI 0001.0300 32 slots 2 ports 3 Gbps 0x3 impl SATA mode flags: 64bit ncq stag pm led clo pio slum part sxs scanning bus for devices... Found 0 device(s). Net: RTL8169#0 Warning: RTL8169#0 using MAC address from net device
=>
Thanks for these wonderful patches.
This is good news! I believe you can continue your work for the ACPI support now :)
Regards, Bin
Hi Bin,
After applying both the patches, I am able to get the u-boot prompt with u-boot.rom . Thanks for these wonderful patches.
This is good news! I believe you can continue your work for the ACPI support now :)
Sure. Thanks a lot for making this possible.
Regards, Saket Sinha
participants (5)
-
Bin Meng -
John Hawley -
Saket Sinha -
Simon Glass -
Zimmer, Vincent