raspberry_256x256_rgb565.h doesn't match raspberry_256x256.png in pico-examples/pio/st7789_lcd

Open
#591 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, raspberry-pi
Domain
embedded-iot

Research direction

Start in pico-examples/pio/st7789_lcd by comparing raspberry_256x256.png with raspberry_256x256_rgb565.h and checking the repository history or nearby documentation for the generation process. Done means documenting the exact conversion steps and explaining why the generated RGB565 bytes differ from the PNG values.

Written by the indexing model from the issue text.

Description

in the rp2040 pico-sdk at https://github.com/raspberrypi/pico-examples.git
in the directory pico-examples/pio/st7789_lcd
there are two related files
raspberry_256x256.png
and
raspberry_256x256_rgb565.h

how was the file raspberry_256x256_rgb565.h generated, since the suggestions I've tried from our friendly LLMs don't seem to generate bytes that match the 16-bit RGB value in the .png file

I was guessing that the presence of both the .png and the .h image files would indicate that they were meant to indicate that one was derived from the other.

Dominant language
C
Stars
3.9k
Forks
1k
Avg merge
1d 16h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/pico-examples

All issues in raspberrypi/pico-examples

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.