<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Industry on When Moore's Law Ends</title><link>https://jimwang99.github.io/posts/industry/</link><description>Recent content in Industry on When Moore's Law Ends</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 07 Jan 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://jimwang99.github.io/posts/industry/index.xml" rel="self" type="application/rss+xml"/><item><title>Hardware Security</title><link>https://jimwang99.github.io/posts/industry/hardware-security/</link><pubDate>Mon, 07 Jan 2019 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/hardware-security/</guid><description>&lt;h2 id="keynote-panel-on-risc-v-summit-2018-opportunities-and-challenges-in-security-for-open-source-hardware">Keynote panel on RISC-V Summit 2018: opportunities and challenges in security for open source hardware&lt;a class="anchor" href="#keynote-panel-on-risc-v-summit-2018-opportunities-and-challenges-in-security-for-open-source-hardware">#&lt;/a>&lt;/h2>
&lt;ul>
&lt;li>
&lt;p>Complex systems tend to have bugs, so making it preparatory will make it more secure from attacks. But open source simple systems attract more eyes to review so that it becomes more and more secure over time.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Military and government customers want secret projects.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>We need to change the way we design system&lt;/p>
&lt;ul>
&lt;li>Formal analysis&lt;/li>
&lt;li>More eyes on it, and keep things open&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>Weakness in RISC-V&lt;/p></description></item><item><title>RISC-V Summit 2018</title><link>https://jimwang99.github.io/posts/industry/risc-v-summit-2018/</link><pubDate>Tue, 04 Dec 2018 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/risc-v-summit-2018/</guid><description>&lt;h2 id="my-notes-on-risc-v-summit-2018-at-santa-clara-conventional-center">My notes on RISC-V Summit 2018 at Santa Clara Conventional Center&lt;a class="anchor" href="#my-notes-on-risc-v-summit-2018-at-santa-clara-conventional-center">#&lt;/a>&lt;/h2>
&lt;p>This year’s summit has many more participants than the last one, which means RISC-V is getting a lot of momentum around the world. Although most of the speeches are technology-detail-less propaganda thing, we still can find something useful out of it. And more importantly, talking to the engineers manning the booth is very interesting and information rich.&lt;/p>
&lt;h3 id="sifives-biz-model">SiFive’s biz model&lt;a class="anchor" href="#sifives-biz-model">#&lt;/a>&lt;/h3>
&lt;ul>
&lt;li>Help customer to tape-out prototypes, and sell chips back to the customer.
&lt;ul>
&lt;li>Fundamentally similar to old school design house&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Front-end is a highly configurable design generator, with which customers can easily change the configuration and get the SoC RTL. Then they can drop-in their proprietary IP with TileLink interface.&lt;/li>
&lt;/ul>
&lt;h3 id="sifives-freedom-revolution-platform">SiFive’s Freedom Revolution platform&lt;a class="anchor" href="#sifives-freedom-revolution-platform">#&lt;/a>&lt;/h3>
&lt;ul>
&lt;li>SiFive acquired OpenSilicon, and it gets HBM2/Interlaken/… IPs, with their own 7-series CPU core (dual issue), they now can offer full SoC solution to custmers&lt;/li>
&lt;li>Interlaken: chip-to-chip connection, 1.2Tbps, proprietary (not open source)&lt;/li>
&lt;/ul>
&lt;h3 id="hwacha-v4">Hwacha v4&lt;a class="anchor" href="#hwacha-v4">#&lt;/a>&lt;/h3>
&lt;ul>
&lt;li>Vector register file
&lt;ul>
&lt;li>Different from new RISC-V vector ISA, it merges storage of low precision registers&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Sequencer
&lt;ul>
&lt;li>Systolic bank unit
&lt;ul>
&lt;li>Stall free, like TPU&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>VRU: vector runahead unit
&lt;ul>
&lt;li>As I understand, it only prefetch the instruction, not the data. Actually the data part is more critical in prefetch&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Polymorphic extension
&lt;ul>
&lt;li>? What?&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h3 id="platformioorg">platformIO.org&lt;a class="anchor" href="#platformioorg">#&lt;/a>&lt;/h3>
&lt;ul>
&lt;li>Cloud, unified IDE for remote debug and CI&lt;/li>
&lt;li>Free and open-source&lt;/li>
&lt;li>Goes down to OpenOCD level, if we can make the hardware drives to support OpenOCD, then it can support it.&lt;/li>
&lt;/ul>
&lt;h3 id="renode">RENODE&lt;a class="anchor" href="#renode">#&lt;/a>&lt;/h3>
&lt;ul>
&lt;li>Simulator of RISC-V system&lt;/li>
&lt;li>PolarFire SoC&lt;/li>
&lt;/ul>
&lt;h3 id="david-pattersons-keynote-speech">David Patterson’s keynote speech&lt;a class="anchor" href="#david-pattersons-keynote-speech">#&lt;/a>&lt;/h3>
&lt;ul>
&lt;li>Learn from the software side of progress&lt;/li>
&lt;li>When Moore’s law stops, people catch up
&lt;ul>
&lt;li>Apple A12 is better than Intel’s CPU in single thread performance&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Security challenge nowadays is more and more serious&lt;/li>
&lt;li>RISC-V committee: slower, but last longer&lt;/li>
&lt;li>Open ISA vs. open hardware&lt;/li>
&lt;li>TPU: software controlled memory (instead of cache)&lt;/li>
&lt;li>Serverless computing
&lt;ul>
&lt;li>Raise the level of abstraction&lt;/li>
&lt;li>Not x86 forever&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h3 id="yunsup-lees-keynote-speech">Yunsup Lee’s keynote speech&lt;a class="anchor" href="#yunsup-lees-keynote-speech">#&lt;/a>&lt;/h3>
&lt;ul>
&lt;li>From customer: “we need more customization”&lt;/li>
&lt;li>EDA on cloud: Cadence + MS Azure&lt;/li>
&lt;/ul>
&lt;h3 id="rob-nxps-keynote-speech">Rob (NXP)‘s keynote speech&lt;a class="anchor" href="#rob-nxps-keynote-speech">#&lt;/a>&lt;/h3>
&lt;ul>
&lt;li>Fragmentation is a big concern&lt;/li>
&lt;li>VEGA board + PULP
&lt;ul>
&lt;li>2x PULP cores + 2x ARM cores&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Foundries.io
&lt;ul>
&lt;li>Software around RISC-V&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h3 id="antmicro-keynote-speech">AntMicro Keynote speech&lt;a class="anchor" href="#antmicro-keynote-speech">#&lt;/a>&lt;/h3>
&lt;ul>
&lt;li>Several things are going too slow
&lt;ul>
&lt;li>Linux-enabled cores&lt;/li>
&lt;li>Non-CPU IP is still hard&lt;/li>
&lt;li>Supply chain of making chips is painful&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Solution: FPGA&lt;/li>
&lt;li>LiteX: open platform for Linux and MicroSemi&lt;/li>
&lt;/ul></description></item><item><title>SNUG Silicon Valley 2017 at Santa Clara Conventional Center</title><link>https://jimwang99.github.io/posts/industry/snug-silicon-valley-2017-at-santa-clara-conventional-center/</link><pubDate>Sun, 30 Apr 2017 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/snug-silicon-valley-2017-at-santa-clara-conventional-center/</guid><description>&lt;h2 id="day-1-morning">Day 1 Morning&lt;a class="anchor" href="#day-1-morning">#&lt;/a>&lt;/h2>
&lt;ol>
&lt;li>Paper from microsoft&lt;/li>
&lt;/ol>
&lt;ul>
&lt;li>Microsoft has a IC design team? Apparently it does.&lt;/li>
&lt;li>Grey code: even when metastability happends, it falls to adjecent states, instead of unknow states, it’s acceptable in some cases.&lt;/li>
&lt;li>Data bus bridge (DBB) for low data throughput&lt;/li>
&lt;li>Async FIFO: more area, more complexity&lt;/li>
&lt;/ul>
&lt;ol start="2">
&lt;li>Panel: synthesis into the future&lt;/li>
&lt;/ol>
&lt;ul>
&lt;li>The disruption in advanced nodes (10nm/7nm)
&lt;ul>
&lt;li>Thermal: drives max freq; heating wires degreeds EM lifetime&lt;/li>
&lt;li>IoT: analog-digital co-design; physical/electical context-aware synthesis (the tool need to be aware of the block’s specific attributes, such as thermal/IR to avoid analog/digital interference. Ex: PLL cause high IR drop so it cannot be placed near some sensitive digital blocks)&lt;/li>
&lt;li>Power: low power is usually focused, but power density is more important. Thermal dissipasion is the key to successful product.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Context includes 2 different aspect
&lt;ul>
&lt;li>Chip-level placement and interface&lt;/li>
&lt;li>Thermal dissipation&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Accurate variation modeling is important for the digital&lt;/li>
&lt;li>Blind clock gating for big blocks is not very good for IR drop, because it will create large power/ground noise. Instead, use smaller cores to go continuously is a better choice other than using large powerful cores working on and off.&lt;/li>
&lt;li>My take-aways: future EDA will merge front-end and back-end. The flow will be unified, as well as the interface and engines. It will require engineers to know better for the whole flow. It fits my understanding of full stack engineer.&lt;/li>
&lt;/ul>
&lt;h2 id="day-1-afternoon">Day 1 Afternoon&lt;a class="anchor" href="#day-1-afternoon">#&lt;/a>&lt;/h2>
&lt;ol>
&lt;li>Paper from Broadcom about DSP ungrouping&lt;/li>
&lt;/ol>
&lt;ul>
&lt;li>Not interesting as expected.&lt;/li>
&lt;li>Issue with auto ungrouping: design hierarchy change, or even port/logic change/moving
&lt;ul>
&lt;li>constraint need to change (it seems Broadcom use hand written constraint file for synthesis and timing analysis, instead of dump out SDC from Synthesis tool to use it in STA)&lt;/li>
&lt;li>script need to change&lt;/li>
&lt;li>porting script from one design to another is difficult&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Potential target to choose for ungrouping?
&lt;ol>
&lt;li>no ungroup at all vs. auto ungroup&lt;/li>
&lt;li>analyze both timing reports to find out critical paths that improved after ungrouping&lt;/li>
&lt;li>only ungroup the paths that improved&lt;/li>
&lt;/ol>
&lt;/li>
&lt;li>One take-away: they dump out timing paths into text files and do post-processing using Python. Another one is from my question, they use unified constraint files for both synthesis and STA, instead of write out SDC from synthesis tool and use it in STA. That actually make sense because unified constraint files are more understandable.&lt;/li>
&lt;/ul>
&lt;ol start="2">
&lt;li>Configurable design using SystemVerilog&lt;/li>
&lt;/ol>
&lt;ul>
&lt;li>Virtual classes, parameters, interfaces and etc to make RTL design more configurable. The author did some research abour work-arounds and what is synthesizable with current DC and VCS.&lt;/li>
&lt;li>Afterwards, I had a very interesting talk with the author and some other audiences. One important thing the others mentioned is that even 99% of the tools support one feature, and if the other 1% is not will kill the whole schedule. And they were beaten up a lot by other designers or front-back-end engineers because they use advanced coding techiques from SystemVerilog in their RTL. Some guy from Qualcomm mentioned that he was forbidden to use even parameters in his block. So it seems that there are not strong willing to switch from Verilog to SystemVerilog, especially from management level because nobody want to take risks in exchange of some configurability. That actually leads to my question to them that if anybody sees any performance improvements by using SystemVerilog. The author mentioned that using “for” loops instead of multiple “assign” will help the compiler to understand design intent and somehow improved the performance in one case.&lt;/li>
&lt;/ul>
&lt;h2 id="day-2-morning">Day 2 Morning&lt;a class="anchor" href="#day-2-morning">#&lt;/a>&lt;/h2>
&lt;ol>
&lt;li>Nanotime used in NVIDIA (Robert)&lt;/li>
&lt;/ol>
&lt;ul>
&lt;li>The presentation is from its memory team. The author mainly focused on the POCV features in Nanotime, and how to embedded ocv_sigma tables in liberty file from extract_model. And they did some correlation between POCV in Nanotime against Monte Carlo in HSPICE. The correlation is not very good at present time with the characterization script (to generate OCV parameter for each kind of transistors) provide by Synopsys. He also mentioned that they are going back to close the loop by feedback the correlation result into characterization script, hoping to improve the accruacy.&lt;/li>
&lt;li>Transistor variation coefficient (characterization script from Synopsys)
&lt;ul>
&lt;li>&lt;code>set_variation_parameters&lt;/code>&lt;/li>
&lt;li>for every individual types of transistors (different parameters)&lt;/li>
&lt;li>transistor variation in stack series is &lt;strong>different&lt;/strong>: more stack less variation&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>How to validate the path variation?
&lt;ul>
&lt;li>Use SPICE Monte Carlo simulation after write_spice from Nanotime.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>How to choose candidate for DDS?
&lt;ul>
&lt;li>Critical paths&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>LVF tables (ocv_sigma) have delay/transition/setup/hold&lt;/li>
&lt;/ul>
&lt;ol start="2">
&lt;li>Nanotime flow in Wave Computing (Roger Carpenter)&lt;/li>
&lt;/ol>
&lt;ul>
&lt;li>Product
&lt;ul>
&lt;li>16K instances of DPU&lt;/li>
&lt;li>Entire core is custom design
&lt;ul>
&lt;li>Network-on-chip, PCIe, DDR, HMC (Hybrid Memory Cube)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Global async local sync design&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Runtime issue? No.&lt;/li>
&lt;li>Coverage report to define the completion of constraint coverage&lt;/li>
&lt;li>Nanotime vs. write_spice
&lt;ul>
&lt;li>TT 25c no SI: delta &amp;lt; 8%&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>This is very interesting for myself personally because they are using custom digital design approach to implement deep learning accelerators which can achieve 10GHZ (actually what I heard is 6.7GHz in 16nm). They used schematic and hand placment, used pulse latch + domino logic + global async local sync clocking scheme. They used to use spice to close timing on their DSP core (which has 16k instances overall) in 28nm but finally moved into Nanotime. It is a very interesting company. And amazing to hear that anybody is still using this “lost art” in real chip design.&lt;/li>
&lt;li>Afterwards, we have several people gathering around to talk about this. A guy from Intel also mentioned that Intel themselves have moved away from custom design.&lt;/li>
&lt;/ul></description></item><item><title>Deep learning and Siri by Alex Acero @ Apple</title><link>https://jimwang99.github.io/posts/industry/deep-learning-and-siri-by-alex-acero-apple/</link><pubDate>Thu, 23 Mar 2017 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/deep-learning-and-siri-by-alex-acero-apple/</guid><description>&lt;h2 id="ai-and-ml">AI and ML&lt;a class="anchor" href="#ai-and-ml">#&lt;/a>&lt;/h2>
&lt;p>Artificial intellegence vs human intellegence
The imitation game, eugen Goosman passed the Turing Test, 2014
Alpha Go, deepmind 2015&lt;/p>
&lt;h2 id="introduction-to-deep-learning">Introduction to deep learning&lt;a class="anchor" href="#introduction-to-deep-learning">#&lt;/a>&lt;/h2>
&lt;p>Improve on task T with respect to performance metric P based on experience E
Perceptron learning (one layer NN): a(i) = a(i-1) + n * {target - output} * A(i)
1974 multi-ayer perceptron with backpropagation training
​ deep learning is old tricks, more computing power, more data makes it possible and powerful
Binary classification
​ TouchID, speaker verification, face verification, emal spam, motion detection, credit card fraud
N-ary classifiction
​ MNIST (handwriting), speaker identification, word prediction (typing on iphone)
Deep learning for speech (Deng, 2010)&lt;/p></description></item><item><title>Deep learning with GPUs in production</title><link>https://jimwang99.github.io/posts/industry/deep-learning-with-gpus-in-production/</link><pubDate>Tue, 21 Mar 2017 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/deep-learning-with-gpus-in-production/</guid><description>&lt;p>Start-up: python -&amp;gt; enterprise: C/Java/Scala, more engineers, faster
Research: quick result and prototyping&lt;/p>
&lt;p>GPU? Data movement between GPU and CPU is important&lt;/p>
&lt;p>[ ] fast.ai: class (high school math)&lt;/p>
&lt;p>infrastructure: spark/flink
scheduler problem
distributed file system&lt;/p>
&lt;p>Problems to think about when running works on GPU clusters
memory is relatively small
throughput, jobs are more than matrix math
resource provisioning: how many resource we need? GPU/CPU/RAM
GPU allocation per job
Python &amp;lt;-&amp;gt; Java overhead, defeats the points of GPUs&lt;/p></description></item><item><title>未来的AR应该是什么样子的？</title><link>https://jimwang99.github.io/posts/industry/%E6%9C%AA%E6%9D%A5%E7%9A%84ar%E5%BA%94%E8%AF%A5%E6%98%AF%E4%BB%80%E4%B9%88%E6%A0%B7%E5%AD%90%E7%9A%84/</link><pubDate>Tue, 21 Feb 2017 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/%E6%9C%AA%E6%9D%A5%E7%9A%84ar%E5%BA%94%E8%AF%A5%E6%98%AF%E4%BB%80%E4%B9%88%E6%A0%B7%E5%AD%90%E7%9A%84/</guid><description>&lt;p>今天去参加一个AI的meetup，碰到了一个连续创业者。他介绍了自己正在做的事情：“改变现有的输入方式，不应该是人给机器输入指令，而应该是机器预测人的需求并作出相应的动作。”，这才是机器的未来。同时他提到输出界面应该AR（增强现实）这种类型的，而不应该是一个显示屏幕。&lt;/p></description></item><item><title>Note of Deep learning for image and video processing tutorial</title><link>https://jimwang99.github.io/posts/industry/note-of-deep-learning-for-image-and-video-processing-tutorial/</link><pubDate>Sat, 21 Jan 2017 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/note-of-deep-learning-for-image-and-video-processing-tutorial/</guid><description>&lt;blockquote class='book-hint '>
&lt;p>By Jon Shlens and George Toderici from Google Research @ 2017-01-20 Fri&lt;/p>&lt;/blockquote>&lt;ul>
&lt;li>
&lt;p>History&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Convolutional NN: old tech, why suddenly it works?&lt;/p>
&lt;ul>
&lt;li>Scale: 60M parameters&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>At least 60M +1 data point to fit these parameters&lt;/p>
&lt;/li>
&lt;li>
&lt;p>SIMD hardware (GPU)&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Domain transfer&lt;/p>
&lt;ul>
&lt;li>Use trained CNN (with large data set) on some other applications with limited data set&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>CNN (convolutional neuron network)&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Toy model of a neuron&lt;/p>
&lt;ul>
&lt;li>Sum over weighted input + nonlinear activation function to output&lt;/li>
&lt;li>Very little relationship with real neuron&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>Softmax classifier&lt;/p></description></item><item><title>智能用电的革命</title><link>https://jimwang99.github.io/posts/industry/%E6%99%BA%E8%83%BD%E7%94%A8%E7%94%B5%E7%9A%84%E9%9D%A9%E5%91%BD/</link><pubDate>Sat, 21 Jan 2017 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/%E6%99%BA%E8%83%BD%E7%94%A8%E7%94%B5%E7%9A%84%E9%9D%A9%E5%91%BD/</guid><description>&lt;p>一场涉及普通消费者的智能用电革命正在悄然发生。加州政府近年来努力推动这项能源节约革命，在近三年来取得了快速的进步，得到了能源公司和电器制造商的广泛支持。&lt;/p>
&lt;h2 id="prosumer的概念">Prosumer的概念&lt;a class="anchor" href="#prosumer%e7%9a%84%e6%a6%82%e5%bf%b5">#&lt;/a>&lt;/h2>
&lt;p>普通家庭以往是以单一的电力消费者出现的。但是近年来由于太阳能发电设备的推广力度不断加大，得到了大量消费者的欢迎和支持，催生了prosumer的概念，即producer + consumer。通过政府大力支持的贷款在自家屋顶安装太阳能板，并将发出的电力上网卖给电力公司，同时获得最低单价的用电费用。我的同事中就有不少安装了，或者正在考虑安装这样的设备，表明这样的project即使对于普通的三口或四口之家都是有利可图的。&lt;/p>
&lt;h2 id="智能用电">智能用电&lt;a class="anchor" href="#%e6%99%ba%e8%83%bd%e7%94%a8%e7%94%b5">#&lt;/a>&lt;/h2>
&lt;p>电网消费有峰有谷，这样的波动由于各个小区域的消费习惯、天气变化等密切相关，而且往往变化迅速，即以分钟为单位反复变化。但是电网负载波动对于电网设备而言是有害的，所以电力公司有非常强烈的意愿通过某些技术手段来消弭这样的波动。这样就提出了“智能用电”的概念，也就是通过对普通的电器进行联网和远程自动控制，来调节小区域内部的用电波动。这样不仅能降低电网设备的负载，也能够有效利用能源，所以对于电力公司和政府决策者而言都是大有益处的。对于普通消费者而言，积极参与“智能用电”项目能够获得的利益来自于电力公司和政府政策补贴。&lt;/p>
&lt;p>举例说明，热水器和烘干机之类的设备是耗电量大户，但是往往对于时效性要求不是很高。如果能够加入特定的芯片进行联网控制其功率，取代恒定的大功率输出，就能够起到平衡电网负载波动的左右。代价可能仅仅是将原有的工作时间延长一些而已。再者就是目前越来越普及的电动车。对于普通使用者而言，充电时间远远大于使用时间。如果在足够的充电时间内自动选择电网负载最低的时段进行充电就能够获得最低的电价。&lt;/p>
&lt;h2 id="另外的小事">另外的小事&lt;a class="anchor" href="#%e5%8f%a6%e5%a4%96%e7%9a%84%e5%b0%8f%e4%ba%8b">#&lt;/a>&lt;/h2>
&lt;p>加州一些城市的商业区或者大型shopping center开始自行安装一些电动车充电桩。这些充电桩在非高峰期（周末或者节假日）是免费的。这样就吸引一些开电动车的顾客来充电和消费。&lt;/p></description></item><item><title>Bluetooth hub from Cassia Networks</title><link>https://jimwang99.github.io/posts/industry/bluetooth-hub-from-cassia-networks/</link><pubDate>Tue, 27 Sep 2016 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/bluetooth-hub-from-cassia-networks/</guid><description>&lt;p>今天的CES meetup是一个清华85级的学长来宣传他们自己公司的bluetooth hub，Cassia Networks。如果简单从名字上来看并没有什么高端的感觉，毕竟bluetooth和hub两个东西都不是什么稀奇的东西。但是它获得了2016年CES大会最佳产品奖项，可不是浪得虚名。&lt;/p>
&lt;p>它解决了bluetooth的痛点，而且是用现有的商业化芯片，在系统集成和固件上下功夫，通过对协议的深刻理解，得到了超出世人的性能：不需要对master和slave有任何的额外要求就能达到300+米的传输距离（相对于普通的10+米极限），能够穿过三堵墙，可以连接多个master和slave，并转发数据（虽然现有的Bluetooth标准并不支持路由功能）。而且，他们还在此基础上开发了开放的SDK，能够对接其他的软硬件厂商，并由此展现出在多个应用场景下的广泛应用前景。这款产品的厉害之处就在于它极大的拓展了Bluetooth在IoT领域的应用范围，甚至给予了Bluetooth这个标准更大的想象空间。&lt;/p>
&lt;p>个人的思考：&lt;/p>
&lt;ol>
&lt;li>坚持在一个领域深入挖掘，即使是已经有非常成熟的标准、广泛应用的技术和芯片产品，也能够厚积薄发取得突破甚至带来该领域的应用革新。&lt;/li>
&lt;li>坚持使用商业化芯片，因为已有的芯片功能其实能够在大部分时间充分满足应用需要，不必动辄开发一款ASIC来解决“+10%”的问题。&lt;/li>
&lt;/ol></description></item><item><title>Observation of IC Industory consolidation of future application</title><link>https://jimwang99.github.io/posts/industry/observation-of-ic-industory-consolidation-of-future-application/</link><pubDate>Sat, 06 Aug 2016 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/observation-of-ic-industory-consolidation-of-future-application/</guid><description>&lt;p>Recent consolidation progress is going so crazy, mostly because of the IC industry is becoming less and less profitable in every individual application fields. My perspective is that this is not just a consolidation of business itself, but a huge change of IC industry business model. There won’t be so many application fields that needs different IC chips, no matter it’s analog or digital. In analog world, more and more functionality will be replaced with digital as long as it can. It’s inevitable just like in digital world, more and more functionality will be replaced by software, as long as it can.&lt;/p></description></item><item><title>Optical Interconnection in Google Data Centers</title><link>https://jimwang99.github.io/posts/industry/optical-interconnection-in-google-data-centers/</link><pubDate>Tue, 11 Aug 2015 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/optical-interconnection-in-google-data-centers/</guid><description>&lt;p>今天的Meetup主要讲的是Google的Data Center中optical interconnection的应用。&lt;/p>
&lt;p>Presentation之后问了一个问题：Google的Data Center里面是否HDD正在被SSD取代？回答是，并没有，因为虽然SSD在读写速度上有明显的优势，但是由于存储容量的性价比非常低，所以仅是作为缓存使用。也就是说在HDD和DRAM之间再加一层SSD来提升存取速度。看来老板Sehat的FLC其实是基于市场选择而做出的理智判断（甚至不能说是预测，因为已经成为工业现实）。而且如果enterprise如果能够迅速跟上以弥补mobile市场的萎缩，Marvell在硬盘市场应该还能继续赚取利润。&lt;/p>
&lt;blockquote class='book-hint '>
&lt;p>Follow-up @ 2019-02-11: Sehat已经被挤出了公司，FLC项目也随之夭折。当时做这个项目的Marvell的同事们出去搞了一个自己的公司，拿到了Sehat的投资，正在如火如荼的做这个项目。时至今日，SSD仍然没有把HDD完全取代，但是根据Marvell最近的财务状况，HDD的市场萎缩的很厉害。&lt;/p>&lt;/blockquote></description></item><item><title>IDF (Intel Developer Forum) 2015 San Francisco, Moscone Center</title><link>https://jimwang99.github.io/posts/industry/idf-intel-developer-forum-2015-san-francisco-moscone-center/</link><pubDate>Wed, 01 Jul 2015 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/idf-intel-developer-forum-2015-san-francisco-moscone-center/</guid><description>&lt;ul>
&lt;li>Intel IoT platform
&lt;ul>
&lt;li>Intel IoT Platform
&lt;ul>
&lt;li>Sensors and things
&lt;ul>
&lt;li>Arduino&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Gateway
&lt;ul>
&lt;li>transfer data between different types of networks&lt;/li>
&lt;li>some data processing as well&lt;/li>
&lt;li>moving quickly: different types of data&lt;/li>
&lt;li>flexibility is important for scalability&lt;/li>
&lt;li>PMA: protocol mapper and adapter (UPAL)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Security
&lt;ul>
&lt;li>not only data, but also physical security&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>data storage
&lt;ul>
&lt;li>physically distributed&lt;/li>
&lt;li>depend on the data types, and there are so many of them&lt;/li>
&lt;li>different users use the same data in many different ways
&lt;ul>
&lt;li>provide different sets of APIs at business level&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Real world IoT challenges
&lt;ul>
&lt;li>3 major areas
&lt;ul>
&lt;li>connected things and devices&lt;/li>
&lt;li>intelligence and the edge&lt;/li>
&lt;li>turn data in to insight&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>different applications
&lt;ul>
&lt;li>cities: e.g. drain block sensor network
&lt;ul>
&lt;li>connected things and devices
&lt;ul>
&lt;li>regulatory:delay tolerance&lt;/li>
&lt;li>harsh conditions: device robust&lt;/li>
&lt;li>long distance: zigbee is not useful anymore&lt;/li>
&lt;li>security&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>intelligence ant ht edge
&lt;ul>
&lt;li>low power&lt;/li>
&lt;li>OOB ML&lt;/li>
&lt;li>sensor fusion&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>turn data into insight
&lt;ul>
&lt;li>diverse ecosystem&lt;/li>
&lt;li>multiuse data&lt;/li>
&lt;li>data ownership&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>smart grid
&lt;ul>
&lt;li>high freq&lt;/li>
&lt;li>extreme reliabliity
&lt;ul>
&lt;li>challenging environment&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>manageablity&lt;/li>
&lt;li>security&lt;/li>
&lt;li>demand response&lt;/li>
&lt;li>actuation&lt;/li>
&lt;li>data privacy&lt;/li>
&lt;li>data volumen&lt;/li>
&lt;li>public/private&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>industrial
&lt;ul>
&lt;li>legacy integration
&lt;ul>
&lt;li>very old implementation&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>multi-protocols&lt;/li>
&lt;li>zero downtime&lt;/li>
&lt;li>security
&lt;ul>
&lt;li>multi million equipments&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>bespoke feeds&lt;/li>
&lt;li>data translation&lt;/li>
&lt;li>ML customisation&lt;/li>
&lt;li>enterprise/network&lt;/li>
&lt;li>integration&lt;/li>
&lt;li>business rules&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Smart cities
&lt;ul>
&lt;li>future of flood management
&lt;ul>
&lt;li>approach
&lt;ul>
&lt;li>work with cicies
&lt;ul>
&lt;li>city managers have the requirements and most of the experience&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>prototype
&lt;ul>
&lt;li>Intel IoT gateway: extend the life of equipment by make use of old equipments that already exists&lt;/li>
&lt;li>custom flood detecting sensor&lt;/li>
&lt;li>software and simulation in matlab (openTSDB)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>deploy and iterate
&lt;ul>
&lt;li>deploy the implementation is time consuming and fruastrating for engineers&lt;/li>
&lt;li>iteration is important for this kind of experiment projects&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Smart grids: enernet
&lt;ul>
&lt;li>put sensors in families and get their energy usage profiles&lt;/li>
&lt;li>and make use of these data&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Data center
&lt;ul>
&lt;li>to increase visibility to resource usage&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Data analytics and machine learning Intel fellow
&lt;ul>
&lt;li>what is machine learning
&lt;ul>
&lt;li>a computer program learns, if tis performance improves with experience, Tom Mitchell&lt;/li>
&lt;li>3 types
&lt;ul>
&lt;li>superviesed learning: large amount of learning data, and people label data out&lt;/li>
&lt;li>unsupervised learning: make inferences without labeled data&lt;/li>
&lt;li>reinforcement learning: act in an env to maximize reward, real learning process&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>why now, tech is decades old, why sudden hot now
&lt;ul>
&lt;li>machine makes real decisions now&lt;/li>
&lt;li>big opportunity: extract value from data. things x data = value&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>relationship to other workloads
&lt;ul>
&lt;li>similar to high performance computing, and showing more and more similarities&lt;/li>
&lt;li>traditional: inside-out process&lt;/li>
&lt;li>emerging: outside-in process, from data to knowledge&lt;/li>
&lt;li>machine learning combines both of these 2 processes&lt;/li>
&lt;li>models
&lt;ul>
&lt;li>algorithms
&lt;ul>
&lt;li>database primitives&lt;/li>
&lt;li>graph algo&lt;/li>
&lt;li>machine learning&lt;/li>
&lt;li>numeric cmputing&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>intel architecture-specific optimization
&lt;ul>
&lt;li>key msg
&lt;ul>
&lt;li>machine learning is the most significant emergin algorithm class today&lt;/li>
&lt;li>publicly available code is highly inefficent in terms of its parallelism-awareness&lt;/li>
&lt;li>code modernization: signle-node or distributed&lt;/li>
&lt;li>enhance both processor and tool chain&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>how intel tools accelerate machine learning&lt;/li>
&lt;li>why deep learning is so exciting
&lt;ul>
&lt;li>shallow learning: one layer&lt;/li>
&lt;li>deep network layers can apply to parallelism&lt;/li>
&lt;li>go deeper in the layers, the system learn and got more clear idea of the target&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Intel Xeon + FPGA (from Altera)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Internet of things software standards unscrambled
&lt;ul>
&lt;li>Creating a Model&lt;/li>
&lt;li>Simple Layer Model
&lt;ul>
&lt;li>application and service &amp;lt;-&amp;gt; data &amp;amp; control points&lt;/li>
&lt;li>profiles, data &amp;amp; resource models
&lt;ul>
&lt;li>how IoT devices are represetned to app and servcies&lt;/li>
&lt;li>how app and servcie interact vith the represetnations&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>comms protocols &amp;lt;-&amp;gt;
&lt;ul>
&lt;li>high level protocols, multi-layers&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>transports &amp;lt;-&amp;gt;
&lt;ul>
&lt;li>physical layers and low level protocols&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>standards for locao IP, internet and cloud
&lt;ul>
&lt;li>local to local via internet?&lt;/li>
&lt;li>cloud to cloud connect?&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>deliverables
&lt;ul>
&lt;li>traditional standard
&lt;ul>
&lt;li>specification&lt;/li>
&lt;li>certification&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>code
&lt;ul>
&lt;li>for developers, open source projects, de facto standard&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>IP
&lt;ul>
&lt;li>trademark&lt;/li>
&lt;li>copyright&lt;/li>
&lt;li>patent&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>standard
&lt;ul>
&lt;li>intel is behind both IIC &amp;amp; OIC&lt;/li>
&lt;li>open source is changing the formation of standard. so intel is contributing open source code&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Future?
&lt;ul>
&lt;li>never be one standard to rule them all&lt;/li>
&lt;li>recurring themes
&lt;ul>
&lt;li>consistency&lt;/li>
&lt;li>low power and constrained services&lt;/li>
&lt;li>security
&lt;ul>
&lt;li>machine to machine communication&lt;/li>
&lt;li>different user/admin will have different level of access&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>IP, REST-based&lt;/li>
&lt;li>cooperation
&lt;ul>
&lt;li>interoperation&lt;/li>
&lt;li>collaboration&lt;/li>
&lt;li>consolidation&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Realsense
&lt;ul>
&lt;li>3D camera and develope kit&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>IoT (windriver &amp;amp; VxWorks)
&lt;ul>
&lt;li>2015 is the peak of inflated expectations&lt;/li>
&lt;li>tech wave: 1B+ desktop internet » 10B+ mobile device » 50B+ IoT&lt;/li>
&lt;li>2 business interests
&lt;ul>
&lt;li>optimization
&lt;ul>
&lt;li>new efficientcies: more data of things that cannot collectable before&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>transformation
&lt;ul>
&lt;li>new revenue streams&lt;/li>
&lt;li>transitionsing business models&lt;/li>
&lt;li>positive shifts in value creation and value capture&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>how to get started with IoT
&lt;ul>
&lt;li>platform, integrited from left (things) to right (cloud)
&lt;ul>
&lt;li>things side
&lt;ul>
&lt;li>embedded system&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>gateway&lt;/li>
&lt;li>cloud side
&lt;ul>
&lt;li>network&lt;/li>
&lt;li>data center&lt;/li>
&lt;li>cloud analytics&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>secure from end to end: edge-to-enterprise&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul></description></item><item><title>DAC 2015</title><link>https://jimwang99.github.io/posts/industry/dac-2015/</link><pubDate>Fri, 19 Jun 2015 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/dac-2015/</guid><description>&lt;ul>
&lt;li>汽车设计正在成为EDA公司的讨论热点。我个人觉得ANSYS应该算是其中翘楚，因为各种物理模拟器和散热模拟器是他们的传统强项。而诸如Synospsys和Mentor这样的软件厂商就更多的focus在电子系统上，硬件软件全部都有。&lt;/li>
&lt;li>From Mindy: EDA厂商每年都要收购大量的小公司来保证自己的创造力。&lt;/li>
&lt;li>ARM推出了专门针对Bluetooth 4.0的IP库和demo&lt;/li>
&lt;li>有一家叫做flexlogic的公司，专门做FPGA阵列的IP，用于在普通的ASIC芯片上embed FPGA模块。但是这个模块的规模一般不会太大。跟他们现场的工程师聊天发现，他们和Marvell做SSD的Engling已经有合作了，用FPGA做在调试接口上，以少量的PIN来支持多种不同的调试协议。想法还是挺有创意的。&lt;/li>
&lt;/ul></description></item><item><title>ISSCC 2015 evening session - Moore's Law challenges below 10nm</title><link>https://jimwang99.github.io/posts/industry/isscc-2015-evening-session-moore-s-law-challenges-below-10nm/</link><pubDate>Mon, 23 Feb 2015 00:00:00 +0000</pubDate><guid>https://jimwang99.github.io/posts/industry/isscc-2015-evening-session-moore-s-law-challenges-below-10nm/</guid><description>&lt;link rel="stylesheet" href="https://jimwang99.github.io/katex/katex.min.css" />&lt;script defer src="https://jimwang99.github.io/katex/katex.min.js">&lt;/script>&lt;script defer src="https://jimwang99.github.io/katex/auto-render.min.js" onload="renderMathInElement(document.body, {&amp;#34;delimiters&amp;#34;:[{&amp;#34;left&amp;#34;:&amp;#34;$$&amp;#34;,&amp;#34;right&amp;#34;:&amp;#34;$$&amp;#34;,&amp;#34;display&amp;#34;:true},{&amp;#34;left&amp;#34;:&amp;#34;$&amp;#34;,&amp;#34;right&amp;#34;:&amp;#34;$&amp;#34;,&amp;#34;display&amp;#34;:false},{&amp;#34;left&amp;#34;:&amp;#34;\\(&amp;#34;,&amp;#34;right&amp;#34;:&amp;#34;\\)&amp;#34;,&amp;#34;display&amp;#34;:false},{&amp;#34;left&amp;#34;:&amp;#34;\\[&amp;#34;,&amp;#34;right&amp;#34;:&amp;#34;\\]&amp;#34;,&amp;#34;display&amp;#34;:true}]});">&lt;/script>
&lt;ul>
&lt;li>
&lt;p>Bohr: moore’s law for 50 years&lt;/p>
&lt;ul>
&lt;li>$mm^2$ is increasing since 130nm&lt;/li>
&lt;li>heterogeneous intergration: 3D chip is not a replacement of moore’s law (quite opposite with Sehat)&lt;/li>
&lt;li>refocus on general purpose design&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>Hill: 21 century computer architecture&lt;/p>
&lt;ul>
&lt;li>21stcentruryarchitecturewhitepaper.pdf - instruction set is not going to be untouchable anymore - energy first - parallelism - specialization - cross-layout design - cross-cutting: break current layers with new interfaces - BREAK LAYERS - software bloat - PHP is 50x slower than BLAC - 3D stack - how to address thermal problem? the power is reduced by 3D stacking&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>
&lt;p>1.3 Madden&lt;/p></description></item></channel></rss>