Launch of the all new Picadillo-35T - PIC32 Embedded Display Module

[James_4DSystems]

Like Arduino / chipKit style development boards?
Like 4D Intelligent Display Modules?
Like TFT LCD Displays with Resistive Touch?

We decided to combine a number of concepts into a single product, and we came up with this!

For more information, please refer to the 4D Systems website and Product Page for the Picadillo-35T, http://www.4dsystems.com.au/product/Picadillo_35T/

[craigsprojects]

Libraries do not compile for many of the Picaldillo-35t examples, not good for promotion for the display.

do I have a problem in installation? or are the Libraries have problems?

for example

---

WindowDemo:
‣ DSPI
IC:\Users\craig\Documents\UECIDE\libraries\DSPI\utility -w
C:\Users\craig\Documents\UECIDE\libraries\DSPI\DSPI.cpp: In member function 'void DSPI::transfer(uint16_t, uint8_t*, uint8_t*)':
C:\Users\craig\Documents\UECIDE\libraries\DSPI\DSPI.cpp:632:41: error: '_SPISTAT_SPITBF' was not declared in this scope
C:\Users\craig\Documents\UECIDE\libraries\DSPI\DSPI.cpp:638:41: error: '_SPISTAT_SPIRBE' was not declared in this scope
C:\Users\craig\Documents\UECIDE\libraries\DSPI\DSPI.cpp: In member function 'void DSPI::transfer(uint16_t, uint8_t*)':
C:\Users\craig\Documents\UECIDE\libraries\DSPI\DSPI.cpp:681:41: error: '_SPISTAT_SPITBF' was not declared in this scope
C:\Users\craig\Documents\UECIDE\libraries\DSPI\DSPI.cpp:687:41: error: '_SPISTAT_SPIRBE' was not declared in this scope
C:\Users\craig\Documents\UECIDE\libraries\DSPI\DSPI.cpp: In member function 'void DSPI::transfer(uint16_t, uint8_t, uint8_t*)':
C:\Users\craig\Documents\UECIDE\libraries\DSPI\DSPI.cpp:734:41: error: '_SPISTAT_SPITBF' was not declared in this scope
C:\Users\craig\Documents\UECIDE\libraries\DSPI\DSPI.cpp:740:41: error: '_SPISTAT_SPIRBE' was not declared in this scope
Failed compiling libraries

---

rtccGUI:

In file included from E:\Other-Projects\4DSYSTEMS\Picadillo-35T\Real-Time clock & Calendar\project files\UECIDE files\rtccGUI\libraries\SD/SD.h:20:0,
from C:\Users\craig\Documents\UECIDE\libraries\gciWidget/gciWidget.h:7,
from E:\Other-Projects\4DSYSTEMS\Picadillo-35T\Real-Time clock & Calendar\project files\UECIDE files\rtccGUI\gciWidget.cpp:1:
E:\Other-Projects\4DSYSTEMS\Picadillo-35T\Real-Time clock & Calendar\project files\UECIDE files\rtccGUI\libraries\SD/utility/SdFat.h:285:10: error: conflicting return type specified for 'virtual size_t SdFile::write(uint8_t)'
C:\Users\craig\AppData\Local\UECIDE\cores\chipKIT\api/Print.h:50:15: error: overriding 'virtual void Print::write(uint8_t)'
E:\Other-Projects\4DSYSTEMS\Picadillo-35T\Real-Time clock & Calendar\project files\UECIDE files\rtccGUI\libraries\SD/utility/SdFat.h:287:10: error: conflicting return type specified for 'virtual size_t SdFile::write(const char*)'
C:\Users\craig\AppData\Local\UECIDE\cores\chipKIT\api/Print.h:51:15: error: overriding 'virtual void Print::write(const char*)'
In file included from C:\Users\craig\Documents\UECIDE\libraries\gciWidget/gciWidget.h:7:0,
from E:\Other-Projects\4DSYSTEMS\Picadillo-35T\Real-Time clock & Calendar\project files\UECIDE files\rtccGUI\gciWidget.cpp:1:
E:\Other-Projects\4DSYSTEMS\Picadillo-35T\Real-Time clock & Calendar\project files\UECIDE files\rtccGUI\libraries\SD/SD.h:36:18: error: conflicting return type specified for 'virtual size_t File::write(uint8_t)'
C:\Users\craig\AppData\Local\UECIDE\cores\chipKIT\api/Print.h:50:15: error: overriding 'virtual void Print::write(uint8_t)'
E:\Other-Projects\4DSYSTEMS\Picadillo-35T\Real-Time clock & Calendar\project files\UECIDE files\rtccGUI\libraries\SD/SD.h:37:18: error: conflicting return type specified for 'virtual size_t File::write(const uint8_t*, size_t)'
C:\Users\craig\AppData\Local\UECIDE\cores\chipKIT\api/Print.h:52:15: error: overriding 'virtual void Print::write(const uint8_t*, size_t)'
Failed compiling sketch

---

Buttons:

C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:7:44: error: no matching function for call to 'twButton::twButton(Picadillo&, AnalogTouch&, int, int, int, int, const char [3])'
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:23:9: note: candidates are: twButton::twButton(Touch&, DisplayCore&, int16_t, int16_t, uint16_t, uint16_t, const char*)
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:6:32: note: twButton::twButton(const twButton&)
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:8:48: error: no matching function for call to 'twButton::twButton(Picadillo&, AnalogTouch&, int, int, int, int, const char [4])'
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:23:9: note: candidates are: twButton::twButton(Touch&, DisplayCore&, int16_t, int16_t, uint16_t, uint16_t, const char*)
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:6:32: note: twButton::twButton(const twButton&)
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:10:41: error: no matching function for call to 'twButton::twButton(Picadillo&, AnalogTouch&, int, int, int, int, const char [2])'
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:23:9: note: candidates are: twButton::twButton(Touch&, DisplayCore&, int16_t, int16_t, uint16_t, uint16_t, const char*)
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:6:32: note: twButton::twButton(const twButton&)
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:11:42: error: no matching function for call to 'twButton::twButton(Picadillo&, AnalogTouch&, int, int, int, int, const char [2])'
.
.
.
.
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:23:9: note: candidates are: twButton::twButton(Touch&, DisplayCore&, int16_t, int16_t, uint16_t, uint16_t, const char*)
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:6:32: note: twButton::twButton(const twButton&)
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:16:42: error: no matching function for call to 'twButton::twButton(Picadillo&, AnalogTouch&, int, int, int, int, const char [2])'
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:23:9: note: candidates are: twButton::twButton(Touch&, DisplayCore&, int16_t, int16_t, uint16_t, uint16_t, const char*)
.
.
.
.
int, int, int, int, const char [2])'
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:23:9: note: candidates are: twButton::twButton(Touch&, DisplayCore&, int16_t, int16_t, uint16_t, uint16_t, const char*)
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:6:32: note: twButton::twButton(const twButton&)
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino: In function 'void setup()':
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:32:33: error: no matching function for call to 'twButton:etTextColor(const uint16_t&)'
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:40:14: note: candidate is: virtual void twButton:etTextColor(uint16_t, uint16_t)
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:33:12: error: 'Ubuntu30' is not a member of 'Fonts'
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:36:28: error: no matching function for call to 'twButton:etTextColor(const uint16_t&)'
C:\Users\craig\Documents\UECIDE\libraries\Widgets/twButton.h:40:14: note: candidate is: virtual void twButton:etTextColor(uint16_t, uint16_t)
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:37:13: error: 'Ubuntu30' is not a member of 'Fonts'
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:39:12: error: 'Ubuntu20' is not a member of 'Fonts'
.
.
.

C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:46:12: error: 'Ubuntu20' is not a member of 'Fonts'
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino: In function 'void loop()':
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:55:27: error: void value not ignored as it ought to be
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:56:29: error: void value not ignored as it ought to be
C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:58:16: error: could not convert 'a1.twButton::<anonymous>.Widget::render()' to 'bool'

.
.
.

C:\Users\craig\Documents\UECIDE\libraries\Widgets\examples\PICadillo-35T\Buttons\Buttons.ino:66:16: error: could not convert 'b4.twButton::<anonymous>.Widget::render()' to 'bool'
Failed compiling sketch

---

I am new to this display and do not fully understand all the tools yet as well as the product. But it seems the results should be better with less frustration. Some examples work fine for example: AAFont, AlphaDemo, DoubleBuffer, FontDemo, Heart, HSWave,Keypad, Primitives, ScrollingWave, Skribble, WindowDemo

where do I start to look? (to many characters to post the full errors)

[James_4DSystems]

Hello,

Yes there have been a number of changes in the last few months, and I admit the information has not been as easy as it should have.

When Picadillo was released, it used the TFT library, and everything worked around that.
TFT has be superseeded by the DisplayCore library.

https://github.com/MajenkoLibraries/DisplayCore

If you go into UECIDE, Displaycore should be installed by default when you install the picadillo library.
There are a number of sub libraries which various things use however, things like Fonts have their own sub library and you install them as required from the UECIDE plugin manager.

The widgets library, I know there is one called Buttons which didn't work when I last tried it.
There may be other libraries, which are not specifically part of this DisplayCore, which no longer compile too.

I have sent a message to the author of this set of libraries, hopefully he will reply back to you soon with some more information.

Regards

[majenko]

You need to make sure that all your software is up to date. That includes using the latest version of DisplayCore as distributed within the UECIDE plugin manager, you're using the beta version of UECIDE (the "stable" version isn't), and that your chipKIT core and pic32-tools compiler plugins are fully up to date.

You should also remove the manually installed libraries that will conflict with the UECIDE installed DisplayCore libraries.

The first error (the DSPI one) may have been a mismatch between the core (released in the last few days) and the compiler (only released in "testing"). I have just released the updated compiler to the main repository and should be available to upgrade in the next few minutes.

[sopronil]

Hello, I'm new here . I have bought a Picadillo 35T, but no way can communicate via USB. From whom and where to ask for help in this matter?
Regards,
László

[James_4DSystems]

Hello László

Can you please provide more detail on what the problem is.
Which USB are you referring to? The programming port at the bottom of the module, or the PIC32 USB pads at the top of the module?

Regards

[sopronil]

Hi James,
Thanks for the response,
1.
I tried to install UECIDE, the application works well but when I click to install PIC32 compiler than the downloading succeed but the install progress runs no more than 16% and stops. No any error message. I tried it on my laptop the problem is same.
2. I don't gave up, therefore I was looking for an other application: workshop by 4d systems. downloaded, installed, launched.
Followed the desired steps to make a new project, everything was ok, two files on the sd card , put into the sd and reset, but didn't happen anything, no problem I exchanged the sd an other type from kingston to sandisk, the result was same.
3.
I installed the USB serial driver and launched the serial terminal and sent any data to display: on the board the TX led flashes once but no answer.
So I have a nice display but I can't use it.
I've got PICKIT 3 and some microchip gadget. I'd like to ask from you any help.
Have a nice day.
László

[sopronil]

Hi James,
Where can I download the factory program to the Picadillo 35t?
Regards

[James_4DSystems]

Hello Sopronil,

PIC32 compiler is downloading fine here:



Workshop4 is not utilised for the Picadillo-35T. It does not feature a 4D Systems processor on it, which is why UECIDE is used. Please try downloading again, maybe there was a comms outage or server issue.
Unsure how you would make a new project for the Picadillo-35T in Workshop4, as there is no Picadillo-35T product to select from the product list.

The Picadillo-35T will come preloaded with the USB bootloader in it, so you program the Picadillo-35T using the USB cable. If you want to use the PICKIT3 then that is fine, however it is not required for normal operation. If you have loaded something with the PICKIT3 then you have likely wiped the bootloader, so you will need to reload it. It is available on the product page, under Software and Tools. http://www.4dsystems.com.au/product/Picadillo_35T/

I assume this is what you mean by 'Factory Program' ?

Regards

[sopronil]

Hi James,
Thanks for a help, I tried to download the latest version (uecide-0.8.8 alpha22-full.exe)deleted the previous and reinstalled, the pic 32 complier downloaded perfectly but the installation stopped. I controlled the filesystem and noticed that there is the compiler in my PC( see at the attached picture).
What can be wrong on my PC? Windows 7. 32 bit.
Of course I use the bootloader from the PICADILLO 35t side and uploaded the hex file via pickit3 the uploading was successfully but the serial communication didn't work. So I have ordered an other one display, I'm curious the first one was wrong or I'm made a mistake. Tomorrow will arrive.
Thanks again
László

[majenko]

It appears there may have been someissue with the compiler in the repository. You are not alone in habing experienced this. Just this evening I have re-uploaded the compiler packages to the repository in the hope that it will cure the issue. I haven't yeet had a chance to test them myself, since it is now late and my computer is off, but in the morning I shall boot my Windows 10 VM and attempt a full clean install to confirm the packages are now working. Feel free to try them yourself as well.

[sopronil]

Hi James,
Unfortunately in my case the cure didn't help. Any idea? Perhaps if you send me an older version to try?
Regards
László

[majenko]

I have found the root of the problem at last. The compiler itself has some idiotically named files in it that contain a * - that is not exactly a windows friendly filename now is it

AFAICT the badly named files aren't actually needed, so I am filtering them out before building the UECIDE packages now. I'm just building some fresh packages to see if that fixes the problem.

[sopronil]

Hi James,
Pls. let me know if I can download the modified UECIDE.
Looking forward on your reply.
László

[majenko]

I have confirmed the fix for the pic32-tools compiler. You should find an updated version in the plugin manager. By the way, I'm Matt, not James :P