Greetings Steve, For creating a bootable IVI image I highly suggest using the bmap tool instead of direct dd. It's easier, faster, and much more reliable. You can read about it in these two links:
https://source.tizen.org/documentation/articles/bmaptool -- A detailed overview of the tool https://wiki.tizen.org/wiki/IVI/IVI_Installation -- A more IVI specific overview. There isn't any difference in the NDis166 hardware that I am aware of. Using the bmap tool with that image should give you a bootable USB stick. Hope that helps and welcome to Tizen IVI. From: [email protected] [mailto:[email protected]] On Behalf Of Maurer, Steven Sent: Friday, August 09, 2013 11:37 AM To: [email protected] Subject: Introduction and looking for pointers Hello all, Let me introduce myself. I'm Steve Maurer. There is a new team of us who have just joined Jaguar Land Rover working on Tizen IVI. We'll become more active in the Tizen developers forums as we get our feet wet in this. Speaking of which, I don't know if this is the correct place to mention this, but the IVI July 29, 3.0-M2-Jul does not appear to work on my NDis166 device, which is supposed to be supported. I followed the instructions and after downloading the executable tizen_20130729.2_ivi-release-mbr-i586-sdb.raw.bz2<http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/images/ivi-release-mbr-i586/tizen_20130729.2_ivi-release-mbr-i586-sdb.raw.bz2> from http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/images/ivi-release-mbr-i586/, I unpacked it onto a bootable GParted USB stick, dd-ed it onto the partition, refreshed Gparted, allowed Gparted it to fix the end MBR, and see it produces the following: Partition File system Label Size Used Unused /dev/sda1 ext4 boot 63.98MiB 13.97 MiB 50.01 MiB /dev/sda2 ext4 platform 3.66GiB 702.93 MiB 2.97 GiB unallocated 33.55 GiB Unfortunately, when I reboot with this, it fails to be recognized as bootable by the NDis166 at all. At this point I'm not sure what to do. Is there something obvious that I'm missing? Was the raw partition built for some other type of device? Should I not let Gparted fix the MBR backup location? Should try to resize the partition immediately? I'm also wondering if there might be some variations within the NDis166 hardware that makes my box fail to accept the image. About the only variation on the procedure I performed was that I downloaded the original .bz2 file and used windows to unpack the raw data file onto the SanDisk stick, but that shouldn't make any difference whatsoever. If there is anyone who knows the trials and travails of getting this to work, I'd be appreciative. -- Kind Regards Steven Maurer ------------------- Infotainment Engineer MSX on behalf of Jaguar Land Rover One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204 Email: [email protected]<mailto:[email protected]>
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
