display simple text from PureData?

i tried something very much along those lines yesterday night using P2-7 and it looks promising.
(copied and adapted from the synchronous-gpio example.. so i'm glad i got that right, hah)

didn't have a mosfet on hand to try the extra 12v switching, so for now i had to run the sketch manually and print a message-to-self to plug in the adapter, giving myself 5 seconds to do so
bit stupid, but it seemed to work - now need to implement a switching system and try running at boot..

giuliomoro it's not too hard, really

true. just another hurdle to take. just meant to say that i did come across a lot of new info for this project, what with the OLED, combining lists to symbols and using arrays in Pd, and now this.. but all very useful for the future!
and it demonstrates yet again how helpful this forum is.
still, i'm quite glad i'm not pushing up to the deadline yet all of this learning took me longer than anticipated, shall we say.

giuliomoro with a barebones practical example

and a very useful one, indeed. copy/paste FTW.
used one pin for reset, and another to switch the 12v line (high side switching w/ a 2n3904 - BD140 combo, as i didn't have any P-channel Mosfets around.)
set project to run on boot, and now i get my startup message to greet me after plugging in! huzzah!

phfew. that is beautiful.

so now i'd run this sketch in the background like before? cool.
ALMOST THERE.

in terms of timing - does this sort of 'background' thread start up first, compared to Audio/Pd?
or do they run in parallel?
not that it matters much, just wondering what the mechanics are.

i have loaded a welcome message at the end of the SDD1309 driver sketch, to have some kind of visual on the state of the driver and the I2C connection. i'm thinking of leaving that in there, and loading all the arrays in Pd after a long button press, trying to spread some of the heavier lifting needed at startup. it also would prevent me from sending OSC messages from Pd too quickly - seeing that startup screen should also mean OSC is running in the background and is ready to receive.

giuliomoro probably a bit later. I'd recommend that you don't rely on any particular startup order.

later? hmm, i expected it the other way around for some reason. good to know.

giuliomoro Just have one ping the other until the other responds, then you'll know they are both alive.

since - as you may have noticed - my coding skills are rather limited, i guess that would be banging

[connect bela.local 7562(
I
[netsend]

until [netsend] returns a 1? will try.

not too worried about the startup procedure, actually, apart from getting the order and the timing right - speed doesn't really matter. this is for an art exhibition, so the startup is non-public.. the only audience interaction is the pressing of a button to get a soundfile to play, but it should be up and running when the doors open.

giuliomoro this is clearly over-engineering, but you could have a Bela digital in connected to the pin you are toggling from OSC2OLED4Bela and monitor that pin from within the Pd patch

hahaa
like it!

i guess the only real issue is indeed when to bang the [netsend -u -b] object (which is was using, actually).
have to make sure it doesn't get banged before the custom render is online, and then fails to connect.

now over-engineering is my middle name.
but in this case, maybe i'll just wait a couple of seconds..
or i could manually bang the connection with the button? once i see my startup message, that should have given Pd plenty of time - and that message only appears after the render is running.
will run soms tests asap.

thanks for all the help so far!

hahaaa
it feels like we're actually creating problems now.

didn't have the time today, will probably be thursday before i manage to come back to this.
keep u posted.

i was trying to use Gpio pins 30 and 31 (P2_5 and P2_7).

this is what would need to happen:

"Power ON sequence:
1. Power ON VDD (= 3.3v)
2. After 3.3v become stable, set RES# pin LOW (logic low) for at least 3us and then HIGH (logic
high).
3. After set RES# pin LOW (logic low), wait for at least 3us. Then Power ON VCC.(= 12v)
4. After 12V become stable, send command AFh for display ON.
SEG/COM will be ON after 100ms."

so ideally, i'd start off with ResetPin high and 12vPin low.
pull reset pin Low, then High again.
pull 12vPin high.
the 'Display On' command is in the display_Init_seq()., so i need to toggle those pins before that happens.

i just tried only writing both of them LOW, but they both remain at 3.3V.
so i'm not controlling them at all, as it is.

i added #include <Gpio.h> in render.cpp.
i addedGpio gResetGpio;
int gResetPin = 31;
Gpio g12VGpio;
int g12VPin = 30;

underneath the extern "C" at line 45

and i have this: // hopefully set up pin P2_7 for reset of display
gResetGpio.open(gResetPin, Gpio::OUTPUT);
g12VGpio.open(g12VPin, Gpio::OUTPUT);
gResetGpio.write(0);
g12VGpio.write(0);
usleep(1000000);
gResetGpio.write(0);
printf("try turning on 12v now?\n");
usleep(10000000);
g12VGpio.write(0);

there for now, i was trying to use the repeat lines of write(0) to toggle them HIGH, obviously.

giuliomoro What happens in the destructor of Gpio is dependent on whether the pin was already "exported" before the program started.

no clue what that means, or how to make sure it gets exported.?

i tried it with the config-pin utility in Terminal, that worked fine..
weird thing was that using those pins as outputs is not listed as an option in config -l
but i could set them to output/hi/lo just fine.

right now setting the 1309 test project to run on boot seems to work.
i have no real idea why it works now, but stopped working before- i can only hope it stays this way.

now need to set it so it runs in the background. deja vu