On Wed, 21 Feb 2024 at 18:20, Faiq Ali Sayed <faiqueali....@gmail.com> wrote: > > >> >> This is also useful information. I would suggest you look >> at what the difference is between the image that boots and >> the one that doesn't: is it the same format (and what format >> is that)? is the way it is loaded on the real hardware the >> same, or different? > > > I am not able to distinguish between the images as they are in binary form, > I noticed that the smaller size image can boot in Qemu. > I normally put the image into an SD card of the real hardware to boot. > so it is quite difficult for me now to distinguish. > > >> From the debug info from gdb you provided, the file clearly >> is not a raw binary file -- the initial bytes seem to be >> largely ASCII text. So it might be that this image is in >> a file format that whatever the real-hardware loader >> recognizes, but QEMU doesn't, whereas the images you have >> that work are really raw binaries. In that case you'd want >> to convert the image somehow to a format QEMU can understand >> (eg ELF, or raw-binary). > > > ahh, that also makes sense, ok now let me try to convert the images, and > let's see. > Does Qemu provide such a tool or do you know any?
We don't know what format these images are in, so hard to say, but I would expect not (mostly QEMU's image conversion handling is for filesystems, not guest binaries). You'll probably do best to look on the QNX and/or Xilinx side -- Xilinx should document what file formats it is that their boot process accepts. Your third-party vendor presumably also knows what format it is that they're generating the image in. -- PMM
