Well sometime back I had successfully build the DuetPkg on both IA32 & X64 architectures. Futher experimenting I came across the build32.sh which enabled me to prepare the efiloaders & floppy images without the need to follow their manual setups. Well after setting up my USB flash for DUET & booting I faced a freeze problem like a hyphen in the left side corner. It would get stuck there until I restarted & so I was unable to figure the problem at all. However getting to qemu to boot it seemed just successful & capturing debugging messages was just useless.
Thus Goggling a bit I came across rod books a BIOS to UEFI Transformation wherein it was mentioned that one of the versions may succeed i.e. either 2.1 or 2.3.1 so I figured out it between EDK_UEFI64 & UDK_X64 (resp) & decided to go with the 2.1 version & there it just booted successfully.
I dont know why there is a failure between  EDK_UEFI64 & UDK_X64. I had last time falsely implicated it to be a EM64T error which I had noticed on Oracles VM Box but  my processor (Intel Pentium D) readily supports it. By the way this how I had set up the USB.

I followed Migles BootDuet

user#cd BootDuet

user# dd if=/dev/zero of=/dev/sdb bs=3M count=1 && cfdisk.gnu /dev/sdb

Under which I created a msdos table, setting up a fat32 partition & 'boot' & 'lba' flags

user#make lba64

user# make DEVICE=/dev/sdb1 install-bd32_64

then disconnected my USB & reconnecting

user# mount /dev/sdb1 /mnt/windows && ./copy_duet_files.sh /mnt/windows/ UDK_X64

I hope so someone on this mailing list would help me solve my problem. I know that I should have posted this on the edk2 mailing list but since the DUET setup has been a part of the coreboot development I decided to ask for help here.

Regards