i2c dev -b 1 0x00 0x7f
>>
>> It will show you the used I2C addresses.
>>
>> Hope this will help you!
>>
>> With kind regards,
>> Ben
>> nuttx.nl
>>
>>
>> -Oorspronkelijk bericht-
>> Van: Matt DeWall
>> Verzond
; Ben
> nuttx.nl
>
>
> -Oorspronkelijk bericht-
> Van: Matt DeWall
> Verzonden: dinsdag 8 december 2020 21:17
> Aan: dev@nuttx.apache.org
> Onderwerp: Re: ssd1306 oled help
>
> Thanks everyone - apologies for the delay, some other priorities blocked
> me.
>
>
help you!
With kind regards,
Ben
nuttx.nl
-Oorspronkelijk bericht-
Van: Matt DeWall
Verzonden: dinsdag 8 december 2020 21:17
Aan: dev@nuttx.apache.org
Onderwerp: Re: ssd1306 oled help
Thanks everyone - apologies for the delay, some other priorities blocked me.
Looks like I was
Thanks everyone - apologies for the delay, some other priorities blocked
me.
Looks like I was getting bit by cygwin and "make clean_context all" got me
sorted out and actually reflected my changes.
However, I'd like to understand how to get the i2ctool working. I was able
to add it and see it in
Hi Matt,
Sorry my delay to reply.
As Mr. Greg pointed the issue is related to your OLED display I2C address.
Normally these OLED display has an Address Select using a 0R resistor
to 0x78 or 0x7A.
You need to setup the CONFIG_SSD1306_I2CADDR with the right address.
Also as Mr. Ben suggested, us
It will give you the insights you need I hope and from there one could help
you further. Good luck and I hope you get it working!!
Op za 5 dec. 2020 2:14 a.m. schreef Matt DeWall :
> Didn't know about that one, thanks! Found one of Alan's articles for that
> and gonna give that a shot.
>
> Matt
Didn't know about that one, thanks! Found one of Alan's articles for that
and gonna give that a shot.
Matt
On Fri, Dec 4, 2020 at 5:01 PM Disruptive Solutions <
disruptivesolution...@gmail.com> wrote:
> Did you try the i2c tool?
>
> Op za 5 dec. 2020 1:58 a.m. schreef Matt DeWall :
>
> > Got it
Did you try the i2c tool?
Op za 5 dec. 2020 1:58 a.m. schreef Matt DeWall :
> Got it. Ok - looks like my 116 errors were from my later experimenting.
> If I completely disconnect or try other i2c pins, I get 116, so that makes
> sense.
>
> So it looks like when I connect the pins correctly I'm g
Got it. Ok - looks like my 116 errors were from my later experimenting.
If I completely disconnect or try other i2c pins, I get 116, so that makes
sense.
So it looks like when I connect the pins correctly I'm getting the 6 error.
I'm wondering if that just means somehow my device has an i2c addr
Should have mentioned that the error code 6 is defined in include/errno.h:
#define ENXIO 6
#define ENXIO_STR "No such device or address"
And errcode code 116 is:
#define ETIMEDOUT 116
#define ETIMEDOUT_STR "Connection timed out"
Which is also
As far as I can tell, this looks like an I2C problem. Alan problem
knows better than I.
I think the failure sequence is:
fs/vfs:
ioctl(FBIO_UPDATE)
drivers/video/fb.c ioctl method:
ret = fb->vtable->updatearea(fb->vtable, area);
drivers/lcd/lcd_framebuffer.c, functio
Hello NuttX devs!
I've followed Alan's great tutorial on setting up an OLED on the Blue Pill
stm32f103-minimum board but running into trouble.
Video:
https://www.youtube.com/watch?v=TZ4i71ArtRo&t=245s
* I've compiled, flashed, and able to get into nsh
* The fb driver is listed as /dev/fb0 and th
12 matches
Mail list logo
