IceNav

Well, new board has arrived .

New challenge for the project, give support for LilyGo T4-S3 board.

An AMOLED ESP32S3 16Mb Flash and 8Mb PSRAM, 450x600 screen resolution...., really it's very cool!!

First of all, try to support this board in LovyanGFX . This screen has a QSPI interface , and , well, maybe it will so difficult, but not impossible!

Stay tunned! 

These days I’ve been receiving requests to support boards already available on the market to make IceNav compatible... If all goes well, I’ll soon provide support for the LilyGo T4-S3. This is a challenge since IceNav currently relies on a graphics library that apparently doesn’t support this type of AMOLED screen, but as they say, 'nothing is impossible.' ... Soon, if everything goes smoothly, I’ll be updating you on the progress. 

Stay tunned.

After several months of code corrections, optimization, etc., the master branch of the repository has been synchronized with the devel branch. It is not yet a final release, but if all goes well, it will be available before the end of the year.

Those who have forked or looked at the master branch will see that there are quite a few changes.

You will be able to see all the changes, etc... in the logs

Thanks to the help from @hpsaturn , the first field tests have already been carried out with a LilyGo T-DECK. There are still some small bugs and adjustments to be made, but it is almost 100% functional.

Here you have a short video of the result.

Hardware support for LiLygo t-deck board is full implemented.

It is not yet published as a release, since at the firmware level some screens need to be adjusted, etc., to make it 100% functional at the user experience level.

All these changes will most likely be applied in the next release.

Stay tuned!

These weeks I have been working on a revision of the IceNav PCB

The idea is to minimize as much as possible and use TFT in parallel mode and not SPI in order to obtain maximum performance at the graphic level.

The PCB design is ready, but it remains to be seen whether the appropriate tests can be carried out and whether a good enough design can finally be achieved.

Until we have a physical PCB and can perform the corresponding tests, the PCB design would be something like this:

This is a first revision, the idea is to be able to integrate modules such as battery charging, sensors, etc... without using existing modules, but I think it's a good start...

Hi,

Support for T-DECK from lilygo is going at a good pace. (taking into account the limitations on my part of not having this board)

Thanks to hpsaturn We are stabilizing the migration and adding new features, such as battery saving, etc., etc.

Following the "roadmap" and if everything goes well, I will soon publish a new firmware release with many new features and perhaps a review of the IceNav custom board

Stay tunned!

I’m currently working on providing support for the LilyGo T-DECK.

Thanks to the immense help of @hpsaturn, a collaborator in my development, we are trying to adapt IceNav to a LilyGo T-DECK.

Since I don’t physically have the device, the development will take some time.

Anyway, I will keep updating on the progress both here and on my GitHub.

Stay tuned!

Although the purpose of this project was to create my own hardware, I see that there are currently solutions on the market that are perfectly valid for my development to work.

That’s why, regardless of my desire to design specific hardware, I want to change the focus of the project and provide support for existing hardware. This way, I believe it would be easier for anyone who wants to make use of it.

Lately, I've realized that this option might help the project reach more people, and who knows, it could end up being used.

That’s why my intention is to try, as much as possible, to ensure that my project can be used with the maximum number of existing hardware solutions that I believe are valid.

To achieve all this, it will involve trying to emulate all the possible existing solutions since I don’t have access to all of them.

Stay tuned!

Due to Hackaday problems.... my last project log doesn't have a screenshot for the new feature...

It's this..