I did not have this problem before migrating VDSP++ to Windows 7 Enterprise. When I compile my .c source to create a .ldr file (intel hex format), burn it to a 28LV010 EEPROM, it will not boot properly. When I use a .ldr file from before the migration, it works fine. I can also compile to a .dxe and use the HPUSBICE to load it into the DSP and that works fine. So the hardware is fine, since it runs from the emulator pod as well as an older compilation in a boot prom.
What I notice when comparing a .ldr that works to one that doesn't, is different content after the end of the kernel (first 0x600 bytes). On a working prom, the code after the kernel shows contiguous addressing to the end of the file. On a non-working prom, there are several lines that have non-contiguous addressing and shorter byte counts, followed by the code.
I can provide example listings of the two cases.
My question is.... Is this an issue with loader settings? What do I need to do to fix this? Has anyone else experienced this before?