Core UART serial ports on Z8350

A place to talk about all the Operating Systems, Software & Hardware
Forum rules

- Posts are to be made in the relevant forum. Users are asked to read the forum descriptions before posting.

- Members should post in a way which is consistent with "normal writing". That is users should not post excessive numbers of emoticons, large, small or coloured text, etc. Similarly users should not SHOUT or use excessive punctuation (e.g. ! and ?) in topic titles or posts.

- Members should use an appropriate, descriptive subject when posting a new topic. Examples of bad subjects include; "Help me!", "I'm stuck!", "I've got an error!", etc. Examples of good subjects include; "Getting an TABLE FULL error upon login", "Cannot restore a backup".

- Members are asked to post in English only so that posts can be well received and properly monitored.

- Spam is not tolerated here under any circumstance. This includes offering hosting services (charged and free), installation services, solicitation etc. Recruiting members for your own projects (moderators, designers, professional MOD work, etc.) is not permitted and is also considered spam. Users posting spam will be warned and their post removed.

- Members should post in a way that is respectful of other users. Flaming or abusing users in any way will not be tolerated and will lead to a warning. Vulgar language and inappropriate material is not allowed and will be removed. We try to maintain a family friendly atmosphere whenever it is possible within the main subject matter of this community. Please keep this in mind when participating.

- Each user is allowed to create one account. If you would like to change your username, please contact us and, most likely, we can do it for you while you can keep all of your profile data, posts, and other content.

- If a user violates our guidelines and shows a disregard for them, our staff and our community, they run the risk of losing their account. We reserve the right to deactivate any account and to edit or remove any content without warning. These guidelines are subject to change at any time without notice.

Thank you for visiting LattePanda.com!
User avatar
hvguy
Posts: 2
Joined: Sun Jul 22, 2018 8:16 pm

Sun Jul 29, 2018 7:58 pm

Hi Lutz,

I would like to see that as well! I am getting the impression that LattePanda admin does not know how to do this. That wouldn't be to bad if they could provide us with other references with which to figure it out.

My concern is that these features may not be supported in the BIOS and therefore difficult to use in windows. However, since we have no information, everything is a guess.

LattePanda can you please tell us:

-Has anyone at LattePanda ever used these pins?
-The physical pins on the CPU which GNSS and I2C connect to
-If the BIOS is even capable of accessing their registers
-If any software exists that uses these features (like GPS or something)

User avatar
Lutz
Posts: 214
Joined: Mon Apr 18, 2016 4:30 am
Location: Germany, NRW

Mon Jul 30, 2018 6:22 am

Hi hvguy,

oh, yes, the BIOS, I forgot.
I am an experienced developer of microcontroller circuits, but I know little about the inner structure of a PC.
Maybe that's why I don't understand why drivers for the second serial and the two I2C are such a problem.
But in the meantime I fear that we will have the same problems with the Alpha and Delta...

(Translation German-English by deepL)

User avatar
LattePanda
Site Admin
Posts: 2523
Joined: Wed Jan 20, 2016 9:09 am

Wed Aug 01, 2018 6:36 am

Thanks for all your explanation! I've got some screenshots of the schematics. Let me attach the related info you requested.
10 CPU pins from interface.png
10 CPU pins from interface.png (93.97 KiB) Viewed 3226 times
SOC pinout.png
SOC pinout.png (416.96 KiB) Viewed 3226 times
SOC pinout 2.png
SOC pinout 2.png (403.52 KiB) Viewed 3226 times
From these picture, my understanding is:
1. PIN 5 and 7 are multi function interface, including DDI2_DDC_IIC, UART0 and INTD_DSI feature (SOC pinout 2), which may explain why @Lutz can make serial works. Could you please recommend a better and clear way to show these info via our pinout diagram? I can organize our content development team to change following your professional suggestions!
2. PIN 6 and 8 comes from HSUART (SOC pinout) UART2 TXD/RXD, which still lakes of the driver support like COM1. - I will need to talk with our RD team!
3. Lake of sample for driving I2C_0 and I2C_2 interface. - I will check with RD team also with this point!

About the I2C sample support, what kind of common accessories will you interest in connecting with LattePanda via these pins!?

Look forward to your suggestion. And let's make some changes together! Thanks indeed for your kindness!
Enjoy Tinkering with LattePanda ! :lol:

User avatar
doanldshimoda
Posts: 7
Joined: Sun Jul 22, 2018 8:47 pm

Fri Aug 03, 2018 4:31 pm

LattePanda wrote:
Sun Jul 29, 2018 4:20 pm

Look forward to your suggestion!
Is very easy. If you dont have time (?) to dcument correctly the connections on late panda just do as any other IOT company : Share your schematics. If your concern is somebody can clone the board or some like that let me say thats silly. Nobody will compite with you because the price is very low vs specifications.

Is impossible we must ask in forums to get the information. That is expected only on extrange procedures, never in fnd a serial port pinoput, or trying to install a OS on latte panda...

I suspect your problem is your engineers are chinese and dont speek english, that happen to me many times with another companies. Well , sorry my friend but if you dont improve your support and coumentations your market will be lower and lower, dont care how much good is your hardware.

I hope you take well my sugestions.

Best regards.

P.S. yes... and you don just a few minutes after my post. Great news. I hope your engineers be more open mind and let grow late panda.

User avatar
Lutz
Posts: 214
Joined: Mon Apr 18, 2016 4:30 am
Location: Germany, NRW

Sat Aug 04, 2018 9:07 am

I think the first problem is the different markets for which LP is now active.
On the one hand the market for hobbyists and on the other hand the market for professionals. Both expect different functions and therefore different documentation and different communication.

In addition, the technology of a PC is very complex. This starts with the hardware and goes through BIOS functions up to the operating system.
I don't know for whom the LP was intended at first, but at the beginning it was advertised more for hobbyists as a "ready-to-use-WINDOWS10-PC".
That a lot of other people (professional equipment manufacturers like me, for example) discovered the LP was probably not expected.

The next problem might be the way engineers think.
Never let an engineer write an instruction manual...
But also a pure marketing person must never be the only contact to customers for a highly technical product! (and different types of customers)

Back to your actual documentation :
The publication of the complete circuit diagram is not necessary in my opinion. But a few more details about the pins of the visible connectors.
( By "visible" I mean ALL connectors that can be seen on the board, not only those in the drawing! )

Current drawing in http://docs.lattepanda.com/content/hard ... ndOutputs/ :
- Draws the rectangles for "U1" and "U2" again.
- Names the pins 5+7 in the drawing only with UART0TX+RX
- Names pins 6+8 in the drawing only with UART2TX+RX
In the text under "Pinouts in area U1 are ..."
- Text that names UART0 as COM1 and UART2 as COM2 (as soon as the driver for COM2 works).
(Publish COM1 because this seems to be the standard function on delivery)
- A table with the assignments of the connector pins to the CPU pins.
Or
The note that the table with the used CPU pins is only available on request. Because this information is only useful for very experienced users who want to change the BIOS.

In addition, an overview of how the Arduino and the PC part are connected could help to clarify some questions among the "non-technicians" among the customers.

To the I2C example :
For me, a standard PIO (PCA9555A, also runs at 1.8V) would suffice as a "blink" example.
The PCF8574 is better known, but needs at least 2.5 V as power supply.
For example programming of a repeat-Read or -Write maybe an EEPROM like AT24C256B (also runs with 1,8V)

(German-English translation by deepL)

User avatar
Lutz
Posts: 214
Joined: Mon Apr 18, 2016 4:30 am
Location: Germany, NRW

Tue Aug 07, 2018 7:21 am

Lutz wrote:
Sat Aug 04, 2018 9:07 am
(...)
In addition, an overview of how the Arduino and the PC part are connected could help to clarify some questions among the "non-technicians" among the customers.
(...)
and here is the next customer with a question on this topic:
https://www.lattepanda.com/topic-f5t16102.html

User avatar
LattePanda
Site Admin
Posts: 2523
Joined: Wed Jan 20, 2016 9:09 am

Sat Aug 11, 2018 7:06 am

doanldshimoda wrote:
Fri Aug 03, 2018 4:31 pm

Is very easy. If you dont have time (?) to dcument correctly the connections on late panda just do as any other IOT company : Share your schematics. If your concern is somebody can clone the board or some like that let me say thats silly. Nobody will compite with you because the price is very low vs specifications.
You've seen our problem. But we should change, learn, grow and face the problem. That's the culture of our team and that's my understanding of maker spirit.

Let me organize our engineering team to see if we can open our schematics for 1st gen products and further version products via our docs!
I think the key obstacle is that a part of design is Intel confidential content...

We will update the process here.
Enjoy Tinkering with LattePanda ! :lol:

User avatar
LattePanda
Site Admin
Posts: 2523
Joined: Wed Jan 20, 2016 9:09 am

Sat Aug 11, 2018 7:28 am

Lutz wrote:
Sat Aug 04, 2018 9:07 am
I think the first problem is the different markets for which LP is now active.

Back to your actual documentation :
The publication of the complete circuit diagram is not necessary in my opinion. But a few more details about the pins of the visible connectors.
( By "visible" I mean ALL connectors that can be seen on the board, not only those in the drawing! )
We started from supporting developers and makers to inspire creativity with cool, powerful development tools. And we see clear and strong market requirement from commercial and industry market. We've worked with several commercial partners to design deeply optimized industrial products for them. So you can see when developing LattePanda Alpha and Delta. We're trying to balance the need between desktop scenarios and commercial needs, which make it possible for small business partners to use our standard products for their innovation in their industry. However we still open the customization service for partners, who have big batch order capabilities.

Anyway, you're definitely right on our market situation now. And we really appreciate your suggestions about the documentation and content! I've forwarded your suggestions to our product team.

They will optimize the content based on your suggestions.
Enjoy Tinkering with LattePanda ! :lol:

User avatar
Ewutru
Posts: 4
Joined: Wed Feb 19, 2020 8:27 am

Mon Mar 16, 2020 10:56 am

@LattePanda Is there already any information about this?

I would like to communicate with the cpu and arduino over I2C as the serial connection can bottleneck my data speedrate....
The arduino uses a SPI to CAN converter, with serial limiting my baud-rate to 100kb/s.

Post Reply