Newbie SPI question

[Scampy]

Henrik,

I'm not blaming anyone, and I understand the minefield that is out there in the domain with lots of different controllers for lots of different screens, and even some controllers are different and have three or more variations... so I quite agree with the task at hand should someone try and venture down that route. But you have also backed up my point. The Arduino community develop "stuff" for technology as it comes out and then the more it gets used the better or improved versions if library files appear. MikroElektronika, whilst being a commercial organisation try to keep abreast of technology and constantly update the range of products with associated library files and software to aid the use of the hardware. I don't know what it is in the PBP camp, but for me at least it feels that it's now lagging behind. Even this forum is slow compared to a few years back. I know a lot of the old school folk like yourself have either moved on, or passed on (RIP DT ), and you guys give us less knowledgeable folk excellent support, but the developers of PBP seem to be lagging behind.

I've not had the opportunity to see what new commands (if any) are available in PBP3, but are there commands for Ethernet, Wi-Fi, TFT screens, etc that would make coding for these devices, (which lets face it have been around for years now) a lot easier. I mean the principles and protocols for things like ethernet are the same regardless of what platform you are using... so it shouldn't (IMO) bee that difficult.

I love PBP. its syntax is very easy to understand, debugging a line of code to work out what's missing in the statement is simple, the manual is a good reference, and there are folk like you who are willing to offer assistance (both on and off board) to resolve issues or develop include files to help others in the future. I don't want to jump ship and just because other platforms have a library to do a set function, or work with a bit of hardware I want to use. But equally I don't like being stuck in the dark ages having to use serial comms, and basic LCD's because that's all that PBP has to offer.

Sorry for the rant, and it's a tad off topic, and hope that you don't take offence over my PBO "bashing" !!

[richard]

I agree with malcom , but its seems the only way forward for now is to help ourselves.
a simple start with one or both of the previously mentioned devices (spi versions only ) on a pic18 with a chr(32 to 90 ) ( space to Z) 8x8 font (in program memory) using hardware spi and a simple background/foreground colour scheme . I think this is achievable especially with a few participants involved .
I'm in anyone else ?

[Gusse]

Have you checked LCD Wiki pages?
There are most of the stuff you need available. Only thing you need to do is modify LCD controller specific parts to match your LCD display (e.g LCD init, std commands, etc...).

If there are Arduino C-codes available for your LCD controllers, then it is even easier to port code to PBP. C and PBP are very similar, only systax is different.
Other method is to read programmers manual and figure out all necessary part of the code from there (hard way).

I could be interested to port my LCD projects to some newer LCD (from monochrome Nokia 3310 LCD, which is still very usable).

LCD module requirements:
- some commonly used LCD (code available in Arduino platform, etc...)
- touch screen functionality (or same LCD controller in modules w and w/o touch screen support).
- SPI (LCD) /I2C (touch) interface
- ~2-3" size

Code could be developed/shared in GitHub to track history and bugs if multiple persons are involved.
I could start participating later on autumn, due to fact that summer is very short here -> I have other activities than coding and debugging