您尚未登录。

楼主 #1 2019-04-16 09:17:08

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

核心板华强做的,为了快直接板厚1.6mm  绿油,华强SMT  结果PCB被做挂了,华强又补做,这样13天过去了,清明一过华强商城的物料又过几天才配齐,贴片完,嗯,22天过去了,真是久远,很少这么久的了。
今天回来手工补了下元件,焊一块到底板上去不亮,一查5V没到核心板,一量其它的核心板都通,惟独焊的第一块不通,无奈飞一下,ok,由于没用spi flash,上电USB插上去,有反应了,sunxi-tools运行,能发现了,总算心情爽了些。
用主线,TF卡行,SDIO WIFI能探测到,USB,网络,UART,按键也都可以,剩下触摸,Wifi有中断申请问题,还有摄像头,我是准备的OV5640的,还要往上挪。看图

Core_S3_V01.jpg
Core_S3_V01_20190416-0910.jpg
S3_V01.jpg
S3_V01_20190416-0912.jpg
S3_V015IPS.jpg
S3_V01_20190416-0916.jpg





离线

楼主 #2 2019-04-16 09:20:00

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

转接板还差个7" 10.1" RGB接口的FPC座,是上接的,今天会到,到时候点下,1024x600的屏跟GP911触摸都有,考虑到有LVDS,把8"  9.7寸的40P LVDS屏也弄上去了,屏跟触摸也都有,不过是大的圆角的,lvds如何点还得研究





离线

#3 2019-04-16 09:20:55

晕哥
管理员
所在地: 微信 whycan_cn
注册时间: 2017-09-06
已发帖子: 9,242
积分: 9197

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

挺不错, 挺不错, 感谢分享!





离线

楼主 #4 2019-04-16 09:21:55

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

当然,底板能直接接40P的4.3寸普清,高清,还有5寸高清屏,不过外形有点不匹配,底板是按照5寸IPS来的,外壳在画,到时候可3D打印





离线

楼主 #5 2019-04-16 09:26:00

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

这个得靠晕哥带着我们玩啊,S3没啥资料,全靠猜了,原理图如下,
core_s3_v01.pdf





离线

楼主 #6 2019-04-16 09:27:11

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

底板原理图
hq_050ips_v01.pdf





离线

楼主 #7 2019-04-16 09:30:15

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

晕哥晕哥,地址发我,我是278129052





离线

#8 2019-04-16 09:55:39

lcfmax
会员
注册时间: 2018-04-13
已发帖子: 319
积分: 272.5

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

谢谢楼主分享了

离线

楼主 #9 2019-04-16 09:59:20

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

没事没事,大家好才是真的好,哈哈,





离线

楼主 #10 2019-04-16 10:06:51

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

uboot配置文件,头文件,及board.c发上来,IPS液晶要spi配置,这种东西资料也要找厂家,因为一般都是带MIPI/RGB功能的,所以外面资料不多
怎么上传c文件?





离线

#11 2019-04-16 10:55:43

晕哥
管理员
所在地: 微信 whycan_cn
注册时间: 2017-09-06
已发帖子: 9,242
积分: 9197

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

zhenfanhei 说:

uboot配置文件,头文件,及board.c发上来,IPS液晶要spi配置,这种东西资料也要找厂家,因为一般都是带MIPI/RGB功能的,所以外面资料不多
怎么上传c文件?

打包成  rar zip 或者 7z 文件上传





离线

#12 2019-04-16 12:44:44

达克罗德
会员
注册时间: 2018-04-10
已发帖子: 1,134
积分: 1086.5

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

关注楼主华强PCB,买料以及SMT一条龙服务怎么样?价格如何

离线

楼主 #13 2019-04-16 13:10:56

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

已知悉@晕哥
@达克罗德, 价格嘛当然不好啦,而且他们没什么备料,我有个料0201  10K弄错了,只好不贴,回来搞死了,





离线

楼主 #14 2019-04-16 13:11:57

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

而且贴片返单的话,只省下钢网钱,其它钱全部再给一次





离线

#15 2019-04-16 16:26:46

mango
会员
所在地: 芒果派
注册时间: 2017-12-02
已发帖子: 779
积分: 730

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

楼主,43438调通了不?直接怼上AP6212的驱动






歪朵拉开源硬件: https://widora.cn
淘宝:  https://widora.taobao.com/

离线

#16 2019-04-16 18:55:09

dycbaba
会员
注册时间: 2019-03-27
已发帖子: 97
积分: 76.5

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

s3 为啥还要做核心板

离线

楼主 #17 2019-04-16 19:24:28

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

@mango, 还没,还搞下液晶扩展板,
@dycbaba, S3是BGA的





离线

楼主 #18 2019-04-18 12:25:29

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

中断申请ok,以前一直用realtek的wifi,博通的以前没用过,现在有报错,试了几种brcmfmac43430-sdio.bin brcmfmac43430-sdio.txt,这个是BPI_WiFi_Firmware那找来的
# insmod /opt/brcmutil.ko
# insmod /opt/brcmfmac.ko
# [  200.328184] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[  200.344345] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr failed, -110
[  200.362001] brcmfmac: brcmf_bus_started: failed: -110
[  200.372179] brcmfmac: brcmf_sdio_firmware_callback: dongle is not responding





离线

楼主 #19 2019-04-18 12:31:35

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

把调试打开,前面看了一截,和驱动顺序比没出错,把后面挂的贴一下,看有没有经验的GGJJ带带我,涨涨知识

[   59.264043] brcmf_sdio_clkctl Enter
[   59.272478] brcmf_sdio_htclk Enter
[   59.280719] brcmf_sdiod_regwb addr:0x0001000e, data:0x00
[   59.290864] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   59.307583] brcmf_sdio_htclk CLKCTL: turned OFF
[   59.316961] brcmf_sdio_clkctl 3 -> 1
[   59.325246] brcmf_sdio_clkctl Enter
[   59.333321] brcmf_sdio_htclk Enter
[   59.341216] brcmf_sdiod_regwb addr:0x0001000e, data:0x10
[   59.351043] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   59.367256] brcmf_sdiod_regrb addr:0x0001000e
[   59.376176] brcmf_sdiod_request_data rw=0, func=1, addr=0x1000e, nbytes=1
[   59.392124] brcmf_sdiod_regrb data:0xd0
[   59.400432] brcmf_sdio_htclk CLKCTL: turned ON
[   59.409247] brcmf_sdio_clkctl 1 -> 3
[   59.417069] brcmf_sdiod_regrb addr:0x0001000e
[   59.425673] brcmf_sdiod_request_data rw=0, func=1, addr=0x1000e, nbytes=1
[   59.441404] brcmf_sdiod_regrb data:0xd0
[   59.449547] brcmf_sdiod_regwb addr:0x0001000e, data:0xd2
[   59.459077] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   59.474514] brcmf_sdiod_regwl addr:0x18002048, data:0x00040000
[   59.488733] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000a, nbytes=1
[   59.504435] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000b, nbytes=1
[   59.519996] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000c, nbytes=1
[   59.535879] brcmf_sdiod_request_data rw=1, func=1, addr=0x0a048, nbytes=4
[   59.551918] brcmf_sdio_firmware_callback enable F2: err=0
[   59.561869] brcmf_sdiod_regwl addr:0x18002024, data:0x200000f0
[   59.576507] brcmf_sdiod_request_data rw=1, func=1, addr=0x0a024, nbytes=4
[   59.592738] brcmf_sdiod_regwb addr:0x00010008, data:0x08
[   59.602713] brcmf_sdiod_request_data rw=1, func=1, addr=0x10008, nbytes=1
[   59.618801] brcmf_chip_sr_capable Enter
[   59.627115] brcmf_sdiod_regrl addr:0x18000508
[   59.636024] brcmf_sdiod_request_data rw=0, func=1, addr=0x08508, nbytes=4
[   59.652037] brcmf_sdiod_regrl data:0x00000000
[   59.660964] brcmf_sdiod_regwb addr:0x0001000e, data:0xd0
[   59.670815] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   59.686930] brcmf_sdiod_change_state 0 -> 1
[   59.695685] brcmf_bus_change_state 0 -> 1
[   59.704184] brcmf_sdiod_intr_register Enter, register OOB IRQ 51
[   59.719254] brcmf_sdiod_regrb addr:0x00000004
[   59.728268] brcmf_sdiod_request_data rw=0, func=0, addr=0x00004, nbytes=1
[   59.744794] brcmf_sdiod_regrb data:0x00
[   59.753360] brcmf_sdiod_regwb addr:0x00000004, data:0x07
[   59.763332] brcmf_sdiod_request_data rw=1, func=0, addr=0x00004, nbytes=1
[   59.779652] brcmf_sdiod_regwb addr:0x000000f2, data:0x03
[   59.789710] brcmf_sdiod_request_data rw=1, func=0, addr=0x000f2, nbytes=1
[   59.806139] brcmf_bus_started 
[   59.813971] brcmf_add_if Enter, bsscfgidx=0, ifidx=0
[   59.823696] brcmf_add_if allocate netdev interface
[   59.833199] brcmf_add_if  ==== pid:14, if:wlan%d (00:00:00:00:00:00) created ===
[   59.849917] brcmf_bus_change_state 1 -> 1
[   59.858654] brcmf_proto_bcdc_query_dcmd Enter, cmd 262 len 20
[   59.873682] brcmf_proto_bcdc_msg Enter
[   59.882066] brcmf_sdio_bus_txctl Enter
[   59.890766] brcmf_sdio_dpc Enter
[   59.898550] brcmf_sdio_bus_sleep Enter: request WAKE currently WAKE
[   59.913663] brcmf_sdio_clkctl Enter
[   59.921549] brcmf_sdio_bus_sleep new state WAKE
[   59.930425] brcmf_sdio_bus_sleep Exit: err=0
[   59.938976] brcmf_sdio_tx_ctrlframe Enter
[   59.947586] brcmf_sdio_bus_watchdog Enter
[   59.956475] brcmf_sdio_bus_txctl ctrl_frame complete, err=0
[   59.970303] brcmf_proto_bcdc_cmplt Enter
[   59.978331] brcmf_sdio_bus_rxctl Enter
[   59.986085] brcmf_sdio_bus_watchdog Enter
[   60.008164] brcmf_sdio_bus_watchdog Enter
[   60.016084] brcmf_sdio_bus_watchdog idle
[   60.023839] brcmf_sdio_bus_sleep Enter: request SLEEP currently WAKE
[   60.037717] brcmf_sdio_clkctl Enter
[   60.045009] brcmf_sdio_htclk Enter
[   60.052135] brcmf_sdiod_regwb addr:0x0001000e, data:0x00
[   60.061243] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   60.076490] brcmf_sdio_htclk CLKCTL: turned OFF
[   60.084973] brcmf_sdio_sdclk Enter
[   60.092136] brcmf_sdio_clkctl 3 -> 0
[   60.099417] brcmf_sdio_bus_sleep new state SLEEP
[   60.107705] brcmf_sdio_bus_sleep Exit: err=0
[   62.488104] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[   62.501211] brcmf_sdio_bus_sleep Enter: request WAKE currently SLEEP
[   62.514859] brcmf_sdio_clkctl Enter
[   62.522038] brcmf_sdio_sdclk Enter
[   62.529087] brcmf_sdio_htclk Enter
[   62.536016] brcmf_sdiod_regwb addr:0x0001000e, data:0x10
[   62.544870] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   62.559631] brcmf_sdiod_regrb addr:0x0001000e
[   62.567611] brcmf_sdiod_request_data rw=0, func=1, addr=0x1000e, nbytes=1
[   62.582032] brcmf_sdiod_regrb data:0xd0
[   62.589599] brcmf_sdio_htclk CLKCTL: turned ON
[   62.597600] brcmf_sdio_clkctl 0 -> 3
[   62.604717] brcmf_sdio_bus_sleep new state WAKE
[   62.612764] brcmf_sdio_bus_sleep Exit: err=0
[   62.620482] brcmf_chip_sr_capable Enter
[   62.627697] brcmf_sdiod_regrl addr:0x18000508
[   62.635485] brcmf_sdiod_request_data rw=0, func=1, addr=0x08508, nbytes=4
[   62.649602] brcmf_sdio_bus_watchdog Enter
[   62.657374] brcmf_sdiod_regrl data:0x00000000
[   62.665346] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000a, nbytes=1
[   62.679449] brcmf_sdio_bus_watchdog Enter
[   62.687071] brcmf_sdio_bus_watchdog idle
[   62.695022] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000b, nbytes=1
[   62.709077] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000c, nbytes=1
[   62.723541] brcmf_sdiod_ramrw read 4 bytes at offset 0x00007ffc in window 0x00078000
[   62.739040] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000a, nbytes=1
[   62.754147] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000b, nbytes=1
[   62.769070] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000c, nbytes=1
[   62.784480] brcmf_sdio_readshared sdpcm_shared address 0x0003C89C
[   62.799019] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000a, nbytes=1
[   62.814643] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000b, nbytes=1
[   62.830312] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000c, nbytes=1
[   62.846469] brcmf_sdiod_ramrw read 64 bytes at offset 0x0000489c in window 0x00038000
[   62.863500] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000a, nbytes=1
[   62.879748] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000b, nbytes=1
[   62.896033] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000c, nbytes=1
[   62.912812] brcmf_sdio_checkdied firmware not built with -assert
[   62.928539] brcmf_fil_cmd_data Failed: (unknown) (-110)
[   62.938711] brcmf_fil_iovar_data_get ifidx=0, name=cur_etheraddr, len=6
[   62.955019] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr failed, -110
[   62.972508] brcmfmac: brcmf_bus_started: failed: -110
[   62.982658] brcmfmac: brcmf_sdio_firmware_callback: dongle is not responding
[   62.999916] brcmf_sdio_firmware_callback failed: dev=mmc1:0001:1, err=-110
[   63.017235] brcmf_ops_sdio_remove Enter
[   63.026298] brcmf_ops_sdio_remove sdio vendor ID: 0x02d0
[   63.036816] brcmf_ops_sdio_remove sdio device ID: 0xa9a6
[   63.047301] brcmf_ops_sdio_remove Function: 1
[   63.056805] brcmf_sdiod_intr_unregister Entering oob=1 sd=0
[   63.072560] brcmf_sdiod_regwb addr:0x000000f2, data:0x00
[   63.083121] brcmf_sdiod_request_data rw=1, func=0, addr=0x000f2, nbytes=1
[   63.101749] brcmf_sdiod_regwb addr:0x00000004, data:0x00
[   63.112485] brcmf_sdiod_request_data rw=1, func=0, addr=0x00004, nbytes=1
[   63.130142] brcmf_sdio_remove Enter
[   63.138892] brcmf_sdiod_intr_unregister Entering oob=0 sd=0
[   63.154602] brcmf_detach Enter
[   63.162685] brcmf_bus_change_state 1 -> 0
[   63.171660] brcmf_sdio_bus_stop Enter
[   63.180269] brcmf_sdio_bus_sleep Enter: request SLEEP currently WAKE
[   63.196261] brcmf_sdio_clkctl Enter
[   63.204541] brcmf_sdio_htclk Enter
[   63.212650] brcmf_sdiod_regwb addr:0x0001000e, data:0x00
[   63.222677] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   63.239624] brcmf_sdio_htclk CLKCTL: turned OFF
[   63.248942] brcmf_sdio_sdclk Enter
[   63.256882] brcmf_sdio_clkctl 3 -> 0
[   63.264954] brcmf_sdio_bus_sleep new state SLEEP
[   63.274014] brcmf_sdio_bus_sleep Exit: err=0
[   63.283075] brcmf_sdio_bus_sleep Enter: request WAKE currently SLEEP
[   63.298049] brcmf_sdio_clkctl Enter
[   63.305790] brcmf_sdio_sdclk Enter
[   63.313340] brcmf_sdio_htclk Enter
[   63.320783] brcmf_sdiod_regwb addr:0x0001000e, data:0x10
[   63.330141] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   63.345776] brcmf_sdiod_regrb addr:0x0001000e
[   63.354337] brcmf_sdiod_request_data rw=0, func=1, addr=0x1000e, nbytes=1
[   63.369482] brcmf_sdiod_regrb data:0xd0
[   63.377269] brcmf_sdio_htclk CLKCTL: turned ON
[   63.385689] brcmf_sdio_clkctl 0 -> 3
[   63.393140] brcmf_sdio_bus_sleep new state WAKE
[   63.401490] brcmf_sdio_bus_sleep Exit: err=0
[   63.409489] brcmf_sdiod_regwl addr:0x18002024, data:0x00000000
[   63.422635] brcmf_sdiod_request_data rw=1, func=1, addr=0x0a024, nbytes=4
[   63.437641] brcmf_sdiod_regrb addr:0x0001000e
[   63.446045] brcmf_sdiod_request_data rw=0, func=1, addr=0x1000e, nbytes=1
[   63.461007] brcmf_sdiod_regrb data:0xd0
[   63.468808] brcmf_sdiod_regwb addr:0x0001000e, data:0xd2
[   63.477994] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   63.492758] brcmf_sdio_bus_stop disable SDIO interrupts
[   63.502046] brcmf_sdiod_regwl addr:0x18002020, data:0x200000f0
[   63.515528] brcmf_sdiod_request_data rw=1, func=1, addr=0x0a020, nbytes=4
[   63.530503] brcmf_proto_detach Enter
[   63.538039] brcmf_fweh_unregister event handler cleared for PSM_WATCHDOG
[   63.553429] brcmf_sdio_clkctl Enter
[   63.598113] brcmf_chip_set_passive Enter
[   63.606058] brcmf_sdiod_regrl addr:0x18103800
[   63.614420] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000a, nbytes=1
[   63.629643] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000b, nbytes=1
[   63.644679] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000c, nbytes=1
[   63.660062] brcmf_sdiod_request_data rw=0, func=1, addr=0x0b800, nbytes=4
[   63.675473] brcmf_sdiod_regrl data:0x00000000
[   63.684242] brcmf_sdiod_regwl addr:0x18103408, data:0x00000003
[   63.698725] brcmf_sdiod_request_data rw=1, func=1, addr=0x0b408, nbytes=4
[   63.714864] brcmf_sdiod_regrl addr:0x18103408
[   63.723908] brcmf_sdiod_request_data rw=0, func=1, addr=0x0b408, nbytes=4
[   63.740230] brcmf_sdiod_regrl data:0x00000003
[   63.749267] brcmf_sdiod_regwl addr:0x18103800, data:0x00000001
[   63.764179] brcmf_sdiod_request_data rw=1, func=1, addr=0x0b800, nbytes=4
[   63.780595] brcmf_sdiod_regrl addr:0x18103800
[   63.789709] brcmf_sdiod_request_data rw=0, func=1, addr=0x0b800, nbytes=4
[   63.806240] brcmf_sdiod_regrl data:0x00000001
[   63.815485] brcmf_sdiod_regwl addr:0x18103408, data:0x00000003
[   63.830816] brcmf_sdiod_request_data rw=1, func=1, addr=0x0b408, nbytes=4
[   63.847518] brcmf_sdiod_regrl addr:0x18103408
[   63.856760] brcmf_sdiod_request_data rw=0, func=1, addr=0x0b408, nbytes=4
[   63.873440] brcmf_sdiod_regrl data:0x00000003
[   63.882680] brcmf_sdiod_regrl addr:0x18101800
[   63.891834] brcmf_sdiod_request_data rw=0, func=1, addr=0x09800, nbytes=4
[   63.908485] brcmf_sdiod_regrl data:0x00000001
[   63.917621] brcmf_sdiod_regwl addr:0x18101408, data:0x00000007
[   63.932877] brcmf_sdiod_request_data rw=1, func=1, addr=0x09408, nbytes=4
[   63.949487] brcmf_sdiod_regrl addr:0x18101408
[   63.958679] brcmf_sdiod_request_data rw=0, func=1, addr=0x09408, nbytes=4
[   63.975245] brcmf_sdiod_regrl data:0x00000007
[   63.984441] brcmf_sdiod_regrl addr:0x18101800
[   63.993567] brcmf_sdiod_request_data rw=0, func=1, addr=0x09800, nbytes=4
[   64.010205] brcmf_sdiod_regrl data:0x00000001
[   64.019416] brcmf_sdiod_regwl addr:0x18101800, data:0x00000000
[   64.034603] brcmf_sdiod_request_data rw=1, func=1, addr=0x09800, nbytes=4
[   64.051242] brcmf_sdiod_regrl addr:0x18101800
[   64.060378] brcmf_sdiod_request_data rw=0, func=1, addr=0x09800, nbytes=4
[   64.076484] brcmf_sdiod_regrl data:0x00000000
[   64.085550] brcmf_sdiod_regwl addr:0x18101408, data:0x00000005
[   64.100570] brcmf_sdiod_request_data rw=1, func=1, addr=0x09408, nbytes=4
[   64.117827] brcmf_sdiod_regrl addr:0x18101408
[   64.127076] brcmf_sdiod_request_data rw=0, func=1, addr=0x09408, nbytes=4
[   64.143180] brcmf_sdiod_regrl data:0x00000005
[   64.152257] brcmf_sdiod_regrl addr:0x18104800
[   64.161234] brcmf_sdiod_request_data rw=0, func=1, addr=0x0c800, nbytes=4
[   64.178034] brcmf_sdiod_regrl data:0x00000000
[   64.187160] brcmf_sdiod_regwl addr:0x18104408, data:0x00000003
[   64.202067] brcmf_sdiod_request_data rw=1, func=1, addr=0x0c408, nbytes=4
[   64.218797] brcmf_sdiod_regrl addr:0x18104408
[   64.227824] brcmf_sdiod_request_data rw=0, func=1, addr=0x0c408, nbytes=4
[   64.244232] brcmf_sdiod_regrl data:0x00000003
[   64.253300] brcmf_sdiod_regwl addr:0x18104800, data:0x00000001
[   64.268209] brcmf_sdiod_request_data rw=1, func=1, addr=0x0c800, nbytes=4
[   64.284733] brcmf_sdiod_regrl addr:0x18104800
[   64.293875] brcmf_sdiod_request_data rw=0, func=1, addr=0x0c800, nbytes=4
[   64.310318] brcmf_sdiod_regrl data:0x00000001
[   64.319472] brcmf_sdiod_regwl addr:0x18104408, data:0x00000003
[   64.334530] brcmf_sdiod_request_data rw=1, func=1, addr=0x0c408, nbytes=4
[   64.351213] brcmf_sdiod_regrl addr:0x18104408
[   64.360402] brcmf_sdiod_request_data rw=0, func=1, addr=0x0c408, nbytes=4
[   64.376888] brcmf_sdiod_regrl data:0x00000003
[   64.386075] brcmf_sdiod_regrl addr:0x18104800
[   64.395166] brcmf_sdiod_request_data rw=0, func=1, addr=0x0c800, nbytes=4
[   64.411718] brcmf_sdiod_regrl data:0x00000001
[   64.420911] brcmf_sdiod_regwl addr:0x18104800, data:0x00000000
[   64.435978] brcmf_sdiod_request_data rw=1, func=1, addr=0x0c800, nbytes=4
[   64.452566] brcmf_sdiod_regrl addr:0x18104800
[   64.461707] brcmf_sdiod_request_data rw=0, func=1, addr=0x0c800, nbytes=4
[   64.478216] brcmf_sdiod_regrl data:0x00000000
[   64.487304] brcmf_sdiod_regwl addr:0x18104408, data:0x00000001
[   64.502386] brcmf_sdiod_request_data rw=1, func=1, addr=0x0c408, nbytes=4
[   64.518875] brcmf_sdiod_regrl addr:0x18104408
[   64.527950] brcmf_sdiod_request_data rw=0, func=1, addr=0x0c408, nbytes=4
[   64.544400] brcmf_sdiod_regrl data:0x00000001
[   64.553574] brcmf_sdiod_regwl addr:0x18004010, data:0x00000003
[   64.568783] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000a, nbytes=1
[   64.585428] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000b, nbytes=1
[   64.601855] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000c, nbytes=1
[   64.618551] brcmf_sdiod_request_data rw=1, func=1, addr=0x0c010, nbytes=4
[   64.635146] brcmf_sdiod_regwl addr:0x18004044, data:0x00000000
[   64.650749] brcmf_sdiod_request_data rw=1, func=1, addr=0x0c044, nbytes=4
[   64.667752] brcmf_sdio_clkctl Enter
[   64.676197] brcmf_sdio_htclk Enter
[   64.684442] brcmf_sdiod_regwb addr:0x0001000e, data:0x00
[   64.694638] brcmf_sdiod_request_data rw=1, func=1, addr=0x1000e, nbytes=1
[   64.711396] brcmf_sdio_htclk CLKCTL: turned OFF
[   64.720873] brcmf_sdio_sdclk Enter
[   64.729075] brcmf_sdio_clkctl 3 -> 0
[   64.737350] brcmf_sdio_remove Disconnected
[   64.746697] brcmf_ops_sdio_remove Exit
[   64.755205] brcmf_ops_sdio_remove Enter
[   64.763642] brcmf_ops_sdio_remove sdio vendor ID: 0x02d0
[   64.773475] brcmf_ops_sdio_remove sdio device ID: 0xa9a6
[   64.783234] brcmf_ops_sdio_remove Function: 2
[   64.792027] brcmf_ops_sdio_remove Exit




离线

楼主 #20 2019-04-18 15:02:27

zhenfanhei
会员
注册时间: 2018-01-18
已发帖子: 296
积分: 251
个人网站

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

感谢晕哥,呵呵,wifi没问题了,不小心把设备树的interrupts从IRQ_TYPE_LEVEL_LOW弄成IRQ_TYPE_EDGE_FALLING了





离线

#21 2019-05-08 17:44:26

IC爬虫
会员
注册时间: 2018-06-18
已发帖子: 27
积分: 26.5

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

使用的是Zeta Linux吗

离线

#22 2019-05-08 17:48:26

晕哥
管理员
所在地: 微信 whycan_cn
注册时间: 2017-09-06
已发帖子: 9,242
积分: 9197

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

IC爬虫 说:

使用的是Zeta Linux吗

主线和zeta 都可以的





离线

#23 2019-11-02 22:04:31

ippen
会员
注册时间: 2018-07-22
已发帖子: 345
积分: 339.5

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

@zhenfanhei
这个S3板子,音频支持会不会像V3s那样,播放音乐前面有一段噪音?
原来这个帖子里面有提及 https://whycan.cn/t_1791.html

离线

#24 2019-11-02 22:09:53

晕哥
管理员
所在地: 微信 whycan_cn
注册时间: 2017-09-06
已发帖子: 9,242
积分: 9197

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

这个和 V3s 同一个 die, V3s有的问题, S3一个都不会少.





离线

#25 2019-12-27 22:39:21

iamkylin
会员
注册时间: 2019-10-09
已发帖子: 16
积分: 4

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

谢谢楼主分享了!

离线

#26 2020-04-21 19:51:30

生态平衡
会员
注册时间: 2020-04-21
已发帖子: 1
积分: 1

Re: 晒下S3核心板+底板+转接板,过程曲折,开源,一起玩,把BSP弄完善

不赖不赖,我是刚刚入门,感谢社区,感谢

离线

页脚

工信部备案:粤ICP备20025096号 Powered by FluxBB

感谢为中文互联网持续输出优质内容的各位老铁们。 QQ: 516333132, 微信(wechat): whycan_cn (哇酷网/挖坑网/填坑网) service@whycan.cn