非疾う 字引 字書 寄書
Priorities - A: high, B: medium, C: low; Status - _: unfinished, X: finished, C: cancelled, P: pending, o: in progress, >: delegated. Covey quadrants - Q1 & Q3: urgent, Q1 & Q2: important
A1XPrepare for ASTI talk
4: Ellen Sanchez businessworld Starbucks on Thursday. Businessworld.
9:30 Talk at ASTI ../school/current/asti-slides.sxi
15:00 CS21A
16:30 ThesisProject
私 が 愛 する 所 の 女 性


1. industry's point of view

Categories: None -- Permalink
standard models premium niche entry barrier very high

2. Embedded system design from ASTI's point of view

Categories: None -- Permalink
  • everywhere Trends in embedded systems development options ASTI's effort

networked or connected device multi-function device increasing use of open source OS

consumer electronics exhibit in the States, >0.5 web-enabled system engineering tool?

real-time development RTOS

3. Embedded talk

Categories: None -- Permalink
Title page
Hello, everyone! I'm Sacha Chua, and I'm here to talk about embedded system design from the developer's point of view. What _is_ embedded computing, anyway? It helps to define it in contrast to personal computers, which we're all familiar with.
PC/embedded system comparison
General use
Personal computers are intended for general use. They can run a wide range of applications - games, business apps, that sort of thing.
Specific function
Embedded systems, on the other hand, are typically designed for a single purpose. Think of a calculator, for example, or the logic in vending machines. (Of course, some embedded systems are becoming more general now, like personal digital assistants a).
OS, apps
Personal computers
On PCs, you can usually assume that someone
Different input/output
Easy to dev or change programs
Infrequently updated
User needs / expectations
Although crashes and data loss seem to be part of our everyday computing experience, people expect embedded systems to be reliable. Imagine an embedded system that crashes! What if your phone crashed and had to be rebooted all the time? People expect features, reliability, and all for a low price.
Tight space and memory constraints
Development tools
Development process
One of the things about embedded development is that the process is a little bit longer. It's not the usual edit, compile, run cycle. It's edit, compile, burn to flash, run.
Architectural quirks
And of course if you go into embedded development, you'll probably have to deal with different architectures. For example, you'll learn about the quirks of conditional ARM.
Why go into embedded dev't?
It's fun!
It's challenging!
It's useful!
How to get started
Courses on computer interfacing / hardware / digital logic
Internship / work / open source
What you need: software, hardware, patience