Starterware/SN65C1168: Issue of bmpToRaster: cannot convert with 565 RGB argument

user4121072

Part Number: SN65C1168

Tool/software: Starterware

Dear All,

Now I want to use the tool bmpToRaster to convert an image(.bmp) to image.h.

I found this tool can convert with 24 RGB argument (I have an 24bit .bmp image) but cannot with 565 RGB argument (and I have another 16bit bpp .bmp)

When I type below command:

./a.out 800 480 ./16bit.bmp ./image.h 565 RGB

Looks like there is segmentation fault begin of the image.h, shown as below:

$ cat image.h:

ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ0xf800, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff,
0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff,
0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff,
0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff,
0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff,
0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff,
0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff,
0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff, 0xffff,

......................

Can anyone provide some helps? My PC is ubuntu 16.04 64-bit.

Thanks in advance!

Jakebo

over 7 years ago

0 Lalindra Jayatilleke over 7 years ago

TI__Mastermind 30365 points

Moving this thread to the industrial interface forum.

0 RandyP over 7 years ago in reply to Lalindra Jayatilleke

TI__Guru* 84110 points

No idea how this got to the C67x Single Core DSP Forum, but trying again to get it to the Industrial Interface forum. Lalindra is not referring to MPU/DSP Starterware from what I can tell. -RandyP

0 Clemens Ladisch over 7 years ago

Guru 242930 points

In the ISO8859-1 encoding, "ÿ" is the character with the code 0xFF.

This looks as if the program dumps some garbage at the beginning of the file. It's possible that the string "unsigned short const image[] = {" was overwritten, possibly due to a buffer overflow.

In theory, the tool should complain if some parameter is not correct. Please show the output of "file ./16bit.bmp" and "hexdump -C -n 128 ./16bit.bmp".