Prebuilt NXP BSP 33 binaries for S32G274AEVB does not boot - no u-boot preamble output whatsoever

[jmeyer15]

In the past, I have taken the NXP prebuilt binaries for BSP30 and made a successful bootable SDCard.  Followed the same procedures for the BSP33 release with the same EVB board with no success.  There is no u-boot preamble output whatsoever on the serial port.  Immediately reverted back to BSP30 SDCard to verify a working EVB board with no problems.  Are there changed switch settings on the EVB between BSP30 and BSP33 releases - if so, then I missed that section of reading.  Any comments/suggestions would be greatly appreciated.

After successfully Yocto building BSP30, I have tried building with BSP32 and BSP34 with no success and have not had prebuilt NXP binaries to validate the builds I have made.  My BSP32/34 builds also boot with no trace of u-boot preamble output.  I have confirmed that I am using gatesgarth Yocto from poky.conf.

[jmeyer15]

On page 28 of the LinuxBSP33UserManual, I followed all the directions as stated.  I used the prebuilt BSP33 binaries from the NXP web site.

• Inserted an SDCard in a USB reader on my Linux machine.
• Umounted all the active partitions
• Export DEVSD=/dev/sdb
• sudo dd if=./fsl-image-auto-s32g274aevb.sdcard of=${DEVSD} bs=1M && sync
• Inserted the SDCard into the EVB with the switches set for SD mode as outlined on Page 41.
• As stated before, there was no u-boot output whatsoever with BSP33.

This morning, as additional verification (and for my own sanity), I grabbed from the NXP web site the prebuilt BSPs from BSP28, BSP29 and BSP30.  Followed the above procedure with all three BSP binaries and generated successful boots from my EVB (without changing any switches from the settings shown on Page 41).  BSP33, when tried again after three successful boots with the same hardware configuration, however failed.

What additional information do you need from me?

[Daniel-Aguirre]

Hi,

Thanks for the information. Just as a sanity check from our side, you are using the same SD card for each of the images? Or you are using different SD's?

Are you verifying that there is only 1 partition on the SD you are using (prior to using the *.sdcard file)?

We will start looking for any changes (if any) are needed for the EVB platform to run BSP33.0.

[jmeyer15]

To answer your questions – 1) I used the same SDCard (that meets all required qualifications) for all my tests mentioned previously, 2) In my previous tests, I did not format my SDCard to one partition before the “dd” copy, though I did umount all active partitions before any “dd” copy.  I tried your suggestion of reformatting my SDCard to one partition before copying the .sdcard file – that had no effect.

In the past, I did build a standard BSP30 from scratch and it booted successfully (as mentioned before, I also did standard builds of BSP32 and BSP34 with unsuccessful results).  Today, I decided to download and standard build BSP31 – it booted successfully.  Also, downloaded and standard built of BSP32 again – that did not boot at all (to reconfirm previous results).

If I were to hazard an informed guess at this point, the build recipe was broken between BSP31 and BSP32.  In doing a MELD comparison of the “sources” directory where all the recipes are stored, there appear to be changes that delete references to some S32G274A related files.  I will follow up on this after the Thanksgiving holidays with a more detailed examination of those changes.

[Daniel-Aguirre]

Hi,

We got confirmation that EVB HW should be working with BSP33. Below the comments:

"There must be an issue in the process of writing the image to the SD card. There are tools like balenaEtcher as an alternative for WinDiskImager in Linux. Customer can try writing SD card once again. 

I just did a quick check with S32G274AEVB and BSP33, works fine on my end."

It seems the problem could be related to the burning of the image, have you used other alternatives like the ones mentioned by the team?

Please, let us know.

[Jj17]

Hello,

I have the exact same problem here. BSP29 boots fine while 33 isn't showing anything at all.

I tried dd, balena-etcher, having 1 partition, it does simply not work (while BSP29 works fine). 
I got the fsl-image-auto-s32g274aevb.sdcard prebuilt image from the nxp website for BSP33. 

Note also that I noticed switch position to boot from SD has changed between BSP29 and BSP33 in the reference manual. I tried both switchs configuration for all my testing, nons works. 

If internal team managed to make it work, knowing exactly how he did instead of tools he used would be great : That include his way of getting the images, of flashing, and board set up.

Thanks 

[Daniel-Aguirre]

Hi,

How are you flashing the SD for your platform? What steps are you following?

The prebuilt "fsl-image-auto-s32g274ardb2" is working no problem, yours should be "fsl-image-auto-s32g274aevb". 

What switches are you changing?

Please, let us know for us to continue improving our answer.

[ronbexten]

I am having the same problem with a S32G274a EVB.  BSP 25 and 30 works fine using prebuilt images but BSPs 32 and 33 have absolutely no output on the console at power up.  I used prebuilt images in all cases using balena-etcher on a Linux box to create the SD card image and also used the dd method.  I made no changes to any switches on the EVB and used the exact same SD card in all cases. 

Your assistance will be greatly appreciated.