Forum Rule: Always post complete source code & details to reproduce any issue!

Search:

Type: Posts; User: bkausbk

Search: Search took 0.00 seconds.

  1. Replies
    36
    Views
    13,160

    There is no more lost pixel, however sometimes...

    There is no more lost pixel, however sometimes readPixel() hangs in infinite loop, even with regular Teensy 3.1 clock of 72 MHz (tested with 7.2MHz SPI clock). Please note, I can't guarantee that the...
  2. Replies
    36
    Views
    13,160

    Yes, I tried your changes and it happens that...

    Yes, I tried your changes and it happens that readRect() was executed infinite. However, I think we should not handle the case when bytes were eaten because of too high clock rates or noise. If so,...
  3. Replies
    36
    Views
    13,160

    @KurtE: unfortunatelly there is still this one...

    @KurtE: unfortunatelly there is still this one lost pixel. I added a counter variable and indeed one pixel is not read. But as I said, this only happens when Teensy 3.1 clock is set to 96 MHz.


    ...
  4. Replies
    36
    Views
    13,160

    @pictographer: Please try default 72 MHz and SPI...

    @pictographer: Please try default 72 MHz and SPI clock of 6-18 MHz. readPixel() seems to be ok if the clock is not too fast/noisy.
  5. Replies
    36
    Views
    13,160

    Hi KurtE thanks for looking at that. However...

    Hi KurtE thanks for looking at that. However after further investigation I found out that the problem does not exists when changing Teensy 3.1 clock rate back to default 72 MHz. The problem was 100%...
  6. Replies
    36
    Views
    13,160

    Reading pixel is correct implemented concerning...

    Reading pixel is correct implemented concerning ILI9341 interface specification at least commands sent to the display are correct and commands for reading inclusive 18 bits to 16 bits conversion...
  7. Replies
    36
    Views
    13,160

    I found the reason. It is a timing problem, clock...

    I found the reason. It is a timing problem, clock rate is too fast. In my situation SPI clock of 20 MHz is still acceptable, 25 MHz for example causes data corruption on read. But why not on write?
    ...
  8. Replies
    36
    Views
    13,160

    Writing to the GRAM indeed goes through the LUT....

    Writing to the GRAM indeed goes through the LUT.

    3642

    You can try to change the LUT with the Color Set (2dh) command. First 32 bytes are the corresponding 6 bit values of the given 5 bit red...
  9. Replies
    36
    Views
    13,160

    But you already know that when reading the colors...

    But you already know that when reading the colors are 18 bit (RGB 6-6-6)?

    See following page 64 of the ILI9341 documentation:

    3641
Results 1 to 9 of 9