完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
我仍然有密码引擎和WOLFSSL的麻烦。(使用PIC32 MZ2048 EFM144和ValueV2.04),WOLFSSL和Microchip在相关模块中固定了很多东西。现在,它工作得多了一些,但仍然不好。我用它的配置测试了WOLFSLSLTCP服务器的样例项目“PIC32 MZYEFSKYSH HWYCRIPT”。它运行良好,并且(非常小)的网站被加密传输。我使用这个项目作为基础,并通过MHC增加HTTP网络支持和FRIERTOS支持。现在错误开始发生:*经常出现SSLyReRoRyRxReCordOrthooOyLoad。(但是HTTP 200的结果)*对于更大的数据,错误更频繁发生。(我用Microchip网站取代了我自己的网站——一个800 KB的文件几乎从来没有完全传输)*对于像Microchip测试网站这样的小型网站来说,错误也会发生。当我停用硬件加密时,软件加密工作得很好。需要调整密码/ SRC/SET设置。H NoYDH定义不能设置或编译错误发生。有什么建议吗?
以上来自于百度翻译 以下为原文 I am still having trouble with the crypto engine and wolfssl. (Using a PIC32MZ2048EFM144 and HARMony v2.04) As I understand, wolfssl and Microchip fixed a lot of things in the related modules. Now, it works a bit more, but still not well. I tested the sample project wolfssl_tcp_server with its configuration "pic32mz_ef_sk_hw_crypt". It works well and the (very small) website is transmitted encrypted. I used this project as a base and added HTTP-Net support and FreeRTOS support via the MHC. Now the errors starting to happen: * Very often a SSL_ERROR_RX_RECORD_TOO_LONG occurs * More often, the data is simply not loaded completely. (But with a HTTP 200 result.) * The errors happen more often for larger data. (I replaces the microchip website with my own - a file of 800KB is almost never completely transmitted) * For smaller websites like the microchip test website, the errors also happen. When I deactivate the hardware encryption, the software encryption is working fine. When I set the FREERTOS define, I need to adjust the crypto/src/settings.h. The NO_DH define must not be set or compile errors happen. Any suggestions? |
|
相关推荐
8个回答
|
|
HI已经能够创建一个更简单的基于WOLFSLSILTCPB客户端的测试用例。我将与硬件加密人和WOLFSSL一起工作,看看我们是否能找出问题的原因。谢谢你的报道。
以上来自于百度翻译 以下为原文 Hi I've been able to create a much simpler test case based on the wolfSSL_tcp_client. I'll be working with the hardware crypt people and wolfSSL to see if we can figure out what is causing the problems. Thank you for reporting this. |
|
|
|
|
|
|
|
我有一个类似的经验与一个测试项目,其中HTTP服务器(端口= 80)工作良好,但HTTPS服务器(端口= 443)不服务网页(什么都没有发送,没有错误信息)。我终于找到了2个允许它工作的设置:在项目配置选项卡中改变堆大小=64960,用于XC32 LD/一般(在MHC)中改变了MHC中的HTTPNET设置,用于“处理HTML的缓冲区大小等”。从512到2000,我找不到任何文档来解释为什么这2个参数是重要的,但是这对我起了作用。就像把拼图拼在一起,把所有的棋子都放下来。:)
以上来自于百度翻译 以下为原文 I had a similar experience with a test project in which the http server (port=80) worked fine but the https server (port=443) did not serve the web pages (nothing was sent and no error message). I finally found 2 settings that allowed it to work: Changed the heap size = 64960 in the Project Configuration tab for the XC32-ld/general (in MHC) Changed the HTTP_NET setting in MHC for "Size of Buffer for Processing HTML, etc... from 512 to 2000. I could not find any documentation that explained why these 2 parameters are important, but this worked for me. It's like putting a jigsaw puzzle together with all the pieces faced down. :) |
|
|
|
在这个问题上得到更多的数据:你用什么浏览器/操作系统来和EFM对话?你的网络有多忙?董事会是否接触了大量的交通?
以上来自于百度翻译 以下为原文 To get a little bit more data on this issue:
|
|
|
|
还有一件事要做的是关闭硬件哈希。应该有两个地方定义WOLFSLSILPIC32 MZZHASH。一个地方在SyrSyCyFig .h文件的内部。另一个在框架/密码/ SRC/SETPATH的内部。H注释这两个。在硬件哈希关闭时,性能仍然很好。AES/DES/TDES硬件仍被用于一般加密。
以上来自于百度翻译 以下为原文 One more thing to try is to turn off hardware hash. There should be two places WOLFSSL_PIC32MZ_HASH is defined. One place is inside of your system_config.h file. And the other is inside of framework/crypto/src/settings.h. Comment out both of these. Performance still seems to be good with hardware hashing turned off. The AES/DES/TDES hardware is still being used for general encryption. |
|
|
|
谢谢你的提示-但这对我来说不起作用。你也使用了EFM芯片的密码引擎吗?我使用的是Windows 7。浏览器中使用的是Firefox和Chrome。在当前的消费版本中,PIC IST直接连接到一个外部的USB 3.0网卡。所以根本没有其他交通工具。我试过了,但没用。我猜,禁用定义为你工作?
以上来自于百度翻译 以下为原文 Thanks for the hint - but this did not work for me. Did you also use the crypto engine of the EFM chip? I am using Windows 7. The browsers in use are Firefox and chrome. Both in the current consumer version. The PIC ist directly attached to an external USB3.0 network card. So there is no other traffic at all. I tried that, but it did not help. I am guessing, disabling the define worked for you? |
|
|
|
|
|
|
|
FWWW我没有设法让硬件密码与Wolf SSLI合作,最终使硬件加密失败。我和保鲁夫谈过这件事。他们告诉我这个问题已经被修复并传回了Microchip,但还没有达到和谐的程度。我仍然使用和声V1.09。
以上来自于百度翻译 以下为原文 fwiw I didn't manage to get the hardware crypto working with Wolf SSL I ended up disabling hardware crypto. I spoke to Wolf about it - they told me that the issue had been fixed and passed back to microchip, but had not yet made it's way into harmony. I'm still using Harmony V1.09 |
|
|
|
只有小组成员才能发言,加入小组>>
5244 浏览 9 评论
2035 浏览 8 评论
1955 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比?
3214 浏览 3 评论
请问电源和晶体值之间有什么关系吗?PIC在正常条件下运行4MHz需要多少电压?
2261 浏览 5 评论
779浏览 1评论
673浏览 1评论
有偿咨询,关于MPLAB X IPE烧录PIC32MX所遇到的问题
599浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
683浏览 0评论
580浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-25 19:46 , Processed in 1.349936 second(s), Total 92, Slave 76 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号