Posts made by mangogeek

Rohs证书：
CE：
FCC：
等待添加

@figaro 在 MT7688AN + PCIE 中说：

？

我没有啊，你 AT libc0607 试试？

@jonsmirl 我们并没有做S3的开发板，HQ这款挺不错的，性价比很高。

@jonsmirl R11的价格和S3L是几乎一致的，其实我更喜欢S3L，在同样晶园的基础上引出了更多的资源。（R11是合作的项目，并不是我们自己选择的）

@jonsmirl V3的SDK一直没更新吗？

第二代芯片手册在此： https://sns.widora.io/topic/614/sd-nand-flash-csnp1gcr01-amw-二代
淘宝购买地址：https://item.taobao.com/item.htm?id=602856522887

CSNP1GCR01-AMW二代.pdf
性能

之前用1代（后缀BMW）在7688上的测试数据： https://sns.widora.io/topic/543/收到了3片sop8封装的sd卡芯片-读11-3mb-s-写5-5mb-s-mt7688/7

SDK没有更新，目前代理不允许把SDK放到网上来

@jonsmirl 没听过R331，只知道一个R311：http://www.allwinnertech.com/index.php?c=product&a=index&id=84

但是他们还有一款未正式发布的芯片，可以认为是将 A33 和一颗DDR3颗粒SIP到一起，针对高端HMI市场。 不知你是否感兴趣？

Allwinner_R11_Datasheet_V1.0.pdf

R11和V3S很像，只不过V3S的RGB接口和CSI是复用关系，R11分开了。
也就是R11可以同时支持RGB，CSI，MIPI。

R11是全志针对HMI市场推出的性价比方案。我们这款R11开发套件会在10月初上架到 https://www.rt-thread.org

首先，重新编译op，将Kernel modules ---> USB Support ---> 下的
kmod-usb-net
kmod-usb-net-rndis

kmod-usb-serial
kmod-usb-serial-wwan
打开

AT端口是ttyUSB2，但必须要修改内核里usb-serial才行。修改地方参考官方资料：http://ask.openluat.com/article/37
我懒得改了，直接测rndis。
启动后，看log

  rndis_host 1-1:1.0 eth1: register 'rndis_host' at usb-101c0000.ehci-1, RNDIS device, ac:62:4f:1f:3a:9d

发现新注册了eth1，我们手动将eth1添加到network中的wan部分。
/etc/config/network

config interface 'wan'
        option force_link '1'
        option macaddr '0c:ef:af:d2:a9:f2'
        option proto 'dhcp'
        option ifname 'eth1'

在nr一下（/etc/init.d/network restart)
ifconfig eth1

root@Widora:~# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 0C:EF:AF:D2:A9:F2  
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::eef:afff:fed2:a9f2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:40 errors:0 dropped:0 overruns:0 frame:0
          TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3715 (3.6 KiB)  TX bytes:15194 (14.8 KiB)

我们在7688中先尝试ping qq.com

root@Widora:~# ping qq.com
PING qq.com (111.161.64.40): 56 data bytes
64 bytes from 111.161.64.40: seq=0 ttl=53 time=21.816 ms
64 bytes from 111.161.64.40: seq=1 ttl=53 time=19.773 ms
64 bytes from 111.161.64.40: seq=2 ttl=53 time=19.538 ms
64 bytes from 111.161.64.40: seq=3 ttl=53 time=15.324 ms
^C
--- qq.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 15.324/19.112/21.816 ms

此时，ifconfig eth0，发现已经获取IP地址，电脑通过NEO的网口连接，可正常浏览网页，我们测个速。

懒人固件： openwrt-ramips-mt7688-WIDORA32128-squashfs-sysupgrade.bin

值得一提的是上网和测试，CPU使用率一直极低，这应该是rndis接口的好处吧。

像是依赖问题，安装 build-essential 后试试，按照： https://cn.doraiot.com/compile 检查依赖包
这个错误很像ubuntu18+版本上的问题，实在不行就用ubuntu16.04

运行make -j1 V=s后再看log

datasheet:
esp32-s2_datasheet_en.pdf

esp32-s2_datasheet_cn.pdf

where ?

出差回来，现在已经在批产PCB了哈

一把点亮

4.3寸电容屏

7寸电容屏

焊接回来，简单测试了电源和usbboot，正常。

@sblpp 板子漂亮这个我们很接受，谢谢了，
但网站主页（widora.io)快被骂死了，改了N次了。

@sblpp 看到了，或许GD5F1GQ4UAYIG也行。记得还有个ATO品牌的我咨询一下货。

ubuntu16.04 编译openwrt_widora遇到这个问题，补丁来自：
https://github.com/openwrt/openwrt/commit/70b104f98c0657323b28fce140b73a94bf3eb756#diff-ad001f3a51a1d957d5013650f14df0cb
手动在tools/mkimage/patches/下增加该文件即可。

@sblpp 支持常规SPI-NAND？我没注意。有推荐的型号吗？

@sblpp 谢谢夸奖
样片在焊接，大概周四到手测试，接下来用最快速度焊接首批300套。

@suguotao 那些引脚是P1-P4的网口指示灯。

涉及脚本：
/usr/bin/ethmode
启动时会被调用，根据flash中的标志位设置网口和网络模式：
/etc/init.d/setnetmode

所以关注如下语句即可：
reg w 10000064 0x0
reg w 1000003c 0xe001ff

fix https://github.com/widora/openwrt_widora/commit/bafe106dfa77d7e7743562da44b22f71da752148

spec	esp32	esp32s2
CPU	single core or dual core LX6	single core LX7
SRAM	520KB	320KB
ROM	448KB	128KB
ext spi-ram support	8MB	128 MB total(not confirm)
ext spi-flash support	16MB	1 GB(not confirm)
GPIOs	34	43
Cap Touch IO	10	14
PKG	QFN48 66 or 55 or 7*7	QFN56 7*7
WiFi	802.11 b/g/n	802.11 b/g/n and TOF(Time-of-Flight)
BT	v4.2 BR/EDR/BLE	None
LCD	None	8/16/24bit parallel RGB/8080/6800
i2s	2	1
DVP	8 or 16-bit in i2s0 or i2s1	8 or 16-bit in i2s0
USB	None	Full speed USB OTG
SDIO	Yes	None
SPI	4	4
ETH	Yes	None

@gomibako 感觉应该是用来代替8266的

项	esp32	esp32s2
I2S	2	1(DVP)
SPI		4 (master 80Mhz,slave 40Mhz)

虽然不是MT7615，但还是相当牛逼！

项	esp32	esp32s2
CPU	单核或双核LX6	单核LX7
SRAM	520KB	320KB
ROM	448KB	128KB
可被映射的外部spi-ram支持	8MB	128 MB total(等待确定)
可被映射的外部flash支持	16MB	1 GB(等待确定)
GPIO数量	34	43
支持电容触摸的IO	10	14
封装	QFN48 66 or 55 or 7*7	QFN56 7*7
WiFi	802.11 b/g/n	802.11 b/g/n and TOF(Time-of-Flight)
BT	v4.2 BR/EDR/BLE	None
LCD	None	8/16/24bit parallel RGB/8080/6800
DVP	in i2s0 or i2s1	8 or 16-bit DVP in i2s0
USB	None	Full speed USB OTG
SDIO	Yes	None
ETH	Yes	None

关于LX7，有国外的一段描述：https://hackaday.com/tag/esp32-s2/
与我们所熟知和喜爱的ESP32相比，存在一些差异。 ESP32-S2使用单核Xtensa LX7内核，运行频率高达240 MHz，目前ESP32使用单核或双核LX6。 这些核心之间的差异隐藏在营销演讲和新闻稿中，但看起来LX7核心能够在每个周期进行更多浮点运算：LX6显然有2个FLOPS /周期，但LX7有64个FLOPS /周期。 这对于DSP和其他计算量很大的应用来说非常棒。 芯片上的其他功能包括320 kB SRAM，128 kB ROM和16 kB RTC存储器。

https://www.youtube.com/watch?v=WALZBQPb_1A

和目前的esp32相比，砍掉了蓝牙，但增加了四个实用外设：
1、USB-OTG
2、LCD驱动接口
3、DVP接口
4、WiFi包的空中时间检测，TOF（Time-of-Flight），应该和测距、定位有关。
还有一个不疼不痒的是更优异的功耗特性

一个开发板，两个模组，两颗芯片（有手写的序号）

开发板

模组

预发布的工具链：
windows：https://dl.espressif.com/dl/toolchains/preview/xtensa-esp32s2-elf-gcc8_2_0-esp32s2-dev-4-g3a626e-win32.zip
mac：https://dl.espressif.com/dl/toolchains/preview/xtensa-esp32s2-elf-gcc8_2_0-esp32s2-dev-4-g3a626e-macos.tar.gz
linux32bit：https://dl.espressif.com/dl/toolchains/preview/xtensa-esp32s2-elf-gcc8_2_0-esp32s2-dev-4-g3a626e-linux-i686.tar.gz
linux64bit：https://dl.espressif.com/dl/toolchains/preview/xtensa-esp32s2-elf-gcc8_2_0-esp32s2-dev-4-g3a626e-linux-amd64.tar.gz
IDF工程（截止到20190803仍然作为一个分支存在）
git clone --recursive -b feature/esp32s2beta https://github.com/espressif/esp-idf.git
截止到20190803，软件包状态：

• 目前在ESP-IDF中发布的ESP32-S2 Beta支持仅支持基本功能。 Espressif固件开发人员正在努力研究剩余的支持，因此请定期检查feature / esp32s2beta分支以获取更新。
• 不支持全速USB OTG外设
• 外围驱动程序正在进行中
• 没有省电模式
• 没有硬件安全功能或加密加速器支持
• 不支持使用普通Wi-Fi数据包进行飞行时间（TOF）测量

from https://www.esp32.com/viewtopic.php?t=11265
Espressif is distributing a small number of ESP32-S2 Beta-DevKitC V1.1 to customers and community members. This gives people a chance to begin exploring the features of the forthcoming ESP32-S2.

Read the ESP32-S2 announcement

The ESP32-S2 Beta chip is not the same as the final ESP32-S2, the Beta chip is an engineering sample and as a result not all features are available. Software support is still being developed ahead of the final ESP32-S2 release (see the "Limitations" section below).

Set up for CMake

CMake will become the default build system in IDF V4.0 and is the only build system with multiple chip target support.

The setup process for ESP-IDF with CMake is here:
https://docs.espressif.com/projects/esp-idf/en/feature-esp32s2beta/get-started-cmake/index.html

Follow the same Getting Started process before starting to work with the new ESP32-S2 Beta chip.

If you were previously using GNU Make build system, you will need to install additional software as described in the Getting Started guide.

Get the ESP32-S2 toolchain

The ESP32-S2 toolchain version may be updated again before the final release, but you can get a pre-release toolchain here:

Windows
macOS
Linux 64-bit x86
Linux 32-bit x86
The toolchain tuple is xtensa-esp32s2-elf-, for example gcc for this target is named xtensa-esp32s2-elf-gcc.

Unpack the toolchain archive somewhere and add the bin subdirectory to your PATH, same as described in Getting Started guide for ESP32.

Check out feature/esp32s2beta branch

ESP32-S2 Beta support is not yet merged into the IDF master branch. Instead it is in the feature/esp32s2beta branch.

For an existing ESP-IDF installation:

cd $IDF_PATH
git fetch
git checkout feature/esp32s2beta
git submodule update --init --recursive

For a new ESP-IDF installation:

git clone --recursive -b feature/esp32s2beta https://github.com/espressif/esp-idf.git

(Before continuing, please make sure to have followed the remaining Get Started steps for CMake build system such as installing host tools, setting PATH and IDF_PATH environment variables, etc.)

Building a project for ESP32-S2 Beta target

Important: Support for ESP32-S2 Beta is a work in progress. Not all drivers, examples, etc. are supported in ESP-IDF yet. For our initial example we will use the HTTP request "protocol" example.

Linux/macOS users:

cd $IDF_PATH/examples/protocols/http_request
rm -rf sdkconfig build
idf.py -D IDF_TARGET=esp32s2beta menuconfig
idf.py build

Windows Command Prompt users:

Note: There are currently some issues building under Windows. This post will be updated when they are resolved.

cd %IDF_PATH%\examples\protocols/http_request
del sdkconfig build
idf.py -D IDF_TARGET=esp32s2beta menuconfig
idf.py build

To flash and watch output from the new board:

idf.py -p port-name flash monitor

(Replace port-name with COM4 or /dev/ttyUSB0 or similar name of the serial port connected to the ESP32-S2beta chip.)

You should see output similar to the following:

esptool.py v2.7-dev
Executing action: flash
Choosing default port /dev/ttyUSB0 (use '-p PORT' option to set a specific serial port)
Running esptool.py in directory /builds/esp/32/idf/examples/protocols/http_request/build
Executing "/builds/esp/env/bin/python /builds/esp/32/idf/components/esptool_py/esptool/esptool.py -p /dev/ttyUSB0 -b 921600 --after hard_reset write_flash @flash_project_args"...
esptool.py -p /dev/ttyUSB0 -b 921600 --after hard_reset write_flash --flash_mode dio --flash_freq 40m --flash_size 2MB 0x8000 partition_table/partition-table.bin 0x10000 http-request.bin 0x1000 bootloader/bootloader.bin
esptool.py v2.7-dev
Serial port /dev/ttyUSB0
Connecting.....
Detecting chip type... ESP32S2beta
Chip is ESP32S2 Beta
Features: Prerelease Silicon
Crystal is 40MHz
MAC: 18:fe:34:71:a4:b0
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Compressed 3072 bytes to 82...
Wrote 3072 bytes (82 compressed) at 0x00008000 in 0.0 seconds (effective 7121.2 kbit/s)...
Hash of data verified.
Compressed 617744 bytes to 349616...
Wrote 617744 bytes (349616 compressed) at 0x00010000 in 6.0 seconds (effective 819.4 kbit/s)...
Hash of data verified.
Compressed 19040 bytes to 11419...
Wrote 19040 bytes (11419 compressed) at 0x00001000 in 0.1 seconds (effective 1165.4 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
Executing action: monitor
Running idf_monitor in directory /builds/esp/32/idf/examples/protocols/http_request
Executing "/builds/esp/env/bin/python /builds/esp/32/idf/tools/idf_monitor.py -p /dev/ttyUSB0 -b 115200 --toolchain-prefix xtensa-esp32s2-elf- /builds/esp/32/idf/examples/protocols/http_request/build/http-request.elf -m '/builds/esp/env/bin/python' '/builds/esp/32/idf/tools/idf.py' '-D' 'IDF_TARGET=esp32s2beta'"...
--- idf_monitor on /dev/ttyUSB0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ESP-ROM ver:v1.0.1
Build:Nov 22 2018 17:03:19
rst:0x1 (POWERON_RESET),boot:0x8 (SPI_FAST_FLASH_BOOT)
PC:0x00000000
configspi: 0x00000000, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff50f0,len:0x4
load:0x3fff50f4,len:0x1688
load:0x40022000,len:0x1c78
load:0x40024000,len:0x16f4
entry 0x40024340
I (33) boot: ESP-IDF v4.0-dev-839-g8805b25ef-dirty 2nd stage bootloader
I (33) boot: compile time 15:34:56
I (35) boot: Enabling RNG early entropy source...
I (40) boot: SPI Speed      : 40MHz
I (44) boot: SPI Mode       : DIO
I (48) boot: SPI Flash Size : 2MB
I (52) boot: Partition Table:
I (56) boot: ## Label            Usage          Type ST Offset   Length
I (63) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (71) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (78) boot:  2 factory          factory app      00 00 00010000 00100000
I (86) boot: End of partition table
I (90) esp_image: segment 0: paddr=0x00010020 vaddr=0x3ffd0000 size=0x024a4 (  9380) load
I (101) esp_image: segment 1: paddr=0x000124cc vaddr=0x40028000 size=0x00400 (  1024) load
0x40028000: _WindowOverflow4 at /builds/esp/32/idf/components/freertos/xtensa_vectors.S:1778

I (108) esp_image: segment 2: paddr=0x000128d4 vaddr=0x40028400 size=0x0c8c0 ( 51392) load
I (133) esp_image: segment 3: paddr=0x0001f19c vaddr=0x00000000 size=0x00e74 (  3700) 
I (135) esp_image: segment 4: paddr=0x00020018 vaddr=0x3f000018 size=0x11750 ( 71504) map
I (159) esp_image: segment 5: paddr=0x00031770 vaddr=0x00000000 size=0x0e8a0 ( 59552) 
I (175) esp_image: segment 6: paddr=0x00040018 vaddr=0x40080018 size=0x66cc8 (421064) map
0x40080018: _stext at ??:?

I (297) boot: Loaded app from partition at offset 0x10000
I (297) boot: Disabling RNG early entropy source...
I (297) spiflash: Instruction cache 	: size 8KB, 8Ways, cache line size 64Byte
I (305) cpu_start: Pro cpu up.
I (309) cpu_start: Single core mode
I (313) heap_init: Initializing. RAM available for dynamic allocation:
I (320) heap_init: At 3FFB4000 len 00004000 (16 KiB): DRAM
I (326) heap_init: At 3FFD8290 len 0001FD70 (127 KiB): DRAM
I (333) heap_init: At 3FFFCDA0 len 00003260 (12 KiB): DRAM
I (339) cpu_start: Pro cpu start user code
I (21) cpu_start: Starting scheduler on PRO CPU.
I (62) wifi: wifi driver task: 3ffdbbbc, prio:23, stack:3584, core=0
I (62) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (62) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE
I (82) wifi: wifi firmware version: 0fca7cf
I (82) wifi: config NVS flash: enabled
I (82) wifi: config nano formating: disabled
I (82) wifi: Init dynamic tx buffer num: 32
I (92) wifi: Init data frame dynamic rx buffer num: 32
I (92) wifi: Init management frame dynamic rx buffer num: 32
I (102) wifi: Init management short buffer num: 32
I (102) wifi: Init static rx buffer size: 1600
I (102) wifi: Init static rx buffer num: 10
I (112) wifi: Init dynamic rx buffer num: 32
I (112) example_connect: Connecting to MySSID...
I (252) phy: phy_version: 10, 6afee14, Jun 14 2019, 20:56:06, 0, 2
I (252) wifi: enable tsf
I (252) wifi: mode : sta (18:fe:34:71:a4:b0)
I (382) wifi: new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (1362) wifi: state: init -> auth (b0)
I (1412) wifi: state: auth -> assoc (0)
I (1412) wifi: state: assoc -> run (10)
I (1462) wifi: connected with MySSID, channel 1, bssid = 5c:93:a2:e3:7c:95
I (1462) wifi: pm start, type: 1

I (2082) tcpip_adapter: sta ip: 192.168.0.174, mask: 255.255.255.0, gw: 192.168.0.1
I (2082) example_connect: Connected to MySSID
I (2092) example_connect: IPv4 address: 192.168.0.174
I (2112) example: DNS lookup succeeded. IP=93.184.216.34
I (2112) example: ... allocated socket
I (2502) example: ... connected
I (2502) example: ... socket send success
I (2502) example: ... set socket receiving timeout success
HTTP/1.0 200 OK
Cache-Control: max-age=604800
Content-Type: text/html; charset=UTF-8
Date: Mon, 01 Jul 2019 05:44:39 GMT
Etag: "1541025663+ident"
Expires: Mon, 08 Jul 2019 05:44:39 GMT
Last-Modified: Fri, 09 Aug 2013 23:54:35 GMT
Server: ECS (oxr/8314)
Vary: Accept-Encoding
X-Cache: HIT
Content-Length: 1270
Connection: close

<!doctype html>
<html>
<head>
    <title>Example Domain</title>
...

Deleting sdkconfig

When changing the chip target between ESP32 and ESP32-S2 Beta it is necessary to delete any existing sdkconfig and then run idf.py at least once with the -D IDF_TARGET=esp32s2beta argument.

This is because a single sdkconfig can only be generated with support for a single target. If no target name is given, it will default to ESP32.

When changing target chips, it is recommended to also delete the build directory. This is not a strict requirement, but it is recommended while the ESP-IDF multiple target support is still maturing.

Limitations

Currently released ESP32-S2 Beta support in ESP-IDF only supports basic features. Espressif firmware developers are working hard on the remaining support, so check the feature/esp32s2beta branch regularly for updates.
Full speed USB OTG peripheral is not supported
Peripheral drivers are a work in progress
No power saving modes
No hardware security features or cryptographic accelerator support
Time-of-Flight (TOF) measurements with normal Wi-Fi packets is not supported
Issues

If you find issues which are not mentioned above, please open an issue on GitHub.

Please make sure to mention that you are using the ESP32-S2 Beta chip.

资源：
1、USB-TTL CP2104串口控制台
2、microUSB OTG口
3、16M nor FLASH
4、TF卡槽，可接TF卡或TF-WiFi
5、40P通用RGB FPC排座（含电容触摸屏）
6、6P通用电容触摸FPC排座
7、MIC一个
8、BOOT按键、复位按键
9、50.8*22.86mm纤瘦尺寸，2.54排针引出所有资源，排针间隔20.32mm适合面包板

Re: f1c200s chip and BITC200 module
不废话，直接上图，尺寸 2000X900mil（50.8*22.86mm)