• AVR Freaks

AnsweredHot!TCP IP with harmony v3

Page: 12 > Showing page 1 of 2
Author
Witek
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2013/02/14 06:56:33
  • Location: Western Australia
  • Status: offline
2020/01/21 01:04:49 (permalink)
0

TCP IP with harmony v3

Hello,
 
So, I thought I would give harmony v3 a go. I want to use it to enable packet fragmentation support in my project, which otherwise works perfoect. I tried to follow the TCPIP migration doc (which I couldn't exactly as I was getting different options), but I got to end, only to find that the code does not compile (error: unknown type name 'WOLFSSL_GLOBAL'). I was half expecting problems, so I wasn't too disappointed.
 
Then I downloaded the "web_net_server_nvm_mpfs" example. It compiled OK. Then I regenerated the code using the code generator (there were 1000's of defferences that had to be merged). Now the example does not compile. I get the same error as with my own project (error: unknown type name 'WOLFSSL_GLOBAL').
 
Avoiding negative comments...
 
Please suggest a solution.
 
Is there a way find and download the snapshot of the repositories that were used to generate the example code?
 
If I can get the example to compile, I am sure I should be able to compile my own project.
 
Also, what are the chances that the LAN8740 driver will work with LAN8720?
 
Thanks
post edited by Witek - 2020/01/21 01:06:56
#1
ric
Super Member
  • Total Posts : 25592
  • Reward points : 0
  • Joined: 2003/11/07 12:41:26
  • Location: Australia, Melbourne
  • Status: online
Re: TCP IP with harmony v3 2020/01/21 01:46:02 (permalink)
0
I've never used Harmony, so this is only a guess.
Plainly WOLFSSL is part of some SSL implementation. Normally I think you have to purchase it, although I'm sure I've seen some reference to Microchip taking out a general licence ot use it on PIC devices.
Nevertheless, have you enabled some SSL options that you didn't have in your old project?
 
 

I also post at: PicForum
Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
NEW USERS: Posting images, links and code - workaround for restrictions.
To get a useful answer, always state which PIC you are using!
#2
Witek
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2013/02/14 06:56:33
  • Location: Western Australia
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 05:16:28 (permalink)
0
Yes, there is every chance I got something wrong. That's why I tried the example. Running the code generator with current repositories makes the ecample no longer compile.

Another thing I noticed is that the files downloaded with the downloading tool are different to what is on github. I dont know how it works
#3
BillP
Super Member
  • Total Posts : 375
  • Reward points : 0
  • Joined: 2014/09/28 07:53:35
  • Location: CA
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 08:48:23 (permalink)
0
I believe that the https server does not work (yet) in Hv3. 
#4
rainad
Moderator
  • Total Posts : 1251
  • Reward points : 0
  • Joined: 2009/05/01 13:39:25
  • Location: 0
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 12:56:32 (permalink)
0
The wolfSSL + wolfCrypt libraries are embedded in the Harmony v3 and the https is up and running.
Start with an existing out of the box demo that uses wolfSSL - web_net_server_nvm_mpfs, for example
That should build and run fine.
Then start the MHC and regenerate that demo, checking all the differences as you regenerate.
There shouldn't be any differences. If they are, then please check the Harmony net 3.5 release notes and make sure that you have the correct dependencies for the net repository (core, csp, wofSSL, wolfCrypt, etc., etc.)
 
 
#5
Witek
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2013/02/14 06:56:33
  • Location: Western Australia
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 16:21:10 (permalink)
0
This is exaclty what I did. That demo project compiled ok. But regeneration caused 1000's of differences. I could not go through all of them. After that it would not compile.
 
I downloaded the latest packages and examples using the content manager.
 
Have I missed something?
#6
NKurzman
A Guy on the Net
  • Total Posts : 18266
  • Reward points : 0
  • Joined: 2008/01/16 19:33:48
  • Location: 0
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 16:53:55 (permalink)
0
caused 1000's of differences. and?  
is only 100's better?
post some? what is the Nature of the Differences?
#7
Witek
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2013/02/14 06:56:33
  • Location: Western Australia
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 17:16:53 (permalink)
0
In this case less is better.
 
I am not complaining that there are differences. I am complaining that at the end of the process the code does not compile. The number of differences is just an observation I made and to me it indicates that there is something fundamentally wrong. I think, Rainad confirmed it by suggesting that there should not be too many of them.
#8
NKurzman
A Guy on the Net
  • Total Posts : 18266
  • Reward points : 0
  • Joined: 2008/01/16 19:33:48
  • Location: 0
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 17:53:31 (permalink)
0
My Point is how can any one help you if you are effectively saying "It's Broken" with no details?
to be Clear
The Project is web_net_server_nvm_mpfs
You can compile it as is when it is new. (No Changes)
You Run MHC 3 on that project with no changes.
You Click the Generate Code Button and You get 100s of Merge differences?
You Try to Compile again and Now get 100s of Errors?
#9
Witek
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2013/02/14 06:56:33
  • Location: Western Australia
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 18:48:57 (permalink)
0
Yes, you have very well summarised what I already said twice (looks like my explanations were quite clear).
and no, I don't think I just said "it's broken" (see previous line)
 
in addition, when trying to compile the first error that pops up is:
error: unknown type name 'WOLFSSL_GLOBAL'
 
which I have also mentioned.
 
Please, do let me know if you need any more info from me.
 
I could have copied in the compile error log and all the differences that I got when generating the code to make the post 100 pages long. But I wanted good helpers (like yourself) to read it, so I kept it to minimum.
 
 
#10
NKurzman
A Guy on the Net
  • Total Posts : 18266
  • Reward points : 0
  • Joined: 2008/01/16 19:33:48
  • Location: 0
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 19:01:08 (permalink)
0
You are Asking Strangers to look in to your Problem.  Why the Attitude?  Do I owe for some past issue you helped me with?  Maybe Tomorrow I will try and see if I get the same Results.
 
You can Put in a Support Ticket if you want Direct Help from Microchip.  Though there is one Post from a Microchip Engineer here.  
WOLFSSL is the Network Encryption Library.  Is it checked on the list of thing to include?
 
Are all your Issues WOLF SSL  was what I was trying to determine.  It does not take alot to make a thousand Errors.  Sometimes a semi-colon will do it
 
 
#11
Witek
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2013/02/14 06:56:33
  • Location: Western Australia
  • Status: offline
Re: TCP IP with harmony v3 2020/01/21 22:01:36 (permalink)
0
I would really appreciate if you did check, it would add more weight to the ticket.
 
Looks like the errors are WOLF SSL related.
 
I manually downloaded a file from WOLF SSL github which defined WOLFSSL_GLOBAL (the original error). Now the error is: error: 'WOLFSSL_X509' has no member named 'notBeforeSz'.
 
It looks like if I downloaded the files myself it would eventually work, but I dont think that the microchip team intended it to be this way.
 
PS
No Attitude. Just politely responding (with justification) to your "you are effectively saying "It's Broken" with no details" comment, as I did not believe it was called for.
#12
rainad
Moderator
  • Total Posts : 1251
  • Reward points : 0
  • Joined: 2009/05/01 13:39:25
  • Location: 0
  • Status: offline
Re: TCP IP with harmony v3 2020/01/22 07:28:18 (permalink)
0
If you're getting differences when you regenerate the project, most likely you're using different versions of the repositories than that net project is expecting.
As listed in the net release notes, the list of package requirements:
Then check that what you have downloaded on your machine matches exactly.
After that we'll know where to look for more info.
 
#13
Witek
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2013/02/14 06:56:33
  • Location: Western Australia
  • Status: offline
Re: TCP IP with harmony v3 2020/01/22 18:42:27 (permalink)
0
Thanks for that. I changed wolfssl back to 4.1.0, and now the example compiles OK.
 
That sorts me out in this regard, but should new versions break things this bad?
 
Also, I notice that there is no LAN8720 driver in Hv3. Would you risk to say whether the available LAN8740 driver could work with the LAN8720 part?
#14
NKurzman
A Guy on the Net
  • Total Posts : 18266
  • Reward points : 0
  • Joined: 2008/01/16 19:33:48
  • Location: 0
  • Status: offline
Re: TCP IP with harmony v3 2020/01/22 18:57:14 (permalink)
0
"I changed wolfssl back to 4.1.0"?  So you changed WolfSSL ? It is not in your list of things you did.
You would need to compare the Versions of WolfSSL to see what changed.
#15
Witek
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2013/02/14 06:56:33
  • Location: Western Australia
  • Status: offline
Re: TCP IP with harmony v3 2020/01/22 19:23:42 (permalink)
0
Thanks
post edited by Witek - 2020/01/22 19:28:19
#16
NKurzman
A Guy on the Net
  • Total Posts : 18266
  • Reward points : 0
  • Joined: 2008/01/16 19:33:48
  • Location: 0
  • Status: offline
Re: TCP IP with harmony v3 2020/01/22 19:28:16 (permalink)
0
I was Trying to help.  You think you are being very clear, I do not believe so.
 
You have you answer so. There is no need for me to invest anymore time in this thread.
#17
Witek
Starting Member
  • Total Posts : 34
  • Reward points : 0
  • Joined: 2013/02/14 06:56:33
  • Location: Western Australia
  • Status: offline
Re: TCP IP with harmony v3 2020/01/22 19:32:19 (permalink)
0
Thanks for your time anyway.
#18
rainad
Moderator
  • Total Posts : 1251
  • Reward points : 0
  • Joined: 2009/05/01 13:39:25
  • Location: 0
  • Status: offline
Re: TCP IP with harmony v3 2020/01/23 07:45:28 (permalink) ☼ Best Answerby Witek 2020/01/23 16:51:18
5 (1)
Witek
That sorts me out in this regard, but should new versions break things this bad?

That's the purpose of listing the required package versions. When we release the net stack and demos we use specific stable versions of all the other dependencies (which are developed and tested separately).
If you ignore this, then you need to do the adjustments yourself.
However, the download manager should take care of that for you and at least warn that something is not right.
Not sure why it doesn't though.
 
Witek
Also, I notice that there is no LAN8720 driver in Hv3. Would you risk to say whether the available LAN8740 driver could work with the LAN8720 part?

Yes, you can use the 8740 driver with no problems.
The 8720 will be added as part of the next release.
 
#19
BillP
Super Member
  • Total Posts : 375
  • Reward points : 0
  • Joined: 2014/09/28 07:53:35
  • Location: CA
  • Status: offline
Re: TCP IP with harmony v3 2020/01/25 14:31:09 (permalink)
0
Thanks @rainad and witek for the clues to implement an https server.  I, too, downloaded the latest software components from github (using the download manager in Harmony)for the Harmony software components.  Then I got the 1000's of compile errors.  Went back to the link rainad gave and saw the wolfSSL 4.1.2 -stable version and downloaded the zip file.  Unzipped it, renamed the original wolfssl folder in the Harmony project and copied the 4.1.2-stable folder to the same place in the Harmony project.  Tried the compile and it failed! There is a hidden requirement to include the sntp module in the TCPIP library.  Did this and everything compiled.  Did a test for http (port 80) and that worked.  Changed the port to 443 and got the following error on Safari "Error code: SEC_ERROR_REUSED_ISSUER_AND_SERIAL".  I also tried Chrome and Firefox. Neither of these two even worked at all.  

Apparently I am missing a step for something like cert verification or ???  Any ideas anyone?
#20
Page: 12 > Showing page 1 of 2
Jump to:
© 2020 APG vNext Commercial Version 4.5