0

When running an INTEGRITY 178 ARINC/APEX image on a PPC SBC, using uboot console we load the program with tftpboot and initiate execution with bootelf. (We actually enter an extra RETURN after the bootelf command so that the INTEGRITY copyright banner displays on the uboot console when the target begins execution.)

Question: Why is there about a 12 second delay between the bootelf command and the apparent beginning of execution of the application portion of the image? And if there is a way to reduce this delay?

Potential sources uboot, POST, GHNet network initialization, other sources...?

Thanks,
mlk

Michael L Kornegay
  • 1
  • 1

1 Answers1

0

For us, the filesystem initialization is the longest delay at boot.

sdstack
  • 185
  • 9
  • Yes I could see that being a contribution.Our target image does not include a filesystem, does not r/w data flash, .... That is why in original post I thought might be POST of some sort or maybe GHNet TCP/IP stack initialization. – Michael L Kornegay Oct 16 '14 at 10:59