flip the world - 使用者貢獻 [zh-tw]

MediaWiki:Common.css

2026-09-09T08:11:22Z

Tommy：Sci-fi dark HUD theme for Timeless: dark palette, cyan/amber accents, HUD headings, dark pygments tokens, print stays light

/* ============================================================================
"flip the world" — DARK HUD sci-fi theme
Target skin: Timeless (site default). MediaWiki 1.43.
Loaded from MediaWiki:Common.css, so it applies to every skin and every
namespace; the structural selectors below are Timeless-specific and are
simply inert under other skins.

Palette: bg #0a0f1a / panel #0e1524 / text #c8d6e5
cyan #35e0ff (structure, links, headings)
amber #ffb340 (markers, emphasis, keywords)
mint #7cf6c8 (strings, positive)
No animation, no scanlines: this wiki is meant to be read.
============================================================================ */

:root {
--sf-bg: #0a0f1a;
--sf-bg-deep: #060b14;
--sf-panel: #0e1524;
--sf-panel-2: #111c2e;
--sf-panel-3: #16233a;
--sf-fg: #c8d6e5;
--sf-fg-dim: #8a9cb2;
--sf-fg-faint: #63758c;
--sf-cyan: #35e0ff;
--sf-cyan-2: #7ceaff;
--sf-amber: #ffb340;
--sf-mint: #7cf6c8;
--sf-red: #ff5f6d;
--sf-violet: #c9a6ff;
--sf-line: rgba( 53, 224, 255, 0.22 );
--sf-line-soft: rgba( 53, 224, 255, 0.09 );
--sf-glow: 0 0 8px rgba( 53, 224, 255, 0.3 );
--sf-mono: 'JetBrains Mono', 'SFMono-Regular', 'Menlo', 'Consolas', 'Noto Sans Mono', 'DejaVu Sans Mono', monospace;
--sf-display: 'Eurostile', 'Bahnschrift', 'DIN Alternate', 'Segoe UI Semibold', 'Noto Sans', sans-serif;
}

/* Native widgets, scrollbars and form controls follow the theme. */
html {
color-scheme: dark;
background-color: var(--sf-bg-deep);
}

body {
background-color: var(--sf-bg-deep);
color: var(--sf-fg);
}

::selection {
background: rgba( 53, 224, 255, 0.3 );
color: #fff;
}

/* ---------------------------------------------------------------- Header -- */

#mw-header-container {
background: linear-gradient( 180deg, #0b1322 0%, var(--sf-bg) 100% );
border-bottom: 1px solid var(--sf-line);
}

#mw-header-container.ts-container {
box-shadow: 0 1px 12px rgba( 0, 0, 0, 0.6 );
}

/* Site title, top left. */
#p-logo-text a {
color: var(--sf-cyan);
font-family: var(--sf-display);
font-weight: 600;
letter-spacing: 0.07em;
text-transform: uppercase;
white-space: nowrap;
text-shadow: var(--sf-glow);
}

#p-logo-text a:hover {
color: #fff;
text-decoration: none;
text-shadow: 0 0 10px rgba( 53, 224, 255, 0.7 );
}

/* The Maker Faire robot is flat red art on a white square. Inverting it turns
the white to black and the red to cyan; `lighten` then drops the black out
against the dark header, so it reads as a cyan HUD glyph with no re-upload. */
#p-logo img,
#p-logo a.mw-wiki-logo,
.mw-wiki-logo.timeless-logo {
max-width: 100%;
max-height: 80px;
width: auto;
height: auto;
}

/* Apply the inversion to the image only — putting it on the <a> as well would
invert twice and hand the red robot back. */
#p-logo img {
filter: invert( 1 ) saturate( 1.35 );
mix-blend-mode: lighten;
}

#p-logo {
padding: 0.5em 0;
overflow: hidden;
}

/* Accent stripe under the header: red/blue/green -> cyan/amber HUD bar. */
.color-left {
background: linear-gradient( 90deg, rgba( 53, 224, 255, 0 ) 0%, var(--sf-cyan) 100% );
}

.color-right {
background: linear-gradient( 90deg, var(--sf-amber) 0%, rgba( 255, 179, 64, 0 ) 100% );
}

.color-middle {
background: var(--sf-cyan);
box-shadow: 0 0 10px rgba( 53, 224, 255, 0.5 );
}

/* ---------------------------------------------------------------- Search -- */

#simpleSearch {
background: var(--sf-bg-deep);
border: 1px solid var(--sf-line);
border-radius: 0;
box-shadow: inset 0 0 12px rgba( 53, 224, 255, 0.06 );
}

#simpleSearch:focus-within {
border-color: var(--sf-cyan);
box-shadow: 0 0 0 1px rgba( 53, 224, 255, 0.35 ), inset 0 0 12px rgba( 53, 224, 255, 0.1 );
}

#searchInput {
color: var(--sf-fg);
font-family: var(--sf-mono);
font-size: 0.9em;
}

#searchInput::placeholder {
color: var(--sf-fg-faint);
}

/* Skin search glyph is a dark grey SVG; lift it onto the dark field. */
#searchButton,
#mw-searchButton {
filter: invert( 1 ) brightness( 1.1 );
opacity: 0.75;
}

.suggestions .suggestions-results,
.suggestions .suggestions-special {
background: var(--sf-panel-2);
border: 1px solid var(--sf-line);
color: var(--sf-fg);
}

.suggestions .suggestions-result {
color: var(--sf-fg);
}

.suggestions .suggestions-result-current,
.suggestions .suggestions-special.suggestions-result-current {
background: var(--sf-panel-3);
color: var(--sf-cyan);
}

/* --------------------------------------------------- Page / content shell -- */

#mw-content-container {
background-color: var(--sf-bg);
/* Skin ships a decorative cat as a backdrop; replace with a soft glow. */
background-image: radial-gradient( 900px 420px at 50% -120px, rgba( 53, 224, 255, 0.08 ), transparent 70% );
background-repeat: no-repeat;
background-position: center top;
border-bottom: 1px solid var(--sf-cyan);
box-shadow: inset 0 -1px 14px rgba( 53, 224, 255, 0.18 );
}

/* The main reading panel. */
#mw-content {
background: var(--sf-panel);
border: 1px solid var(--sf-line);
border-radius: 0;
box-shadow: 0 0 0 1px rgba( 0, 0, 0, 0.5 ), 0 8px 30px rgba( 0, 0, 0, 0.45 );
position: relative;
}

/* Corner bracket, top right — HUD framing without clipping any menus. */
#mw-content::before {
content: '';
position: absolute;
top: -1px;
right: -1px;
width: 22px;
height: 22px;
border-top: 2px solid var(--sf-cyan);
border-right: 2px solid var(--sf-cyan);
box-shadow: var(--sf-glow);
pointer-events: none;
}

#mw-content::after {
content: '';
position: absolute;
bottom: -1px;
left: -1px;
width: 22px;
height: 22px;
border-bottom: 2px solid var(--sf-cyan);
border-left: 2px solid var(--sf-cyan);
box-shadow: var(--sf-glow);
pointer-events: none;
}

/* ------------------------------------------------------------- Sidebars -- */

#mw-site-navigation .sidebar-chunk,
#mw-related-navigation .sidebar-chunk {
background: var(--sf-panel-2);
border: 1px solid var(--sf-line-soft);
border-radius: 0;
box-shadow: 0 4px 18px rgba( 0, 0, 0, 0.4 );
}

#mw-site-navigation .sidebar-inner,
#mw-related-navigation .sidebar-inner {
background: transparent;
border-radius: 0;
}

.sidebar-chunk .mw-portlet h3,
#mw-site-navigation h3,
#mw-related-navigation h3,
#personal h3 {
color: var(--sf-cyan);
font-family: var(--sf-display);
font-size: 0.8em;
font-weight: 600;
letter-spacing: 0.18em;
text-transform: uppercase;
border-bottom: 1px solid var(--sf-line-soft);
padding-bottom: 0.35em;
}

/* Leading marker on every nav link. */
.sidebar-chunk .mw-portlet-body li,
#personal-inner .mw-portlet-body li {
list-style: none;
}

.sidebar-chunk .mw-portlet-body li a::before,
#personal-inner .mw-portlet-body li a::before {
content: '\203A\00a0';
color: var(--sf-cyan);
opacity: 0.55;
}

.sidebar-chunk .mw-portlet-body li a:hover::before {
opacity: 1;
color: var(--sf-amber);
}

/* Personal tools dropdown (top right). */
#personal-inner.dropdown,
#personal .dropdown {
background: var(--sf-panel-2);
border: 1px solid var(--sf-line);
box-shadow: 0 6px 24px rgba( 0, 0, 0, 0.6 );
}

/* ----------------------------------------------------- Page action tabs -- */

#mw-page-header-links .mw-portlet h3,
#mw-page-header-links h3 {
color: var(--sf-fg-faint);
}

#mw-page-header-links .tools-inline li a {
color: var(--sf-fg-dim);
font-family: var(--sf-display);
font-size: 0.9em;
letter-spacing: 0.08em;
text-transform: uppercase;
border-bottom: 2px solid transparent;
}

#mw-page-header-links .tools-inline li a:hover {
color: var(--sf-cyan);
text-decoration: none;
border-bottom-color: var(--sf-line);
}

#mw-page-header-links .tools-inline li.selected a,
#mw-page-header-links .tools-inline li.selected a:visited {
color: var(--sf-cyan);
border-bottom-color: var(--sf-cyan);
text-shadow: var(--sf-glow);
}

/* ------------------------------------------------------------ Typography -- */

.mw-body-content {
line-height: 1.75;
color: var(--sf-fg);
}

#firstHeading,
.firstHeading {
color: #eaf6ff;
font-family: var(--sf-display);
font-weight: 600;
letter-spacing: 0.06em;
text-transform: uppercase;
border-bottom: 1px solid var(--sf-line);
padding-bottom: 0.35em;
text-shadow: 0 0 14px rgba( 53, 224, 255, 0.25 );
}

/* Small callsign above the title. */
#siteSub {
display: block;
color: var(--sf-fg-faint);
font-family: var(--sf-mono);
font-size: 0.72em;
letter-spacing: 0.22em;
text-transform: uppercase;
}

.mw-body-content h2,
.mw-body-content h3,
.mw-body-content h4 {
color: var(--sf-cyan);
font-family: var(--sf-display);
font-weight: 600;
}

.mw-body-content h2 {
margin-top: 1.8em;
padding: 0 0 0.3em 0.7em;
border-bottom: 1px solid var(--sf-line);
border-left: 3px solid var(--sf-cyan);
letter-spacing: 0.08em;
text-transform: uppercase;
text-shadow: var(--sf-glow);
background: linear-gradient( 90deg, rgba( 53, 224, 255, 0.1 ), transparent 55% );
}

.mw-body-content h3 {
margin-top: 1.4em;
padding-left: 0.7em;
color: var(--sf-cyan-2);
border-left: 2px solid var(--sf-line);
letter-spacing: 0.04em;
}

.mw-body-content h4 {
color: var(--sf-fg);
letter-spacing: 0.04em;
}

.mw-body-content b,
.mw-body-content strong {
color: #e6f3ff;
}

/* Section [edit] links. */
.mw-editsection,
.mw-editsection a {
color: var(--sf-fg-faint);
font-family: var(--sf-mono);
font-size: 0.75em;
text-transform: uppercase;
letter-spacing: 0.1em;
}

.mw-editsection a:hover {
color: var(--sf-amber);
}

/* ----------------------------------------------------------------- Links -- */

.mw-body-content a,
#mw-content a {
color: var(--sf-cyan);
}

.mw-body-content a:visited,
#mw-content a:visited {
color: #9bb8ff;
}

.mw-body-content a:hover,
#mw-content a:hover {
color: #fff;
text-shadow: var(--sf-glow);
}

.mw-body-content a.new,
#mw-content a.new,
a.new:visited,
.sidebar-chunk a.new {
color: var(--sf-red);
}

/* External links: drop the skin's blue icon for a HUD arrow. */
.mw-parser-output a.external {
background-image: none;
padding-right: 0;
border-bottom: 1px dotted var(--sf-line);
}

.mw-parser-output a.external::after {
content: '\2197';
color: var(--sf-amber);
font-size: 0.85em;
padding-left: 0.15em;
vertical-align: super;
}

/* Sidebar / footer links. */
.sidebar-chunk a,
#personal a,
#mw-footer a,
#catlinks a {
color: var(--sf-fg-dim);
}

.sidebar-chunk a:hover,
#personal a:hover,
#mw-footer a:hover,
#catlinks a:hover {
color: var(--sf-cyan);
text-decoration: none;
}

/* ----------------------------------------------------------------- Lists -- */

.mw-parser-output ul {
list-style: none;
padding-left: 1.4em;
}

.mw-parser-output ul > li {
margin-bottom: 0.4em;
position: relative;
}

.mw-parser-output ul > li::before {
content: '\25B8';
position: absolute;
left: -1.1em;
color: var(--sf-amber);
}

/* Nested bullets step down in weight. */
.mw-parser-output ul ul > li::before {
content: '\25AA';
color: var(--sf-cyan);
opacity: 0.7;
}

.mw-parser-output ol {
padding-left: 1.8em;
}

.mw-parser-output ol > li {
margin-bottom: 0.4em;
}

.mw-parser-output ol > li::marker {
color: var(--sf-amber);
font-family: var(--sf-mono);
}

/* Galleries and TOC keep their own list semantics — no HUD bullets there. */
.mw-parser-output ul.gallery > li::before,
.mw-parser-output #toc ul > li::before,
.mw-parser-output .toc ul > li::before {
content: none;
}

.mw-parser-output ul.gallery,
.mw-parser-output #toc ul {
padding-left: 0;
}

/* ------------------------------------------------------------------ Code -- */

.mw-body-content pre,
.mw-highlight pre,
.mw-parser-output pre {
background: var(--sf-bg-deep);
color: #dbe7f3;
border: 1px solid var(--sf-line);
border-left: 3px solid var(--sf-cyan);
border-radius: 0;
padding: 0.9em 1.1em;
overflow-x: auto;
font-family: var(--sf-mono);
font-size: 0.9em;
line-height: 1.55;
box-shadow: inset 0 0 24px rgba( 53, 224, 255, 0.05 );
/* Cut corner, bottom right. */
clip-path: polygon( 0 0, 100% 0, 100% calc( 100% - 12px ), calc( 100% - 12px ) 100%, 0 100% );
}

.mw-body-content code,
.mw-parser-output code,
.mw-body-content tt {
background: var(--sf-bg-deep);
color: var(--sf-mint);
border: 1px solid var(--sf-line-soft);
border-radius: 0;
padding: 0.05em 0.4em;
font-family: var(--sf-mono);
font-size: 0.9em;
}

.mw-body-content pre code {
background: transparent;
border: 0;
padding: 0;
color: inherit;
}

.mw-highlight,
.mw-highlight pre {
background: var(--sf-bg-deep);
}

/* Pygments ships a light theme (dark green keywords, dark red strings) which is
unreadable on this background. Remap the tokens the wiki actually uses. */
.mw-highlight .hll { background-color: rgba( 53, 224, 255, 0.12 ); }
.mw-highlight .c,
.mw-highlight .ch,
.mw-highlight .cm,
.mw-highlight .c1,
.mw-highlight .cs,
.mw-highlight .cpf { color: #5f7f95; font-style: italic; }
.mw-highlight .cp { color: var(--sf-amber); }
.mw-highlight .k,
.mw-highlight .kc,
.mw-highlight .kd,
.mw-highlight .kn,
.mw-highlight .kr { color: var(--sf-amber); font-weight: bold; }
.mw-highlight .kp { color: var(--sf-amber); font-weight: normal; }
.mw-highlight .kt { color: #ffd479; font-weight: normal; }
.mw-highlight .s,
.mw-highlight .s1,
.mw-highlight .s2,
.mw-highlight .sa,
.mw-highlight .sb,
.mw-highlight .sc,
.mw-highlight .dl,
.mw-highlight .sd,
.mw-highlight .se,
.mw-highlight .sh,
.mw-highlight .si,
.mw-highlight .sx,
.mw-highlight .sr,
.mw-highlight .ss { color: var(--sf-mint); }
.mw-highlight .m,
.mw-highlight .mb,
.mw-highlight .mf,
.mw-highlight .mh,
.mw-highlight .mi,
.mw-highlight .mo,
.mw-highlight .il { color: #ff9d7a; }
.mw-highlight .nb,
.mw-highlight .bp,
.mw-highlight .na { color: #9fd6ff; }
.mw-highlight .nc,
.mw-highlight .nn { color: var(--sf-cyan); font-weight: bold; }
.mw-highlight .nf,
.mw-highlight .fm { color: var(--sf-cyan); }
.mw-highlight .nt { color: var(--sf-amber); }
.mw-highlight .nv,
.mw-highlight .vc,
.mw-highlight .vg,
.mw-highlight .vi,
.mw-highlight .vm { color: var(--sf-violet); }
.mw-highlight .no { color: #ffd479; }
.mw-highlight .nd,
.mw-highlight .ne { color: #ff8fa3; }
.mw-highlight .o,
.mw-highlight .ow { color: #a9c0d6; }
.mw-highlight .p { color: var(--sf-fg-dim); }
.mw-highlight .err { color: var(--sf-red); border: 1px solid rgba( 255, 95, 109, 0.5 ); }
.mw-highlight .gd { color: var(--sf-red); }
.mw-highlight .gi { color: var(--sf-mint); }
.mw-highlight .go { color: var(--sf-fg-dim); }
.mw-highlight .gr,
.mw-highlight .gt { color: var(--sf-red); }
.mw-highlight .gh,
.mw-highlight .gp,
.mw-highlight .gu { color: var(--sf-cyan); font-weight: bold; }
.mw-highlight .linenos,
.mw-highlight .lineno,
.mw-highlight .linenodiv pre { color: var(--sf-fg-faint); background: transparent; }

/* Copy button shipped by SyntaxHighlight. */
.mw-highlight-copy,
.mw-highlight .mw-highlight-copy {
background: var(--sf-panel-3);
border: 1px solid var(--sf-line);
color: var(--sf-cyan);
}

/* ---------------------------------------------------------------- Tables -- */

.mw-body-content table.wikitable,
.mw-body-content .mw-datatable,
.mw-body-content table.mw_metadata {
background: var(--sf-panel-2);
color: var(--sf-fg);
border: 1px solid var(--sf-line);
border-collapse: collapse;
}

.mw-body-content table.wikitable > tr > th,
.mw-body-content table.wikitable > * > tr > th,
.mw-body-content .mw-datatable th,
.mw-body-content table.mw_metadata th {
background: var(--sf-panel-3);
color: var(--sf-cyan);
border: 1px solid var(--sf-line);
font-family: var(--sf-display);
letter-spacing: 0.08em;
text-transform: uppercase;
}

.mw-body-content table.wikitable > tr > td,
.mw-body-content table.wikitable > * > tr > td,
.mw-body-content .mw-datatable td,
.mw-body-content table.mw_metadata td {
border: 1px solid var(--sf-line-soft);
}

.mw-body-content table.wikitable > * > tr:hover > td {
background: rgba( 53, 224, 255, 0.05 );
}

/* The pin-out tables (Raspberry Pi) set cell fills inline. Those fills split
into light and dark, so each needs its own text colour — a single blanket
rule leaves half the pin numbers invisible. Values enumerated from the
wikitext: cyan / #00FF80 / magenta / yellow / orange are light; black, green
and red are dark. */
.mw-parser-output td[style*="#00FFFF" i],
.mw-parser-output td[style*="#00FF80" i],
.mw-parser-output td[style*="#FF00FF" i],
.mw-parser-output td[style*="cyan" i],
.mw-parser-output td[style*="yellow" i],
.mw-parser-output td[style*="orange" i],
.mw-parser-output td[style*="white" i],
.mw-parser-output th[style*="#00FFFF" i],
.mw-parser-output th[style*="yellow" i] {
color: #06121f !important;
}

.mw-parser-output td[style*="black" i],
.mw-parser-output td[style*="green" i],
.mw-parser-output td[style*="red" i],
.mw-parser-output td[style*="blue" i],
.mw-parser-output td[style*="navy" i],
.mw-parser-output td[style*="purple" i] {
color: #ffffff !important;
}

.mw-parser-output td[style*="background" i] a,
.mw-parser-output th[style*="background" i] a {
color: inherit !important;
text-decoration: underline;
}

/* Inline red text (used as a warning marker on a handful of pages) is too dark
against this background — lift it without changing the wikitext. */
.mw-parser-output [style*="color:red"],
.mw-parser-output [style*="color: red"],
.mw-parser-output [style*="color:#FF0000"],
.mw-parser-output [style*="color:#ff0000"],
.mw-parser-output [style*="color: #FF0000"] {
color: var(--sf-red) !important;
}

/* ---------------------------------------------------- Images & galleries -- */

.mw-body-content .thumbinner,
.mw-parser-output .thumbinner {
background: var(--sf-panel-2);
border: 1px solid var(--sf-line);
border-radius: 0;
box-shadow: 0 4px 18px rgba( 0, 0, 0, 0.45 );
}

.mw-body-content .thumbimage,
.mw-parser-output .thumbimage {
background: var(--sf-bg-deep);
border: 1px solid var(--sf-line-soft);
}

.mw-body-content .thumbcaption,
.mw-parser-output .thumbcaption {
color: var(--sf-fg-dim);
font-family: var(--sf-mono);
font-size: 0.85em;
line-height: 1.5;
}

/* Enlarge icon is a dark grey SVG. */
.mw-body-content .magnify a,
.mw-parser-output .magnify a {
filter: invert( 1 ) brightness( 1.1 );
opacity: 0.7;
}

.mw-body-content ul.gallery {
margin: 1.4em 0 2em;
}

.mw-body-content .gallerybox div.thumb {
background: var(--sf-panel-2);
border: 1px solid var(--sf-line);
border-radius: 0;
transition: border-color 0.15s ease, box-shadow 0.15s ease;
}

.mw-body-content .gallerybox:hover div.thumb {
border-color: var(--sf-cyan);
box-shadow: 0 0 14px rgba( 53, 224, 255, 0.35 );
}

.mw-body-content .gallerybox .thumb img {
border-radius: 0;
box-shadow: none;
}

.mw-body-content .gallerybox .gallerytext {
font-size: 0.88em;
color: var(--sf-fg-dim);
padding-top: 0.5em;
}

/* ------------------------------------------------------------------- TOC -- */

#toc,
.toc,
.toccolours {
background: var(--sf-bg-deep);
border: 1px solid var(--sf-line);
border-radius: 0;
box-shadow: inset 0 0 20px rgba( 53, 224, 255, 0.05 );
}

#toc .toctitle h2,
.toc .toctitle h2,
#mw-toc-heading {
color: var(--sf-cyan);
font-family: var(--sf-display);
font-size: 0.85em;
letter-spacing: 0.2em;
text-transform: uppercase;
border: 0;
background: none;
padding: 0;
text-shadow: none;
}

#toc .tocnumber,
.toc .tocnumber {
color: var(--sf-amber);
font-family: var(--sf-mono);
}

#toc .toctext,
.toc .toctext {
color: var(--sf-fg);
}

/* ------------------------------------------------- Categories & footer -- */

#catlinks,
.catlinks {
background: var(--sf-bg-deep);
border: 1px solid var(--sf-line-soft);
border-left: 3px solid var(--sf-amber);
border-radius: 0;
color: var(--sf-fg-dim);
}

#catlinks .mw-normal-catlinks > a {
color: var(--sf-amber);
font-family: var(--sf-display);
letter-spacing: 0.1em;
text-transform: uppercase;
font-size: 0.85em;
}

#mw-footer-container,
#mw-footer {
background: var(--sf-bg-deep);
color: var(--sf-fg-faint);
border-top: 1px solid var(--sf-line);
}

#mw-footer li,
#footer-info li {
color: var(--sf-fg-faint);
font-family: var(--sf-mono);
font-size: 0.82em;
}

/* -------------------------------------------------- Forms / editing UI -- */

textarea,
#wpTextbox1,
.mw-editform textarea {
background: var(--sf-bg-deep);
color: var(--sf-fg);
border: 1px solid var(--sf-line);
border-radius: 0;
caret-color: var(--sf-cyan);
font-family: var(--sf-mono);
}

textarea:focus,
#wpTextbox1:focus {
border-color: var(--sf-cyan);
box-shadow: 0 0 0 1px rgba( 53, 224, 255, 0.3 );
outline: 0;
}

input[type="text"],
input[type="search"],
input[type="password"],
input[type="number"],
select {
background: var(--sf-bg-deep);
color: var(--sf-fg);
border: 1px solid var(--sf-line);
border-radius: 0;
}

.mw-editform #wpSummary,
#wpSummary {
background: var(--sf-bg-deep);
color: var(--sf-fg);
border: 1px solid var(--sf-line);
}

/* Preview / diff / history and message boxes. */
table.diff,
table.diff td,
.mw-diff-table {
background: transparent;
color: var(--sf-fg);
}

td.diff-context,
.diff-context {
background: var(--sf-panel-2);
color: var(--sf-fg-dim);
border-color: var(--sf-line-soft);
}

td.diff-deletedline,
.diff-deletedline {
background: rgba( 255, 95, 109, 0.12 );
border-color: rgba( 255, 95, 109, 0.4 );
}

td.diff-addedline,
.diff-addedline {
background: rgba( 124, 246, 200, 0.12 );
border-color: rgba( 124, 246, 200, 0.4 );
}

.diff-deletedline .diffchange {
background: rgba( 255, 95, 109, 0.35 );
color: #fff;
}

.diff-addedline .diffchange {
background: rgba( 124, 246, 200, 0.3 );
color: #06121f;
}

.mw-message-box,
.mw-message-box-warning,
.mw-message-box-error,
.mw-message-box-success,
.warningbox,
.errorbox,
.successbox,
.mw-warning,
#mw-content .mw-message-box {
background: var(--sf-panel-2);
color: var(--sf-fg);
border: 1px solid var(--sf-line);
border-left: 3px solid var(--sf-amber);
border-radius: 0;
}

.mw-message-box-error,
.errorbox {
border-left-color: var(--sf-red);
}

.mw-message-box-success,
.successbox {
border-left-color: var(--sf-mint);
}

/* Special: pages and search results ride on .mw-body-content, but a few bits
carry their own light backgrounds. */
.mw-search-result-heading,
.searchresult {
color: var(--sf-fg);
}

.mw-search-results li {
border-bottom: 1px solid var(--sf-line-soft);
padding-bottom: 0.5em;
}

.mw-changeslist-line,
.mw-changeslist td,
.mw-changeslist th,
.mw-history-histlinks {
color: var(--sf-fg);
}

/* ------------------------------------------------- Narrow viewports (Timeless
switches to its stacked layout with drop-down menus at 850px) -- */

@media screen and ( max-width: 850px ) {
#mw-header-container {
background: var(--sf-bg);
}

/* Menu / user / tools toggles are dark grey SVGs on a dark bar. */
#user-tools h2,
.sidebar-chunk h2,
#ca-more span,
#ca-languages span,
.tools-inline li a {
filter: invert( 1 ) brightness( 1.15 );
}

.sidebar-inner,
.dropdown {
background: var(--sf-panel-2);
border: 1px solid var(--sf-line);
box-shadow: 0 8px 28px rgba( 0, 0, 0, 0.7 );
}

/* Backdrop behind an open menu was a light wash. */
#menus-cover {
background: #02060d;
opacity: 0.82;
}

#mw-content {
border-left: 0;
border-right: 0;
}

#mw-content::before,
#mw-content::after {
display: none;
}
}

/* --------------------------------------------------------------- Printing -- */

@media print {
/* Never print the dark theme — it wastes toner and reads badly on paper. */
body,
#mw-content,
#mw-content-container,
.mw-body-content,
#toc,
.toc,
#catlinks,
.mw-parser-output pre,
.mw-body-content pre,
.mw-highlight pre,
.mw-parser-output code,
.thumbinner {
background: #fff !important;
color: #000 !important;
box-shadow: none !important;
text-shadow: none !important;
}

.mw-body-content h2,
.mw-body-content h3,
#firstHeading {
color: #000 !important;
background: none !important;
text-shadow: none !important;
}

#p-logo img {
filter: none !important;
mix-blend-mode: normal !important;
}

#mw-content::before,
#mw-content::after {
display: none !important;
}
}

ST, STM32F4 Discovery

2026-08-23T10:18:28Z

Tommy：Remove links to pages that were never written

The '''STM32F4 Discovery''' is an ST Cortex-M4 board. These notes cover the GNU/ARM toolchain, building and flashing with ST-Link, and debugging with GDB.

[[File:IMAG4572 BURST001.jpg|thumb|200px|Dot matrix + servo + touch sensor]]
== Download the GNU/ARM toolchain ==
* tar -xvjf gcc-arm-none-eabi-4_8-2014q2-20131204-linux.tar.bz2
* export PATH=$PATH:~/gcc-arm-none-eabi-4_8-2014q2/bin
== Download and Build STLINK ==
* sudo apt-get install autoconf pkg-config libusb-1.0 git
* git clone https://github.com/texane/stlink.git
<syntaxhighlight lang="bash">
cd ~/stlink
./autogen.sh
./configure
make
</syntaxhighlight>
== Download STM32 Libraries and Blinky Example ==
* git clone https://github.com/rowol/stm32_discovery_arm_gcc
== Compile Your Source Code ==
* Edit Makefile
** STLINK=/home/rowol/stlink #Example, change to your location
** STM_COMMON=/home/rowol/stm32_discovery_arm_gcc/STM32F4-DISCOVERY_FW_V1.1.0
** make it
== Program ARM's Flash and Run Code ==
* make burn
or
* st-flash write STM32F4-Discovery.bin 0x08000000

== Using external ST-Link ==
* Remove CN3 jumper
<pre>
ST-Link STM32F4
VCC 3V
SWIO PA13
SWCLK PA14
VDD VDD ( depends on product, could range from 1.8v - 5v )
GND GND
</pre>

== GDB ==
<pre>
In the directory with your source code, I've also add a .gdbinit file which contains:

define reload
kill
monitor jtag_reset
load
end

target extended localhost:4242
load

This will execute whenever you start GDB in the source directory

To start up:

~/stlink/st-util #Start GDB server
arm-none-eabi-gdb main.elf #In a second terminal window, start GDB

continue #Starts code running, or use other GDB commands to
# set breakpoints, etc first...

</pre>

== Related projects ==
* [[Application - MPR121, capacitive touch sensor controller]]
* [[Application - MAX7219, Serially Interfaced, 8-Digit LED Display Drivers (interact with MPR121)]]
* [[Application - MAX7219, Serially Interfaced, 8-Digit LED Display Drivers (scrolling text)]]
* [[Application - MG90S, Metal Gear Servo]]
* [[Application - Joystick]]
* [[Application - nRF52, (BLE - UART - STM32F4)]]
* [[Application - MeArm, mini robotic arm]]

== Reference ==
* [https://launchpad.net/gcc-arm-embedded/+download ARM toolchain]
* [http://www.wolinlabs.com/blog/linux.stm32.discovery.gcc.html STM32 Discovery Development On Linux]

* [http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419 STM32F4 Discovery Kit Resource Page]
* [http://www.arm.com/products/processors/cortex-m/cortex-microcontroller-software-interface-standard.php CMSIS - Cortex Microcontroller Software Interface Standard]
* [http://rusefi.com/wiki/index.php?title=Hardware:stm32f4discovery_repair Hardware:stm32f4discovery repair]

[[Category:Boards and SoCs]]

Nordic, nRF52 Preview DK

2026-08-23T10:18:28Z

Tommy：Remove links to pages that were never written

The '''nRF52 Preview DK''' is Nordic's development kit for the nRF52832. These notes cover the SDK, JLink, the GCC toolchain, and programming the board.

== Prepare ==
=== Install SDK ===
# Get latest SDK from https://developer.nordicsemi.com/nRF52_SDK/nRF52_SDK_v0.x.x/ (ex. nRF52_SDK_0.9.2_dbc28c9.zip)
# Get SDK with FreeRTOS example from http://developer.nordicsemi.com/nRF5_SDK/nRF5_SDK_v11.x.x/ (nRF5_SDK_11.0.0-2.alpha_bc3f6a0.zip)
# Edit ./components/toolchain/gcc/Makefile.posix to fit your toolchain setting if necessary

=== Install JLink ===
# Download "Software and Document pack" from https://www.segger.com/jlink-software.html according your platform (ex. x86_64)
# decompress and make a symbolic to /opt/SEGGER/JLink
## ln -s ~/Downloads/JLink_Linux_V510c_x86_64 /opt/SEGGER/JLink
=== Toolchain ===
sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded
sudo apt-get update
sudo apt-get install gcc-arm-none-eabi
=== Programming ===
<syntaxhighlight lang="bash">
1. Softdevice
ex.
sudo /home/tommy/projects/mbed/nRF52/NrfJProg_7_7_0_Linux/nrfjprog --family NRF52 --program ~/projects/mbed/nRF52/s132_nrf52_1.0.0-3.alpha/s132_nrf52_1.0.0-3.alpha_softdevice.hex

2. change dir to example
ex.
sudo ~/projects/mbed/nRF52/NrfJProg_7_7_0_Linux/nrfjprog --sectorerase --family nRF52 --program _build/nrf52832_xxaa_s132.hex

3. sudo ~/projects/mbed/nRF52/NrfJProg_7_7_0_Linux/nrfjprog --sectorerase --family nRF52 --program _build/nrf52832_xxaa.hex
4. power recycle to take effect
</syntaxhighlight>
<pre>
tommy@tommy-HP-EliteBook-Folio-1040-G2:~/projects/mbed/nordic/nRF52/nRF5_SDK_11.0.0_89a8197/examples/ble_peripheral/ble_app_beacon/pca10040/s132/armgcc$ sudo ~/projects/mbed/nordic/tools/nrfjprog --sectorerase --family nRF52 --program ~/projects/mbed/nordic/nRF52/s132/s132_nrf52_1.0.0-3.alpha_softdevice.hex
Parsing hex file.
Erasing page at address 0x0.
Erasing page at address 0x3000.
Erasing page at address 0x4000.
Erasing page at address 0x5000.
Erasing page at address 0x6000.
Erasing page at address 0x7000.
Erasing page at address 0x8000.
Erasing page at address 0x9000.
Erasing page at address 0xA000.
Erasing page at address 0xB000.
Erasing page at address 0xC000.
Erasing page at address 0xD000.
Erasing page at address 0xE000.
Erasing page at address 0xF000.
Erasing page at address 0x10000.
Erasing page at address 0x11000.
Erasing page at address 0x12000.
Erasing page at address 0x13000.
Erasing page at address 0x14000.
Erasing page at address 0x15000.
Erasing page at address 0x16000.
Erasing page at address 0x17000.
Erasing page at address 0x18000.
Erasing page at address 0x19000.
Erasing page at address 0x1A000.
Erasing page at address 0x1B000.
Erasing page at address 0x1C000.
Erasing page at address 0x1D000.
Applying system reset.
Checking that the area to write is not protected.
Programing device.
tommy@tommy-HP-EliteBook-Folio-1040-G2:~/projects/mbed/nordic/nRF52/nRF5_SDK_11.0.0_89a8197/examples/ble_peripheral/ble_app_beacon/pca10040/s132/armgcc$ sudo ~/projects/mbed/nordic/tools/nrfjprog --sectorerase --family nRF52 --program _build/nrf52832_xxaa_s132.hex
Parsing hex file.
Erasing page at address 0x1C000.
Erasing page at address 0x1D000.
Erasing page at address 0x1E000.
Erasing page at address 0x1F000.
Applying system reset.
Checking that the area to write is not protected.
Programing device.

</pre>

=== Console, UART ===
[[File:nrf52_cp2105.jpg|border|350px|nRF52 preview DK + CP2105]]
* cp2105 in host
<pre>
nRF52 Host
-----------------
RX TX
CTS RTS
TX RX
RTS CTS
</pre>

=== Tool, nRF Connect ===
[[File:Nrf-connect.png|border|350px|nRF Connect v1.0]]

=== App source ===
* git clone https://github.com/NordicSemiconductor/Android-nRF-Toolbox

=== SDK ===
* git clone https://bitbucket.org/tommy0804/nrf52 (based on nRF52_SDK_0.9.2_dbc28c9.zip)

[[Category:Boards and SoCs]]

ESP8266, Wi-Fi SoC

2026-08-23T10:18:28Z

Tommy：Remove links to pages that were never written

The '''ESP8266''' is a Wi-Fi SoC usually met on a NodeMCU DevKit board. These notes cover flashing the NodeMCU firmware, the ESPlorer and Arduino IDE toolchains, and a few Lua examples.

[[File:Esp8266 nodemcu.jpg|thumb|300px|ESP8266 NodeMCU]]
== Pin definition ==
[[File:Esp8266 Pinout.png| ESP8266 pin definition]]
== Pre-build firmware ==
* Download
** git clone https://github.com/nodemcu/nodemcu-firmware/releases
== NodeMCU flasher ==
<pre>
NodeMCU flasher is a firmware programmer for NodeMCU DEVKIT V0.9.
You can use it to program NodeMCU DEVKIT or your own ESP8266 board.
You MUST set GPIO0 to LOW before programming, and NodeMCU DEVKIT V0.9 will do it automatically.
</pre>
[[File:ESP8266Flasher_1.png|250px|ESP8266Flasher_1]][[File:ESP8266Flasher_2.png|250px|ESP8266Flasher_2]][[File:ESP8266Flasher_3.png|250px|ESP8266Flasher_3]][[File:ESP8266Flasher_4.png|250px|ESP8266Flasher_4]][[File:ESP8266Flasher_5.png|250px|ESP8266Flasher_5]]
* Download
** git clone https://github.com/nodemcu/nodemcu-flasher
** Choice the Win32 / Win64 against your environment
* Prepare & running
** So far, it seems like only can flash success in Windows environment

== ESPlorer ==
[[File:Esplorer.jpg|500px|Esplorer]]
* Download
** http://esp8266.ru/esplorer/#download
* Build from source
<pre>
1. Install Netbeans 8.1, download from here. I used the "All", but I think Java SE should be enough.
2. Install JDK 1.7 (I wasn't able to use JDK 1.8), download from here.
3. Download rsyntaxtextarea 2.5.6.jar (I wasn't able to use any other version) from here, put it somewhere and remember where (e.g.: inside the ESPlorer root dir)
4. Open the project.properties file in a texteditor, and edit file.reference.rsyntaxtextarea-2.5.6.jar to point to where you put rsyntaxtextarea 2.5.6.jar
5. Open netbeans
6. Open the ESPlorer project, you should get an error about the JDK platform
7. Click resolve, add platform
8. Add the JDK 1.7 dir, and where it says Name you should see "JDK 1.7", rename that to "JDK1.7" (notice the lack of a space), close the dialog 9 press F11 to build
9. The ESPLorer .jar should be under the dist subdir
</pre>
* Prepare & running
** Install java
** java -jar EXPlorer.jar

== Breathing LED ==
<syntaxhighlight lang="lua">
pwm.setup(2, 500, 512)
pwm.start(2)

pwm.setduty(2, 0)
i = 0

while true do
while i < 512 do
pwm.setduty(2, i)
i=i+5
tmr.delay(20000)
end

tmr.delay(100000)

while i > 0 do
pwm.setduty(2, i)
i=i-5
tmr.delay(20000)
end

tmr.delay(50000)
end
</syntaxhighlight>

== httpserver to control GPIO ==
* Lua script ( <span style="color:#ff0000">wifi.sta.config SHOULD provide real AP information</span>)
<syntaxhighlight lang="lua">
wifi.setmode(wifi.STATION)
wifi.sta.config("YOUR_NETWORK_NAME","YOUR_NETWORK_PASSWORD")
print(wifi.sta.getip())
led1 = 3
led2 = 4
gpio.mode(led1, gpio.OUTPUT)
gpio.mode(led2, gpio.OUTPUT)
srv=net.createServer(net.TCP)
srv:listen(80,function(conn)
conn:on("receive", function(client,request)
local buf = "";
local _, _, method, path, vars = string.find(request, "([A-Z]+) (.+)?(.+) HTTP");
if(method == nil)then
_, _, method, path = string.find(request, "([A-Z]+) (.+) HTTP");
end
local _GET = {}
if (vars ~= nil)then
for k, v in string.gmatch(vars, "(%w+)=(%w+)&*") do
_GET[k] = v
end
end
buf = buf.."<h1> ESP8266 Web Server</h1>";
buf = buf.."<p>GPIO0 <a href=\"?pin=ON1\"><button>ON</button></a> <a href=\"?pin=OFF1\"><button>OFF</button></a></p>";
buf = buf.."<p>GPIO2 <a href=\"?pin=ON2\"><button>ON</button></a> <a href=\"?pin=OFF2\"><button>OFF</button></a></p>";
local _on,_off = "",""
if(_GET.pin == "ON1")then
gpio.write(led1, gpio.HIGH);
elseif(_GET.pin == "OFF1")then
gpio.write(led1, gpio.LOW);
elseif(_GET.pin == "ON2")then
gpio.write(led2, gpio.HIGH);
elseif(_GET.pin == "OFF2")then
gpio.write(led2, gpio.LOW);
end
client:send(buf);
client:close();
collectgarbage();
end)
end)
</syntaxhighlight>
* Accessing your web server
<pre>
When your ESP8266 restarts it prints in your serial monitor the IP address of your ESP8266.
If you type your ESP8266 IP address in your web browser, you can access your web server.
In my case it’s http://192.168.1.8.
</pre>
[[File:Esp8266_httpserver.png|250px| http server for GPIO control ]]

== Using Arduino IDE as ESP8266 development tool ==
* Download the Arduino IDE 1.8.2 above
* Go to File --> Preferences and add the link http://arduino.esp8266.com/stable/package_esp8266com_index.json to the Additional Boards Manager URLS.
* Go to Tools --> Board --> Boards manager
* You should now have the esp8266 as an option there since you've added it to the Additional Boards. Select it and press Install
* Wait, and then, ....
* Now, You have the ESP8266 boards configure. Choose the board you have, "Generic ESP8266 Module" if you got the regular module

== Reference ==
* [https://zh.wikipedia.org/zh-tw/NodeMCU wiki - NodeMCU]
* [http://nodemcu.com/index_en.html NodeMCU]
* [https://github.com/nodemcu/nodemcu-flasher NMCU flasher]
* [http://www.esp8266.com/viewtopic.php?f=22&t=882 ESPlorer]
* [https://github.com/devyte/nodemcu-platform/wiki/How-to-build-ESPlorer-from-sources How-to-build-ESPlorer-from-sources]
* [http://randomnerdtutorials.com/esp8266-web-server/ ESP8266 Web Server Tutorial]
* [http://www.whatimade.today/esp8266-easiest-way-to-program-so-far/ ESP8266 - Easiest way to program so far (Using Arduino IDE)]

[[Category:Boards and SoCs]]

Application - Alexa

2026-08-23T10:18:27Z

Tommy：Remove links to pages that were never written

Running '''Alexa Voice Service''' on a Raspberry Pi and driving smart-home devices through AWS Lambda and AWS IoT, through to skill certification.

[[File:Alexa-logo-3.png|thumb|300px|Alexa Logo]]
[[File:RPi3_ALEXA.JPG|thumb|300px|RPi3_Alexa]]
== Hardware ==
* PRi
* Speaker
* Microphone

== OS ==
* Raspbian

== Software ==
* Configure AVS(Alexa Voice Service)
** https://developer.amazon.com/avs/home.html
* Connect AVS in your Pi
** git clone https://github.com/novaspirit/AlexaPi/
** Go to AlexaPi, then, run "python main.py"
*Software apps and online services:
** Alexa Skills Kit
** AWS Lambda
** AWS IoT
** Alexa Voice Service

== Python requirement ==
* pip install --upgrade pip
* pip install --upgrade requests

== Configure AWS CLI ==
<pre>
pi@raspberrypi:~/projects/rpi/alexa/AWShome $ aws configure
AWS Access Key ID [None]: AKIAIOSFODNN7EXAMPLE
AWS Secret Access Key [None]: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Default region name [None]: us-east-1
Default output format [None]:
</pre>

== Smart home arch ==
[[File:Avs_lambda_iot.jpeg|AVS_Lambda_IOT]]

== Create the Things using AWS IoT ==
* update awscli version to 1.11.75 above
<pre>
pi@raspberrypi:~/projects/rpi/alexa/AWShome $ aws iot create-thing --thing-name floor-lamp
usage: aws [options] <command> <subcommand> [parameters]
aws: error: argument command: Invalid choice, valid choices are:

autoscaling | cloudformation
cloudfront | cloudsearch
cloudsearchdomain | cloudtrail
cloudwatch | cognito-identity
cognito-sync | datapipeline
directconnect | dynamodb
ec2 | elasticache
elasticbeanstalk | elastictranscoder
elb | emr
iam | importexport
kinesis | logs
opsworks | rds
redshift | route53
route53domains | sdb
ses | sns
sqs | storagegateway
sts | support
swf | s3api
s3 | configure
help
</pre>

== ALEXA Skill submit ==
[[File:Alexa_skill_submit.jpg|Alexa skills submit]]

== ALEXA Skill has passed Amazon certification process ==
[[File:Amazon_skill_passed.jpg|Your Alexa skill Project K is now live!]]

== ALEXA Skill Alive ==
[[File:Amazon_skill_alive.jpg| skill alive]]

== Search my skill in amazon.com ==
[[File:Amazon_search_project_k.jpg|Search skill in amazon.com]]

== Reference ==
* [https://blog.yorkxin.org/2013/09/30/oauth2-1-introduction OAuth 2.0 筆記 (1) 世界觀]
* [https://www.hackster.io/awshome/awshome-home-automation-using-rpi-alexa-iot-a3d3dc AWShome - Home automation using RPi + Alexa + IoT]
* [https://developer.amazon.com/blogs/post/TxWSCWZI9SPYNT/Coding-Smart-Home-Skill-Adapter-Directives-Using-Node-js Coding Smart Home Skill Adapter Directives Using Node.js]
* [https://developer.amazon.com/blogs/post/Tx480XF5QCA6IN/managing-device-discovery-for-your-alexa-smart-home-skill Managing Device Discovery for Your Alexa Smart Home Skill]
* [https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/linking-an-alexa-user-with-a-user-in-your-system Linking an Alexa User with a User in Your System]

[[Category:Projects]]

首頁

2026-08-23T10:12:31Z

Tommy：Replace imported text with a locally written page

== About Tommy C. Liu ==
* Welcome to discuss outsourcing project
** FW/SW development
** Training course
* E-mail: tommy.using@gmail.com
* LinkedIn: https://www.linkedin.com/in/chia-chuan-liu-7706b473/
<gallery mode="packed" heights="156">
File:3D_ripples_01.gif|3D LED cube – ripple effect
File:MeArm_stm32f4.jpg|MeArm robotic arm driven by STM32F4
File:Gps_wifiap.jpg|GPS tracker with Wi-Fi AP
File:Eye_tracker_alexa.jpg|Eye tracker with Alexa and AWS IoT
</gallery>

=== Browse by category ===
* [[:Category:Projects|Projects]] — hands-on builds and application notes (31)
* [[:Category:Boards and SoCs|Boards and SoCs]] — dev boards, MCUs and SoCs (23)
* [[:Category:Software and Tools|Software and Tools]] — OS, build and test tooling (10)
* [[:Category:Sensors and Modules|Sensors and Modules]] — sensors and peripheral modules (5)
* [[:Category:Software Engineering|Software Engineering]] — process and practice (3)
* [[:Category:Connectivity|Connectivity]] — buses and wireless protocols (2)

=== CI/CD ===

* [[Jenkins]]

=== Equipments ===
* Measurement
** Logic Analyzer
*** Max Sample Rate 400MHz
*** 16G stream / 256M buffer
*** 16 Channels
** Multimeter

* Computings
** Linux server - Intel Xeon E3-1231 v3(8 cores)
*** Intel(R) Xeon(R) CPU E3-1230 v3
*** 24G RAM
** Windows desktop
*** Intel(R) Xeon(R) CPU E3-1231
** Linux laptop
*** i7-7600U
*** 16G RAM

=== Rule ==
* [[Software version]]
* [[Software release life cycle]]
=== Article ===
* [[如何用正確的方法來寫出品質好的軟體的75條體會]]
* [[Tomato Firmware]]

Tomato Firmware

2026-08-23T10:12:30Z

Tommy：Replace imported text with a locally written page

'''Tomato''' is a free Linux-based replacement firmware for consumer wireless
routers, mostly Broadcom-based ones. It derives from HyperWRT and is known for a
compact Ajax web interface with SVG bandwidth graphs.

== Features ==
* Ajax web interface, with real-time bandwidth and connection graphs
* QoS with per-connection classification
* Access as CLI over telnet or SSH (Dropbear), plus BusyBox userland
* Wireless modes beyond AP: client, bridge and WDS
* DHCP and DNS through Dnsmasq, dynamic DNS, Wake-on-LAN
* Static routing, port forwarding, UPnP and NAT-PMP
* Scripting hooks on firewall, init and shutdown

== Hardware ==
Originally the Linksys WRT54G family; later builds cover a wider range of
Broadcom-based Linksys, Asus, Netgear and Buffalo routers. Check a specific model
against the build you intend to flash before flashing it.

== Forks ==
Development moved into forks. '''TomatoUSB''' added USB and NAS support;
'''Shibby''' and '''FreshTomato''' carried it forward from there.

== See also ==
* [https://openwrt.org/ OpenWrt] - the general-purpose alternative, far wider hardware support
* [https://dd-wrt.com/ DD-WRT] - the other long-running Broadcom-focused firmware

== Reference ==
* [https://en.wikipedia.org/wiki/Tomato_(firmware) Tomato (firmware) - Wikipedia]

[[Category:Software and Tools]]

Software version

2026-08-23T10:12:30Z

Tommy：Replace imported text with a locally written page

'''Software versioning''' is the practice of assigning identifiers to distinct
releases. This page records the scheme used on this wiki and the alternatives it
was chosen over.

== Scheme used here ==
Four sequences, '''major.minor.patch.build''' - the form used by the release logs
on [[ASTAR]], [[RTD1073]], [[Netgem]] and [[Tiny6410]], for example
<code>NTV350_Diag_1.0.3.4</code>.

{| class="wikitable"
! Field !! Increment when
|-
| major || The interface changes in a way that breaks existing users.
|-
| minor || Features are added, but existing users are unaffected.
|-
| patch || Only defects are fixed.
|-
| build || A new build of otherwise identical source.
|}

Any field that increments resets every field to its right.

== Other schemes ==
* '''Semantic versioning''' - three sequences with the same major/minor/patch
rules made explicit and machine-checkable. See [https://semver.org/ semver.org].
* '''Date-based''' - <code>2015.04</code> or <code>20150401</code>. Says when, not
what changed; useful for rolling releases.
* '''Year of release''' - marketing-facing, e.g. Windows 95. Carries no ordering
information for a maintainer.
* '''Degree of compatibility''' - some projects encode ABI compatibility in the
major number so a linker can reason about it.

== Practice ==
* The version in the binary and the version in the tag must match. If they can
disagree, they eventually will.
* Never reuse a version number, even for a build that was never shipped.
* An unreleased tree carries the next version with a suffix, not the last
released version.

== Reference ==
* [https://en.wikipedia.org/wiki/Software_versioning Software versioning - Wikipedia]
* [https://semver.org/ Semantic Versioning]

[[Category:Software Engineering]]

Software release life cycle

2026-08-23T10:12:30Z

Tommy：Replace imported text with a locally written page

The '''software release life cycle''' is the sequence of stages a piece of
software passes through, from first build to end of life. These are the stage
names used on this wiki.

== Stages ==
{| class="wikitable"
! Stage !! Meaning
|-
| Pre-alpha || Anything before feature freeze - design, coding, unit testing.
|-
| Alpha || Feature complete is not expected. Tested internally, usually by the developers. Known to be unstable.
|-
| Beta || Feature complete, but not bug complete. Given to testers outside the team; a '''closed beta''' goes to invited testers, an '''open beta''' to anyone.
|-
| Release candidate || Beta with no known blocking defects. Ships as the release unless something new is found.
|-
| RTM || Release to manufacturing. The build handed to the customer or to production.
|-
| GA || General availability. The build published to everyone, through whatever channel it ships in.
|-
| Support || Defect fixes and service releases against a shipped version.
|-
| End of life || No further fixes. The version is no longer supported.
|}

== Freezes ==
* '''Feature freeze''' - no new features accepted; only defect fixes.
* '''Code freeze''' - no changes at all except those fixing a blocking defect.

== Practice ==
* Do not call a build beta until it is feature complete - it makes the remaining
defect count meaningless.
* A release candidate that needs a change becomes a new release candidate, not a
patched one.
* Tag every build that leaves the team, so a defect report can be tied to a
specific tree.

== Reference ==
* [https://en.wikipedia.org/wiki/Software_release_life_cycle Software release life cycle - Wikipedia]

[[Category:Software Engineering]]

Tomato Firmware

2026-08-23T10:01:25Z

Tommy：Consistency: syntax highlighting for code, File: prefix

{{Infobox software
|name= Tomato Firmware
|logo= [[File:Tuxt.png]]
|screenshot= [[File:Tomato Firmware - Bandwidth Real Time.PNG|250px]]
|caption= Real time bandwidth view, running on a [[AirStation|Buffalo AirStation]] [[AirStation#WHR_series|WHR-HP-G54]] as rendered by the [[Opera (web browser)|Opera]] web browser

|Description= [[Open Source]] [[RouterOS]]
|developer= <br />Jonathan Zarate
|latest release version= 1.28
|latest release date= {{release date and age|2010|6|28}}
|latest preview version=
|latest preview date=
|operating system= Linux
|genre= Routing software
|license= [[Freeware]] <br />Backend: [[GNU General Public License]] <br />Frontend: proprietary
|website= [http://www.polarcloud.com/tomato www.polarcloud.com/tomato]
}}

'''Tomato Firmware''' is a [[Free software|free]] [[HyperWRT]]-based, [[Linux]] core [[firmware]] distribution for mostly [[Broadcom]] [[chipset]] based [[wireless router]]s, most notably the older-model [[Linksys]] [[WRT54G]] (including the [[WRT54GL]] and [[WRT54GS]]), [[AirStation|Buffalo AirStation]], [[Asus Routers]] and [[Netgear]]'s [[WNR3500L]]. Among other notable features is the user interface, which makes heavy use of [[AJAX]] as well as an [[Scalable Vector Graphics|SVG]]-based graphical bandwidth monitor.

==Features==

* Interactive [[Ajax framework|Ajax]] based GUI using [[scalable vector graphics|SVG]] and CSS-based color schemes (allowing [[Graphical user interface|GUI]] look and feel changes).
* [[Command-line interface|CLI]] access ([[BusyBox]]) via [[TELNET]] or [[Secure Shell|SSH]] (using [[Dropbear (software)|Dropbear]]).
* [[DHCP]] server.
* DNS forwarder (using [[Dnsmasq]]).
* Netfilter/iptables with customizable settings, IPP2P and l7-filter.
* [[Wake-on-LAN]].
* Advanced [[Quality of service|QoS]]: 10 unique QoS classes defined, real-time graphs display prioritized traffic with traffic class details.
* Client Bandwidth Control via QoS classes
* Bandwidth graphing/statistics.
* Wireless modes:
** Access point ([[Wireless access point|AP]])
** Wireless client station (STA)
** Wireless ethernet (WET) bridge
** Wireless distribution system ([[Wireless Distribution System|WDS]] aka wireless bridging)
** Simultaneous AP and WDS (aka wireless repeating).
* [[Dynamic DNS]] service with ezUpdate and services extended for more providers.
* Syslog viewable through the GUI (also downloadable).
* SES button control.
* [[JFFS2]].
* [[Server Message Block|CIFS]] client.
* [[Wireless LAN]] Radio power of adjustment, antenna selection, and 14 wireless channels.
* 'Boot wait' protection (increase the time slot for uploading firmware via the boot loader).
* Advanced [[port forwarding]], redirection, and triggering with [[Universal Plug and Play|UPnP]] and [[NAT Port Mapping Protocol|NAT-PMP]].
* Advanced user access restrictions.
* Init, Shutdown, [[Firewall (computing)|Firewall]], and WAN Up [[Scripting language|script]]s.
* Uptime, load average, and free memory status.
* Minimal reboots - Very few configuration changes require a reboot.
* Wireless survey page to view other networks in your neighborhood.
* More comprehensive dashboard than stock firmware: displays signal strengths of wireless client devices, reveals UPnP mappings.
===Feature comparison===

{| style="border=1 cellspacing=0 cellpadding=3 class="wikitable"
|-style="background-color:#eee;"
! Mod Name
! Base Tomato<br/>Version
! Min Flash MB
! Max<br/>Connections
! SpeedMod
! SFTP
! VPN<br/>Client
! VPN<br/>Server
! SNMP
! SD Card<br/>Support
! USB<br/>Support
! VLANs
! IPv6<br/>Support
|-
! Tomato
| {{yes|1.28}}
| 4MB
| {{yes|4096}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! Tomato ND
| {{yes|1.28}}
| 4MB
| {{yes|4096}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! TomatoUSB <ref>[http://tomatousb.org/ TomatoUSB] release announcement.</ref><ref>[http://www.linksysinfo.org/forums/showthread.php?t=60185 Teddy Bear] Mod release announcement.</ref>
| {{yes|1.28<sup>**</sup>}}
| 4MB/8MB
| {{yes|10240}}
| {{yes}}
| {{yes}}
| {{yes|OpenVPN}}
| {{yes|OpenVPN}}
| {{no}}
| {{no}}
| {{yes|Print, NAS}}
| {{no}}
| {{no}}
|-
! TomatoVPN <ref>[http://tomatovpn.keithmoyer.com/search/label/release TomatoVPN] release announcement.</ref>
| {{yes|1.27<sup>***</sup>}}
|
|
| {{no}}
| {{no}}
| {{yes|OpenVPN}}
| {{yes|OpenVPN}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! hardc0re Mod <ref>[http://touristinparadise.blogspot.com/2008/04/linksys-wrt54gl-routers-improving.html hardc0re] release announcement.</ref>
| {{yes|1.28}}
| 4MB
| {{yes|8192+}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|-
! jyavenard Mod <ref>[http://www.linksysinfo.org/forums/showpost.php?p=336696&postcount=28 jyavenard] release announcement.</ref>
| {{no|1.23}}
|
|
|
|
| {{yes|PPTP}}
|
| {{yes}}
|
|
| {{no}}
| {{no}}
|-
! Neorouter Mod <ref>[http://www.neorouter.com/forum/viewtopic.php?f=2&t=1015 Neorouter] release announcement.</ref>
| {{no|1.25<sup>***</sup>}}
|
|
|
|
| {{yes|''proprietary''}}
| {{yes|''proprietary''}}
|
|
|
| {{Yes}}
| {{no}}
|-
! roadkill Mod <ref>[http://www.linksysinfo.org/forums/showthread.php?t=53233 roadkill] release announcement.</ref>
| {{no|1.21}}
|
|
|
| {{yes}}
| {{yes|OpenVPN}}
| {{yes|OpenVPN}}
|
| {{yes|SD, MMC}}
|
| {{no}}
| {{no}}
|-
! slodki Mod <ref>[http://gemini.net.pl/~slodki/tomato-sdhc.html slodki] release announcement.</ref>
| {{yes|1.25<sup>*</sup>}}
| 4MB
| {{yes|4096}}
| {{no}}
| {{no}}
| {{yes|OpenVPN}}
| {{yes|OpenVPN}}
| {{no}}
| {{yes|SDHC, MMC}}
| {{no}}
| {{no}}
| {{no}}
|-
! Thor Mod <ref>[http://www.linksysinfo.org/forums/showthread.php?t=61552 Thor] release announcement.</ref>
| {{yes|1.25<sup>**</sup>}}
| 8MB
| {{yes|8192}}
| {{yes}}
| FTP only
| {{yes|OpenVPN}}
| {{yes|OpenVPN}}
| {{yes}}
| {{yes|SDHC, MMC}}
| {{yes|NAS}}
| {{no}}
| {{no}}
|-
! Trzepako Mod <ref>[http://www.linksysinfo.org/forums/showthread.php?t=58722 Trzepako] release announcement.</ref>
| {{no|1.21}}
| 4MB
|
| {{yes}}
|
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|
| {{no}}
| {{no}}
|-
! Victek Mod. Tomato RAF <ref>[http://www.linksysinfo.org/forums/showthread.php?t=62248 Victek Mod. Tomato RAF] release announcement.</ref>
| {{yes|1.25<sup>***</sup>}}
| 4MB
| {{yes|8192}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
|
| {{no}}
| {{no}}
|-
! Tomato DualWAN Mod <ref>[http://www.dualwan.cn/index.php/download/category/12-1.23 Tomato DualWAN Mod] release announcement.</ref>
| {{yes|1.23<sup>***</sup>}}
| 4MB/8MB
| {{yes|10240}}
| {{yes}}
| {{yes}}
| {{yes|PPTP}}
| {{yes|PPTP}}
| {{yes}}
| {{no}}
| {{yes|NAS, 3G USB Modem}}
| {{yes}}
| {{no}}
|}
{|cellspacing=3 cellpadding=0
|-
| align="right" | <sup>*</sup>
| Tomato standard only
|-
| align="right" | <sup>**</sup>
| Tomato ND (New Driver) only
|-
| align="right" | <sup>***</sup>
| Tomato standard and ND
|}

==License==

Tomato is based on the GPL source code released by Linksys, but includes proprietary binary modules from the chipset manufacturer Broadcom. Portions of the code are licensed under the [[GNU General Public License]], but the source code for the user interface is under a more restrictive license which forbids use without the author's permission.

==Compatible routers==
{{Main|wikibooks:Tomato (firmware)}}

Tomato is compatible with many [[Broadcom]]-based routers, including [[Asus routers]], [[Buffalo Technology|Buffalo]] [[AirStation]], and the [[Linksys WRT54G series]]. Detailed information is available from [[wikibooks:Tomato (firmware)|the Wikibooks page on Tomato]]. WRT54G models of version 5 and newer are not compatible. Tomato is generally recommended by Community Forums for Linksys Devices, Ex.. LinksysInfo.org, for users who desire an alternative to [[DD-WRT]], while not offering as much customization as the advanced [[OpenWrt]] firmware. Support for the Asus RT-N16, RT-N12, Linksys WRT-160Nv3 and Netgear WNR3500L/v2 has been added via a new [https://sourceforge.net/projects/tomatousb/ firmware modification] (based on Linux kernel 2.6).

==See also==
{{Portal|Free software}}

* [[List of wireless router firmware projects]]

== Reference ==
{{Reflist|2}}

==External links==
{{en:wikibooks|title=Tomato Firmware}}
{{Commons category|Tomato (firmware)}}
* [http://www.polarcloud.com/tomato Tomato Firmware] Official Homepage
* [http://www.linksysinfo.org/forums/showthread.php?t=57933 Tomato Modifications] Forum and listings of Tomato additions/distributions
* [http://en.wikibooks.org/wiki/Tomato_(firmware) Tomato Documentation] a Wikibook
* [http://lampiweb.com/tomato/about.htm Virtual Tomato GUI (ver. 1.07)]
* [http://lampiweb.com/virtual/Tomato_RAF/index.html Virtual Tomato RAF (victek mod)]
* [[Revision3]] - [[Systm]] - [http://revision3.com/systm/tomato/ Episode 71 on Tomato]

{{Routing software}}

{{DEFAULTSORT:Tomato (Firmware)}}
[[da:Tomato firmware]]
[[de:Tomato (Firmware)]]
[[pl:Tomato]]
[[zh:Tomato]]

[[Category:Software and Tools]]

Tiny6410

2026-08-23T10:01:25Z

Tommy：Consistency: syntax highlighting for code, File: prefix

'''Tiny6410''' was an internal ARM11 evaluation board project on the Samsung S3C6410. This page is the release log for its camera work.

''The repository referenced below (<code>192.168.50.188</code>) no longer exists. These notes are the surviving record of the project.''

==Project info==
Customer: internal<br>
Product: ARM11 evalution board<br>
Chip: Samsung S3C6410 / 533MHZ<br>

==SVN info==
[[File:Tiny6410_REPO_20110926_01.png]]<br>
'''camera'''
svn+ssh://192.168.50.188/svnroot/tiny6410/branches/camera

==Release info==
=== camera ===
==== tiny6410-camera-0.0.0.1 ====
svn+ssh://192.168.50.188/svnroot/NTV350OS/tags/
===== release date =====

''Not recorded. The repository this page refers to is gone, so this cannot be recovered.''

===== release note =====
* disable preview thread
* add 176x144 size for USB Camera C200
* combine V4l2 process into picture thread
* store image in temp file and re-open to get image data for Camera.apk
(please create tommy_test.jpg in root for r/w, and need to optimize this process)

[[Category:Boards and SoCs]]

Teensy 4.0

2026-08-23T10:01:24Z

Tommy：Consistency: syntax highlighting for code, File: prefix

'''Teensy 4.0''' is a 600 MHz Cortex-M7 board built on the NXP i.MX RT1062. These notes cover the pinout, memory map, and building for it with Teensyduino, PlatformIO and the NXP MCUXpresso SDK.

== Technical Specifications ==
* ARM Cortex-M7 at 600 MHz
* 1024K RAM (512K is tightly coupled)
* 2048K Flash (64K reserved for recovery & EEPROM emulation)
* 2 USB ports, both 480 MBit/sec
* 3 CAN Bus (1 with CAN FD)
* 2 I2S Digital Audio
* 1 S/PDIF Digital Audio
* 1 SDIO (4 bit) native SD
* 3 SPI, all with 16 word FIFO
* 3 I2C, all with 4 byte FIFO
* 7 Serial, all with 4 byte FIFO
* 32 general purpose DMA channels
* 31 PWM pins
* 40 digital pins, all interrrupt capable
* 14 analog pins, 2 ADCs on chip
* Cryptographic Acceleration
* Random Number Generator
* RTC for date/time
* Programmable FlexIO
* Pixel Processing Pipeline
* Peripheral cross triggering
* Power On/Off management
* FPU support
<pre>
Teensy 4.0's Cortex-M7 processor includes a floating point unit (FPU) which supports both 64 bit "double" and 32 bit "float".
With M4's FPU on Teensy 3.5 & 36, and also Atmel SAMD51 chips, only 32 bit float is hardware accelerated.
Any use of double, double functions like log(), sin(), cos() means slow software implemented math.
Teensy 4.0 executes all of these with FPU hardware.
</pre>

== PIN assignment ==
[[File:Card10a_rev1_web.png|500px|top side]]
[[File:Card10b_rev1_web.png|500px|back side]]

== Schematic ==
[[File:Schematic40.png|500px|Teensy 4.0 shematic]]
[[File:Schematic41.png|500px|Teensy 4.1 shematic]]

== Memory Map ==
* Teensy 4.0 has 1 Mbyte of RAM and 2 Mbyte of Flash memory. The RAM is divided into 2 physically separate banks.
[[File:Teensy4_memory.png|Teensy 4.0 Memory Layout]]

== Teensyduino IDE installation ==
* Download & Extract Arduino
* Install udev Rules
** The udev rule file gives non-root users permission to use the Teensy devices (serial, HID, etc). More Linux tips below.

sudo cp 49-teensy.rules /etc/udev/rules.d/

== PlatformIO ==
* Install VSCode(Visual Studio Code)
** Install PlatformIO from extensions

== MCUXpresso IDE ==

Teensy 4.0 carries an NXP i.MX RT1062, so NXP's own tools can be used to study
the chip even though Teensy itself is normally programmed through Teensyduino or
PlatformIO. MCUXpresso IDE is NXP's free Eclipse-based IDE for i.MX RT, LPC and
Kinetis parts; it bundles the GNU Arm toolchain and supports the SDK examples
built in the NXP SDK section below.

* Download from NXP (account required)
* Import an SDK as a zip, then '''Import SDK example''' to build the EVK projects
* Debug over the EVK's on-board CMSIS-DAP; Teensy 4.0 has no SWD header brought
out, so the IDE is useful for reference builds rather than flashing a Teensy

== MCUXpresso Config Tools ==

A standalone GUI for generating the start-up code for an i.MX RT part. It has
three sub-tools:

* '''Pins''' - assign peripheral signals to package pins, flags conflicts
* '''Clocks''' - configure the PLLs and clock tree, shows the resulting frequencies
* '''Peripherals''' - configure a peripheral and emit its init struct

Output is written back into the project as pin_mux.c, clock_config.c and
peripherals.c. It can run standalone or from inside MCUXpresso IDE.

== MCUXpresso SDK ==

The per-board driver and example package. Build one for a given board with the
SDK Builder at https://mcuxpresso.nxp.com and choose the toolchain when
generating it - the armgcc variant is what the NXP SDK section below builds.

Contents:
* '''devices/''' - CMSIS headers, start-up code and peripheral drivers (fsl_*.c)
* '''boards/''' - board-specific examples, one directory per example
* '''middleware/''' - optional stacks such as USB, FatFs and lwIP

For Teensy 4.0 the relevant board is EVK-MIMXRT1060, whose MIMXRT1062 is the same
part as the one on the Teensy.

== NXP SDK ==
<syntaxhighlight lang="bash">
export ARMGCC_DIR=$TOOLCHAIN_PATH
cd SDK_2.7.0_EVK-MIMXRT1060/boards/evkmimxrt1060/driver_examples/gpio/led_output/armgcc
chmod 777 build_all.sh
./build_all.sh
arm-none-eabi-objcopy -O ihex flexspi_nor_release/igpio_led_output.elf flexspi_nor_release/igpio_led_output.hex
teensy_loader_cli -v -w --mcu=imxrt1062 flexspi_nor_release/igpio_led_output.hex
</syntaxhighlight>

* For led_output example, need to modify gpio mapping in board.h (refer to schematic)
<pre>
/*! @brief The USER_LED used for board */
#define LOGIC_LED_ON (0U)
#define LOGIC_LED_OFF (1U)
#ifndef BOARD_USER_LED_GPIO
#define BOARD_USER_LED_GPIO GPIO2 <----- modify
#endif
#ifndef BOARD_USER_LED_GPIO_PIN
#define BOARD_USER_LED_GPIO_PIN (3U) <----- modify
#endif
</pre>

== Upload binary standalone ==
* teensy_loader_cli -mmcu=imxrt1062 -w evkmimxrt1060_freertos_hello_teensy.hex -v

== SPI Timing ==
* CS_OFF around 40 ns
[[File:Teensy_4_spi_cs.jpg|400px|SPI CS_OFF width]]

* SPI CLK in 16M
[[File:Teensy_4_spi_16M.jpg|400px|SPI CLK in 16M]]

* Sampling rate evaluation
** CS_ON+CS_OFF around 1.46 us
** For 32 Ch in 16M SPI_CLK, the sampling rate for each channel would be:
*** (1000000/1.46*32)/1000=21.4KS

== SDIO 4 bit ==
[[File:Teensy_4_sdio_4_bit.JPG|500px|SDIO4 bit mode]]
* Format SD before running
* Change pin define in code
** SD.begin(BUILTIN_SDCARD)
<syntaxhighlight lang="c">
/*
SD card datalogger

This example shows how to log data from three analog sensors
to an SD card using the SD library.

The circuit:
* analog sensors on analog ins 0, 1, and 2
* SD card attached to SPI bus as follows:
** MOSI - pin 11, pin 7 on Teensy with audio board
** MISO - pin 12
** CLK - pin 13, pin 14 on Teensy with audio board
** CS - pin 4, pin 10 on Teensy with audio board

created 24 Nov 2010
modified 9 Apr 2012
by Tom Igoe

This example code is in the public domain.

*/

#include <SD.h>
#include <SPI.h>

// On the Ethernet Shield, CS is pin 4. Note that even if it's not
// used as the CS pin, the hardware CS pin (10 on most Arduino boards,
// 53 on the Mega) must be left as an output or the SD library
// functions will not work.

// change this to match your SD shield or module;
// Arduino Ethernet shield: pin 4
// Adafruit SD shields and modules: pin 10
// Sparkfun SD shield: pin 8
// Teensy audio board: pin 10
// Teensy 3.5 & 3.6 on-board: BUILTIN_SDCARD
// Wiz820+SD board: pin 4
// Teensy 2.0: pin 0
// Teensy++ 2.0: pin 20
//const int chipSelect = 36;

void setup()
{
//UNCOMMENT THESE TWO LINES FOR TEENSY AUDIO BOARD:
//SPI.setMOSI(37); // Audio shield has MOSI on pin 7
//SPI.setSCK(36); // Audio shield has SCK on pin 14

// Open serial communications and wait for port to open:
Serial.begin(9600);
while (!Serial) {
; // wait for serial port to connect. Needed for Leonardo only
}

Serial.print("Initializing SD card...");

// see if the card is present and can be initialized:
if (!SD.begin(BUILTIN_SDCARD)) {
Serial.println("Card failed, or not present");
// don't do anything more:
return;
}
Serial.println("card initialized.");
}

void loop()
{
// make a string for assembling the data to log:
String dataString = "";

// read three sensors and append to the string:
for (int analogPin = 0; analogPin < 3; analogPin++) {
int sensor = analogRead(analogPin);
dataString += String(sensor);
if (analogPin < 2) {
dataString += ",";
}
}

// open the file. note that only one file can be open at a time,
// so you have to close this one before opening another.
File dataFile = SD.open("datalog.txt", FILE_WRITE);

// if the file is available, write to it:
if (dataFile) {
dataFile.println(dataString);
dataFile.close();
// print to the serial port too:
Serial.println(dataString);
}
// if the file isn't open, pop up an error:
else {
Serial.println("error opening datalog.txt");
}
}
</syntaxhighlight>

== Related projects ==
* [[Application - ADS1256]]

[[Category:Boards and SoCs]]

Software version

2026-08-23T10:01:24Z

Tommy：Consistency: syntax highlighting for code, File: prefix

'''Software versioning''' is the process of assigning identifiers to distinct releases of a piece of software. This article surveys the schemes in use.

==Schemes==
A variety of version numbering schemes have been created to keep track of different versions of a piece of software. The ubiquity (the ability to be everywhere at the same time) of computers has also led to these schemes being used in contexts outside computing.

===Sequence-based identifiers===
[[File:VersionNumbers.svg|right|Version number sequence|1000x500px]]
In sequence-based software versioning schemes, each [[software release]] is assigned a unique identifier that consists of one or more sequences of numbers or letters. This is the extent of the commonality, however: schemes vary widely in areas such as the quantity of sequences, the attribution of meaning to individual sequences, and the means of incrementing the sequences.

====Change significance====
In some schemes, sequence-based identifiers are used to convey the significance of changes between releases: changes are classified by significance level, and the decision of which sequence to change between releases is based on the significance of the changes from the previous release, whereby the first sequence is changed for the most significant changes, and changes to sequences after the first represent changes of decreasing significance.

For instance, in a scheme that uses a four-sequence identifier, the first sequence may be incremented only when the code is completely rewritten, while a change to the user interface or the documentation may only warrant a change to the fourth sequence.

This practice permits users (or potential adopters) to evaluate how much real-world testing a given software release has undergone. If changes are made between, say, 1.3rc4 and the production release of 1.3, then that release, which asserts that it has had a production-grade level of testing in the real world, in fact contains changes which have not necessarily been tested in the real world ''at all''.{{Clarify|January 2010|date=January 2010}} This approach commonly permits the third level of numbering ("change"), but does not apply this level of rigor to changes in that number: 1.3.1, 1.3.2, 1.3.3, 1.3.4... 1.4b1, etc.{{Clarify|January 2010|date=January 2010}}

In principle, in subsequent releases, the ''major'' number is increased when there are significant jumps in functionality, the ''minor'' number is incremented when only minor features or significant fixes have been added, and the ''revision'' number is incremented when minor bugs are fixed. A typical product might use the numbers 0.9 (for beta software), 0.9.1, 0.9.2, 0.9.3, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.1, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.2, etc. Developers have at times jumped (for example) from version 5.0 to 5.5 to indicate that significant features have been added, but not enough to warrant incrementing the major version number, though this is [[Software_versioning#Separating_sequences|improper]].{{Clarify|January 2010|date=January 2010}}

A different approach is to use the ''major'' and ''minor'' numbers, along with an alphanumeric string denoting the release type, i.e. "alpha", "beta" or "release candidate". A release train using this approach might look like 0.5, 0.6, 0.7, 0.8, 0.9 == 1.0b1, 1.0b2 (with some fixes), 1.0b3 (with more fixes) == 1.0rc1 (which, if it is stable ''enough'') == 1.0. If 1.0rc1 turns out to have bugs which must be fixed, it turns into 1.0rc2, and so on. The important characteristic of this approach is that the first version of a given level (beta, RC, production) ''must be identical'' to the last version of the release below it: you cannot make any changes at all from the last beta to the first RC, or from the last RC to production. If you do, you must roll out another release at that lower level.

However, since version numbers are human-generated, not computer-generated, there is nothing that prevents arbitrary changes that violate such guidelines: for example, the first sequence could be incremented between versions that differ by not even a single line of code, to give the (false) impression that very significant changes were made.

Other schemes impart meaning on individual sequences:
:''<nowiki>major.minor[.build[.revision]]</nowiki>''
or
:''<nowiki>major.minor[.maintenance[.build]]</nowiki>''

Again, in these examples, the definition of what constitutes a "major" as opposed to a "minor" change is entirely arbitrary and up to the author, as is what defines a "build", or how a "revision" differs from a "minor" change.

In most proprietary software, the first released version of a software product has version 1.

====Designating development stage====
Some schemes use a zero in the first sequence to designate [[Software release life cycle#Alpha|alpha]] or [[Software release life cycle#Beta|beta]] status for releases that are not stable enough for general or practical deployment and are intended for testing or internal use only.

It can be used in the third position:
* 0 for alpha (status)
* 1 for beta (status)
* 2 for release candidate
* 3 for (public) release

For instance:
* 1.2.0.1 instead of 1.2-a
* 1.2.1.2 instead of 1.2-b2 (beta with some bug fixes)
* 1.2.2.3 instead of 1.2-rc (release candidate)
* 1.2.3.0 instead of 1.2-r (commercial distribution)
* 1.2.3.5 instead of 1.2-r5 (commercial distribution with many bug fixes)

====Separating sequences====
When printed, the sequences may be separated with characters. The choice of characters and their usage varies by scheme. The following list shows hypothetical examples of separation schemes for the same release (the thirteenth third-level revision to the fourth second-level revision to the second first-level revision):

* A scheme may use the same character between all sequences: 2.4.13, 2/4/13, 2-4-13
* A scheme choice of which sequences to separate may be inconsistent, separating some sequences but not others: 2.413
* A scheme's choice of characters may be inconsistent within the same identifier: 2.4_13

When a period is used to separate sequences, it does ''not'' represent a decimal point, and the sequences do ''not'' have positional significance. An identifier of ''2.5'', for instance, is not "two and a half" or "half way to version three", it is the ''fifth second-level revision of the second first-level revision''.

====Number of sequences====

There is sometimes a fourth, unpublished number which denotes the software build (as used by [[Microsoft]]). [[Adobe Flash]] notably publicly indicates a 4-part version, as in 10.1.53.64. Some companies also include the build date. Version numbers may also include letters and other characters, such as [[Lotus 1-2-3]] Release 1a.

====Incrementing sequences====

There are two schools of thought regarding how numeric version numbers are incremented: Most [[free software]] packages treat numbers as a continuous stream, therefore a free software or open source product may have version numbers 1.7.0, 1.8.0, 1.8.1, 1.9.0, 1.10.0, 1.11.0, 1.11.1, 1.11.2, etc. An example of such a software package is [[MediaWiki]]. However, many programs treat version numbers in another way, generally as decimal numbers, and may have version numbers such as 1.7, 1.8, 1.81, 1.82, 1.9, etc. In software packages using this way of numbering 1.81 is the next minor version after 1.8. Maintenance releases (i.e. bug fixes only) would generally be denoted as 1.81a, 1.81b, etc.

The standard [[GNU]] version numbering scheme is major.minor.revision, but [[emacs]] is notably using another scheme where the major number ("1") was dropped and a "user site" revision was added which is always zero in original emacs packages but increased by distributors.<ref name="advogato"/> Similarly, [[Debian]] package numbers are prefixed with an optional "epoch", which is used to allow the versioning scheme to be changed.<ref>Debian Policy Manual, [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version 5.6.12 Version]</ref>

====Using negative numbers====
There exist some projects that use negative version numbers. One example is the [[smalleiffel]] compiler which started from -1.0 and counted upwards to 0.0.<ref name="advogato">{{Cite web|url=http://www.advogato.org/article/40.html|title=Advogato: Version numbering madness|accessdate=2009-04-11|date=2000-02-28}}</ref>

====Degree of compatibility====
Some projects use the major version number to indicate incompatible releases. Two examples are Apache APR<ref name="apr">{{Cite web|url=http://apr.apache.org/versioning.html|title=Versioning Numbering Concepts - The Apache Portable Runtime Project|accessdate=2009-04-11}}</ref> and the FarCry CMS.<ref name="farcry">{{Cite web|url=http://blog.daemon.com.au/archives/000276.html|title=Daemonite: The science of version numbering|date=2004-09-14|accessdate=2009-04-11}}</ref>

===Date===
The [[Wine (software)|Wine]] project used a date versioning scheme, which uses the year followed by the month followed by the day of the release; for example, "Wine 20040505". Wine is now on a "standard" release track; the most current stable version (as of [[2010]]) is 1.2. [[Ubuntu Linux]] uses a similar versioning scheme—Ubuntu 10.04, for example, was released April 2010.

When using dates in versioning, for instance, file names, it is common to use the ISO scheme<ref name="ISO Date">{{Cite web|url=http://www.cl.cam.ac.uk/~mgk25/iso-time.html|title=International standard date and time notation|author=Markus Kuhn|accessdate=2009-04-11|date=2004-12-19|publisher=[[University of Cambridge]]}}</ref>: YYYY-MM-DD, as this is easily string sorted to increasing/decreasing order. The hyphens are sometimes omitted.

[[Microsoft Office]] build numbers are actually an encoded date.<ref name="ms">{{Cite web|url=http://www.codinghorror.com/blog/archives/000793.html|title=Coding Horror: What's In a Version Number, Anyway?|date=2007-02-15|accessdate=2009-04-11|author=Jeff Atwood}}</ref>

===Year of release===
Other examples, identifying versions by year ([[Adobe Illustrator]] 88, [[WordPerfect Office]] 2003). Although when a date is used to denote version it is generally for marketing purposes, and an actual version number exists. For example, [[Microsoft Windows 2000 Server]] is internally versioned as Windows NT 5.0 ("NT" being a reference to the original product name).

===Alphanumeric codes=== 
Examples:
* [[Macromedia Flash]] MX
* [[Adobe Photoshop]] CS2

===TeX===
[[TeX]] has an [[idiosyncratic]] version numbering system. Since version 3, updates have been indicated by adding an extra digit at the end, so that the version number [[asymptote|asymptotically]] approaches [[pi|π]]; this is a form of [[Unary numeral system|unary numbering]] – the version number is the number of digits. The current version is 3.1415926. This is a reflection of the fact that TeX is now very stable, and only minor updates are anticipated. TeX developer [[Donald Knuth]] has stated that the "absolutely final change (to be made after my death)" will be to change the version number to π, at which point all remaining bugs will become permanent features.<ref>Donald E. Knuth. [http://www.ntg.nl/maps/05/34.pdf ''The future of TeX and METAFONT''], NTG journal MAPS (1990), 489. Reprinted as chapter 30 of ''Digital Typography'', p. 571.</ref>

In a similar way, the version number of [[METAFONT]] asymptotically approaches [[E (mathematical constant)|e]].

===Apple===
Apple has a formalised version number structure based around the NumVersion struct, which specifies a one- or two-digit major version, a one-digit minor version, a one-digit "bug" (i.e. revision) version, a stage indicator (drawn from the set development/prealpha, alpha, beta and final/release), and a one-byte (i.e. having values in the range 0–255) pre-release version, which is only used at stages prior to final. In writing these version numbers as strings, the convention is to omit any parts after the minor version whose value are zero (with "final" being considered the zero stage), thus writing 1.0.2b12, 1.0.2 (rather than 1.0.2f0), and 1.1 (rather than 1.1.0f0).

===Other schemes===
Some software producers use different schemes to denote releases of their software. For example, the [[Microsoft Windows]] operating system was first labelled with standard numerical version numbers ([[Windows 1.0]] through [[Windows 3.1x|Windows 3.11]]). Later, Microsoft started using separate version names for marketing purposes, first using years ([[Windows 95]] (4.0), [[Windows 98]] (4.10), [[Windows 2000]] (5.0)), then using alphanumeric codes ([[Windows Me]] (4.90), [[Windows XP]] (5.1)), then using brand names ([[Windows Vista]] (6.0)). With the release of [[Windows 7]] it appears that Microsoft has returned to using numerical version numbers, although the official version number for Windows 7 is 6.1<ref>Enter the "ver" command in Windows 7 command prompt</ref>.

The [[Debian]] project uses a major/minor versioning scheme for releases of its operating system, but uses code names from the movie ''[[Toy Story]]'' during development to refer to stable, unstable and testing releases.

[[Category:Software Engineering]]

Software release life cycle

2026-08-23T10:01:23Z

Tommy：Consistency: syntax highlighting for code, File: prefix

{{Redirect|Development stage|other meanings|Stage of development (disambiguation)}}
{{Merge|software development process|date=July 2010}}
{{moreref|date=August 2010}}
{{Infobox
|above = Software Development and Release Stages
|image = [[File:Software dev2.png]]
}}

A '''software release''' is the distribution of [[computer software|software]] code, documentation, and support materials. The '''software release life cycle''' is composed of discrete phases that describe the software's maturity as it advances from planning and development to release and support phases.

== Development ==
=== Pre-Alpha ===
Pre-alpha refers to all activities performed during the software project prior to [[software testing|testing]]. These activities can include [[requirements analysis]], [[software design]], [[software development]] and [[unit testing]].

In typical [[open source]] development, there are several types of pre-alpha versions. '''Milestone''' versions include specific sets of functions and are released as soon as the functionality is complete.

=== Alpha === 
The [[alpha (letter)|alpha]] phase of the release life cycle is the first phase to begin [[Software testing]]. In this phase, developers generally test the software using [[white box testing|white box techniques]]. Additional validation is then performed using [[black box testing|black box]] or gray box techniques, by another [[Software testing|testing team]]. Moving to black box testing inside the organization is known as ''alpha release''.

Alpha software can be unstable and could cause crashes or data loss.

The alpha phase usually ends with a [[Freeze (software engineering)|feature freeze]], indicating that no more features will be added to the software. At this time, the software is said to be [[feature complete]].

=== Beta === 
"Beta" is the software development phase following alpha, named after the Greek letter [[Beta (letter)|beta]]. It generally begins when the software is [[feature complete]]. The focus of beta testing is reducing impacts to users, often incorporating [[usability testing]]. The process of delivering a beta version to the users is called '''beta release'''.

The users of a beta version are called ''beta testers''. They are usually customers or prospective customers of the organization that develops the software, willing to test the software for free or for a reduced price.

Beta version software is likely to be useful for internal demonstrations and previews to select customers. Some developers refer to this stage as a '''preview''', a '''prototype''', a '''technical preview''' ('''TP''') or as an '''early access'''.

==== Open and closed beta ====

Developers release either a '''closed beta''' or an '''open beta'''; closed beta versions are released to a select group of individuals for a user test, while open betas are to a larger community group, usually the general public. The testers report any bugs that they found and sometimes minor features they would like to see in the final version.

Examples of a major public beta test were [[Microsoft]]'s release of '''community technology preview'''s ('''CTP'''s) for [[Windows Vista]] in January 2005. In September 2000, a ''boxed version'' of Apple Computer's [[Mac OS X Public Beta]] operating system was released.

=== Release candidate ===
The term '''release candidate''' ('''RC''') refers to a version with potential to be a final product, ready to release unless fatal [[computer bug|bugs]] emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bug.

During the 1990s, [[Apple Inc.]] used the term "[[golden master]]" for its release candidates, and the final golden master was used as the general availability release. Other Greek letters, such as '''gamma''' and '''delta''', are sometimes used to indicate versions that are substantially complete, but still undergoing testing, with '''omega''' or '''zenith''' used to indicate final testing versions that are believed to be relatively bug-free, ready for production.

A release is called '''code complete''' when the development team agrees that no entirely new source code will be added to this release. There may still be source code changes to fix defects. There may still be changes to documentation and data files, and to the code for test cases or utilities. New code may be added in a future release.

=== Origin of alpha and beta terminology ===
{{Unreferenced section|date=August 2007}}
The term '''beta test''' comes from an [[IBM Product Test|IBM convention]], dating back to punched card tabulating and sorting machines. Hardware first went through an '''alpha test''' for preliminary functionality and small scale manufacturing feasibility. Then came a '''beta test''', to verify that the hardware correctly performed the intended functions and could be manufactured at scale. Ultimately, a '''gamma test''' was performed to verify safety.

When IBM began testing software, it used the same terminology as it had for hardware. As other companies began developing their own software, the terminology stuck—and now is part of the common vocabulary.

== Release ==
=== RTM {{Anchors|RTM|Release to manufacturing|Release to marketing|RTM_or_RTW}} ===
The term "'''release to manufacturing'''" or "'''release to marketing'''" (both abbreviated RTM)—also known as "going gold"—is a term used to indicate that the software has reached a point that it is ready to or has been delivered or provided to the customer. It is typically used in certain retail mass-production software contexts - as opposed to a specialized software production or project in a commercial or government production and distribution - where the software is sold as part a bundle in a related computer hardware sale and typically where the software and related hardware is ultimately to be available and sold on mass/public basis at retail stores to indicate that the software has met a defined quality level and is ready for mass retail distribution. RTM could also mean in other contexts that the software has been delivered or released to a client or customer for installation or distribution to the related hardware end user computers or machines. The term does ''not'' define the delivery mechanism or volume; it only states that the quality is sufficient for mass distribution. The deliverable from the engineering organization is frequently in the form of a '''gold''' master CD used for duplication or to produce the image for the web.

RTM happens prior to general availability ([[#GA|GA]]) when the product is released to the public.

=== General availability {{Anchors|GA|General availability}} ===
'''General availability '''or''' General Acceptance''' ('''GA''') is the point where all necessary commercialization activities have been completed and the software has been made available to the general market either via the web or physical media.

Commercialization activities could include but are not limited to the availability of media world wide via dispersed distribution centers, marketing collateral is completed and available in as many languages as deemed necessary for the target market, the finishing of security and compliance tests, etc. The time between RTM and GA can be from a week to months in some cases before a generally available release can be declared because of the time needed to complete all commercialization activities required by GA.

Another term with a meaning almost identical to GA is '''FCS''', for '''First Customer Shipment'''. Some companies (such as Sun Microsystems and Cisco) use FCS to describe a software version that has been shipped for revenue.

It is also at this stage that the software is considered to have "gone live". The '''production''', '''live''' version is the final version of a particular product. A live release is considered to be very stable and relatively bug-free with a quality suitable for wide distribution and use by end users. In commercial software releases, this version may also be [[Code signing|signed]] (used to allow end-users to verify that code has not been modified since the release). The expression that a software product "has gone live" means that the code has been completed and is ready for distribution. Other terms for the live version include: live master, live release, or live build.

In some areas of software development it is at this stage that the release is referred to as a '''gold''' release; this seems to be confined mainly to game software.

== Support ==
=== Service release ===
{{Expand section|date=August 2009}}
During its supported lifetime, software is sometimes subjected to service releases, or [[service pack]]s. As a well used example, Microsoft's [[Windows XP]] has currently had 3 major [[Windows XP#Service packs|Service Packs]].

Such service releases contain a collection of updates, fixes and/or enhancements, delivered in the form of a single installable package. They may also contain entirely new features.

Certain software is released with the expectation of regular support. Classes of software that generally involve protracted support as the norm include [[Antivirus software|Anti-virus suites]] and [[Massively multiplayer online game|Massively Multiplayer Online Games]].

=== End of life {{Anchors|EOL|End of life}} ===
{{See also|End-of-life (product)}}
When software is no longer sold or supported, the product is said to have reached end-of-life.

== Impact of the World-Wide Web ==

As the Internet has allowed for rapid and inexpensive distribution of software, companies have begun to take a more loose approach to use of the word "beta".<ref>[http://www.tidbits.com/tb-issues/TidBITS-328.html#lnk5 "Waiting with Beta'd Breath"] ''[[TidBITS]]'' #328 (May 13, 1996)</ref> [[Netscape Communications]] was infamous for releasing alpha level versions of its [[Netscape (web browser)|Netscape web browser]] to the public and calling them "beta" releases.{{Citation needed|date=April 2010}} In February 2005, [[ZDNet]] published an article about the recent phenomenon of a beta version often staying for years and being used as if it were in production-level. It noted that [[Gmail]] and [[Google News]], for example, had been in beta for a long period of time and were not expected to drop the beta status despite the fact that they were widely used; however, Google News did leave beta in January 2006, followed by [[Google Apps]], including [[Gmail]], in July 2009.<ref>[http://googleblog.blogspot.com/2009/07/google-apps-is-out-of-beta-yes-really.html "Google Apps is out of beta (yes, really)"] "The Official Google Blog" (July 7, 2009)</ref> This technique may also allow a developer to delay offering full support and/or responsibility for remaining issues. In the context of [[Web 2.0]], people even talk of [[perpetual beta]]s to signify that some software is meant to stay in beta state. Also, "beta" is sometimes used to indicate something more like a [[Software release life cycle#Release candidate|release candidate]], or as a form of time limited demo, or marketing technique.<ref>[http://www.gamesradar.com/f/the-inconvenient-truths-behind-betas/a-2010051712402686048 The inconvenient truths behind betas]</ref>

Some users disparagingly refer to release candidates and even final "point oh" releases as "gamma test" software, suggesting that the developer has chosen to use its customers to test software that is not truly ready for general release. Beta testers, if privately selected, will often be credited for using the release candidate as though it were a finished product.

=== Web release ===
A '''web release''' is a means of software delivery that utilizes the Internet for distribution. No physical media are produced in this type of release mechanism by the manufacturer. This is sometimes also referred to as ''Release To Web'' (RTW).


== See also ==
*[[Paper launch]]
*[[Release engineering]]
*[[Release management]]
*[[Rolling release]]
*[[Software maintenance]]
*[[Software testing]]
*[[Software versioning]]
*[[Software deployment]]
*[[Vaporware]]

== Reference ==

{{Reflist}}

== External links ==
*[http://developer.apple.com/technotes/tn/tn1132.html Apple, Inc. Version Territory]
*[http://www.tldp.org/HOWTO/Software-Proj-Mgmt-HOWTO/users.html#ALPHABETA Free Software Project Management HOWTO].
*[https://pide.dev.java.net/glossary-std.html Java Standard Terms].
*[http://www.se-cure.ch/Publications.html Software Release Decisions]
*[http://www.methodsandtools.com/archive/archive.php?id=55 A Methodology to Support Software Release Decisions]
*[http://www.editorial.co.in/software/software-testing-life-cycle.php Software Testing Life Cycle].
*[http://www.computeruser.com/resources/dictionary/definition.html?lookup=792 computeruser.com definition]
*[http://www.smartcomputing.com/editorial/dictionary/detail.asp?guid=&searchtype=&DicID=8430&RefType=Dictionary smartcomputing.com definition]
*[http://www.techweb.com/encyclopedia/defineterm.jhtml?term=betaware techweb.com definition]
*[http://semver.org/ Semantic versioning]

[[ar:دورة حياة إصدار البرمجيات]]
[[de:Entwicklungsstadium (Software)]]
[[et:Tarkvara väljalaske elutsükkel]]
[[es:Fases del desarrollo de software]]
[[fa:چرخهٔ ارائهٔ نرم‌افزار]]
[[it:Release (informatica)]]
[[pl:Cykl życia programu]]
[[pt:Liberação de software]]
[[ru:Стадии разработки программного обеспечения]]
[[sl:programska izdaja]]
[[sv:Programvaruutveckling]]
[[zh:軟件出版週期]]

[[Category:Software Engineering]]

ST, STM32F4 Discovery

2026-08-23T10:01:23Z

Tommy：Consistency: syntax highlighting for code, File: prefix

The '''STM32F4 Discovery''' is an ST Cortex-M4 board. These notes cover the GNU/ARM toolchain, building and flashing with ST-Link, and debugging with GDB.

[[File:IMAG4572 BURST001.jpg|thumb|200px|Dot matrix + servo + touch sensor]]
== Download the GNU/ARM toolchain ==
* tar -xvjf gcc-arm-none-eabi-4_8-2014q2-20131204-linux.tar.bz2
* export PATH=$PATH:~/gcc-arm-none-eabi-4_8-2014q2/bin
== Download and Build STLINK ==
* sudo apt-get install autoconf pkg-config libusb-1.0 git
* git clone https://github.com/texane/stlink.git
<syntaxhighlight lang="bash">
cd ~/stlink
./autogen.sh
./configure
make
</syntaxhighlight>
== Download STM32 Libraries and Blinky Example ==
* git clone https://github.com/rowol/stm32_discovery_arm_gcc
== Compile Your Source Code ==
* Edit Makefile
** STLINK=/home/rowol/stlink #Example, change to your location
** STM_COMMON=/home/rowol/stm32_discovery_arm_gcc/STM32F4-DISCOVERY_FW_V1.1.0
** make it
== Program ARM's Flash and Run Code ==
* make burn
or
* st-flash write STM32F4-Discovery.bin 0x08000000

== Using external ST-Link ==
* Remove CN3 jumper
<pre>
ST-Link STM32F4
VCC 3V
SWIO PA13
SWCLK PA14
VDD VDD ( depends on product, could range from 1.8v - 5v )
GND GND
</pre>

== GDB ==
<pre>
In the directory with your source code, I've also add a .gdbinit file which contains:

define reload
kill
monitor jtag_reset
load
end

target extended localhost:4242
load

This will execute whenever you start GDB in the source directory

To start up:

~/stlink/st-util #Start GDB server
arm-none-eabi-gdb main.elf #In a second terminal window, start GDB

continue #Starts code running, or use other GDB commands to
# set breakpoints, etc first...

</pre>

== Related projects ==
* [[Application - MPR121, capacitive touch sensor controller]]
* [[Application - MAX7219, Serially Interfaced, 8-Digit LED Display Drivers (interact with MPR121)]]
* [[Application - MAX7219, Serially Interfaced, 8-Digit LED Display Drivers (scrolling text)]]
* [[application - CS43L22, built-in DAC(audio playback)]]
* [[Application - MG90S, Metal Gear Servo]]
* [[Application - Joystick]]
* [[Application - nRF52, (BLE - UART - STM32F4)]]
* [[Application - MeArm, mini robotic arm]]

== Reference ==
* [https://launchpad.net/gcc-arm-embedded/+download ARM toolchain]
* [http://www.wolinlabs.com/blog/linux.stm32.discovery.gcc.html STM32 Discovery Development On Linux]

* [http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419 STM32F4 Discovery Kit Resource Page]
* [http://www.arm.com/products/processors/cortex-m/cortex-microcontroller-software-interface-standard.php CMSIS - Cortex Microcontroller Software Interface Standard]
* [http://rusefi.com/wiki/index.php?title=Hardware:stm32f4discovery_repair Hardware:stm32f4discovery repair]

[[Category:Boards and SoCs]]

RTD1073

2026-08-23T10:01:23Z

Tommy：Consistency: syntax highlighting for code, File: prefix

'''RTD1073''' was a RealTek-based IP media player built for NetGear. This page is the release log for its diagnostic and RadioTime firmware, 2010-2011.

''The repository referenced below (<code>192.168.50.188</code>) no longer exists. These notes are the surviving record of the project.''

==Project info==
Customer: NetGear<br>
Product: IP media player<br>
Chip: RealTek RTD1073<br>

==SVN info==
[[File:NTV350_REPO_20101123.jpg]]<br>
'''Diag'''
svn+ssh://192.168.50.188/svnroot/NTV350SDK/branches/diag
'''UI'''
svn+ssh://192.168.50.188/svnroot/NTV350SDK/branches/UI
'''RadioTime'''
svn+ssh://192.168.50.188/svnroot/NTV350SDK/branches/radioTime
<br>
'''Diag kernel'''
svn+ssh://192.168.50.188/svnroot/NTV350OS/branches/diagOS
'''RadioTime kernel'''
svn+ssh://192.168.50.188/svnroot/NTV350OS/branches/radioTimeOS

==Release info==
=== Diag ===
==== diag-1.0.0.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/diag-1.0.0.0
===== release date =====
2010/08/31
===== release note =====
First release with alpha version<br>
Supported command:
* play
* speed
* stop
* reset
* setDigiOutputMode
* setTVSystem
* usbDetect
* ver
* help
* exit

==== NTV350_Diag_1.0.1.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.0
===== release date =====
2010/09/01
===== release note =====
* Fix: Dummy message from USB scan
* Fix: exit command - kill self before leaving
* Add: "Unihan" sign before come in diag
* Add: Display "Firmware version" in ver command
==== NTV350_Diag_1.0.1.1 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.1
===== release date =====
2010/09/02

===== release note =====
* Add: add "getAppCRC" command for calculate and get crc of DvdPlayer
* Fix : Re-open the IR thread
* Add : Merge the card detecting solution
* Fix : Printf("Firmware Version: v") is printed with the version is found from DvdPlay binary file.
* Fix : memory card insert/remove message.
==== NTV350_Diag_1.0.1.2 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.2
===== release date =====
2010/09/03

===== release note =====
* Fix : trim the version string with control character in ASCII
==== NTV350_Diag_1.0.1.3 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.3
===== release date =====
2010/09/07
===== release note =====
* Fix : system revision
==== NTV350_Diag_1.0.1.4 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.4
===== release date =====
2010/09/09

===== release note =====
* Add getKernelCRC command:calculate CRC of kernel, need size as input parameter.
* Add getSquashCRC command:calculate CRC of last block of SquashFS, need size as input parameter.
==== NTV350_Diag_1.0.2.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.2.0
===== release date =====
2010/09/27
===== release note =====
* Enhance Diag launch time from ~11s to ~6s
Add: Remove sleep(5) in main.cpp to increase start up speed.

==== NTV350_Diag_1.0.3.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.0
===== release date =====
2010/10/15
===== release note =====
*Add : Auto play default video(demp.mpg) from USB
*Add : Remove WatchDog before running diag
*Fix : Stopall utility not kill DvdPlayer all the time
==== NTV350_Diag_1.0.3.1 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.1
===== release date =====
2010/10/20
===== release note =====

''Not recorded. The repository this page refers to is gone, so this cannot be recovered.''

==== NTV350_Diag_1.0.3.2 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.2
===== release date =====
2010/10/22
===== release note =====
* Disable DHCP when DvdPlayer launched
* Add : play Demo1/Demo2
==== NTV350_Diag_1.0.3.3 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.3
===== release date =====
2010/10/27
===== release note =====
-Fix: adjust searching Firmware and System version offset.
==== NTV350_Diag_1.0.3.4 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.4
===== release date =====
2010/11/23
===== release note =====
Add two command lines.
A. “play” command line:
1. play Demo1 (Demo1 = HD-underwater.mpg)
2. play Demo2 (Demo2 = Unihan_Jerry_CBARS100_1K_Tone.ts)
3. play file_location (example: play /mnt/usbmounts/sdb1/movie1.mpg)
4. play link_url (example: play http://192.168.50.194:8080/music/qianli.mp3)
B. “setVolumeRate” command line:
setVolumeRate rate_value (where rate value = 0 ~ 30)
Example: setVolumeRate 30 (set volume rate to MAX)

=== RadioTime ===
==== NTV350_RadioTime_1.0.0.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.0
===== release date =====
2010/09/06
===== release note =====
* First release UI prototype to NetGear
* Including search function
* Still can not play stream from RadioTime due to DTS license
==== NTV350_RadioTime_1.0.0.1 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.1
===== release date =====
2010/09/07
===== release note =====
* Remove network WORKGROUP layer
* Downsize the 20MB to 2MB for indexing
* Win7 PlayTo - Add backward & forward functions
==== NTV350_RadioTime_1.0.0.2 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.2
===== release date =====
2010/09/20

===== release note =====
* Add display status of xml,
* Add main menu for home and search submenu,
* Add new UI for NETGEAR,
* Add function to get radio channel bitrate and formats,
* Add category for each linking note.
* Add Netgear request UI(page1,page2,page3,search).

==== NTV350_RadioTime_1.0.0.3 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.3
===== release date =====
2010/09/27
===== release note =====
* Add WN111v2 driver and insert module automatically
* Add network connecting detection.
* Add first and last rolling detection.
* Modify UI as Netgear requested.

==== NTV350_RadioTime_1.0.0.4 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.4
===== release date =====
2010/10/07
===== release note =====
* Add rolling text in page2 and search.
* Change page3 to vertical scrolling.
==== NTV350_RadioTime_1.0.0.5 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.5
===== release date =====
2010/11/03
===== release note =====
* Add check font length of scrolling string,
* Start scrolling after 1 second,
* Parsing M3U list for continue playing stream in list,
* Shrink logo screen and button,
* Add return playing error scheme.

[[Category:Boards and SoCs]]

Qualcomm, HDK8250(SM8250)

2026-08-23T10:01:22Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Building Android for the Qualcomm '''HDK8250''' (SM8250) - the HLOS images, the non-HLOS images, and programming them to the board.

== Build tool ==
* Snapdragon LLVM Arm toolchain

* GCC Linaro GNU 4.9 – 2014.07 

* Install toolchain - Hexagon 8.3.04 and Hexagon 8.3.06
** export HEXAGON_ROOT=$PATH_OF_INTALLL_DIR

* Make bash in the default shell(symlink /bin/sh → dash to /bin/sh → bash)
<syntaxhighlight lang="bash">
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh
</syntaxhighlight>
* install repo (dependency with python and git) ... prefer to use python 2.7
<syntaxhighlight lang="bash">
curl https://storage.googleapis.com/git-repo-downloads/repo-1 > ~/bin/repo
chmod a+x ~/bin/repo
rm -rf ~/.repo* ~/.gnupg
gpg --import

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.11 (GNU/Linux)

mQENBFHRvc8BCADFg45Xx/y6QDC+T7Y/gGc7vx0ww7qfOwIKlAZ9xG3qKunMxo+S
hPCnzEl3cq+6I1Ww/ndop/HB3N3toPXRCoN8Vs4/Hc7by+SnaLFnacrm+tV5/OgT
V37Lzt8lhay1Kl+YfpFwHYYpIEBLFV9knyfRXS/428W2qhdzYfvB15/AasRmwmor
py4NIzSs8UD/SPr1ihqNCdZM76+MQyN5HMYXW/ALZXUFG0pwluHFA7hrfPG74i8C
zMiP7qvMWIl/r/jtzHioH1dRKgbod+LZsrDJ8mBaqsZaDmNJMhss9g76XvfMyLra
9DI9/iFuBpGzeqBv0hwOGQspLRrEoyTeR6n1ABEBAAG0H0NvbmxleSBPd2VucyA8
Y2NvM0BhbmRyb2lkLmNvbT6JATgEEwECACIFAlHRvc8CGwMGCwkIBwMCBhUIAgkK
CwQWAgMBAh4BAheAAAoJEGe35EhpKzgsP6AIAJKJmNtn4l7hkYHKHFSo3egb6RjQ
zEIP3MFTcu8HFX1kF1ZFbrp7xqurLaE53kEkKuAAvjJDAgI8mcZHP1JyplubqjQA
xvv84gK+OGP3Xk+QK1ZjUQSbjOpjEiSZpRhWcHci3dgOUH4blJfByHw25hlgHowd
a/2PrNKZVcJ92YienaxxGjcXEUcd0uYEG2+rwllQigFcnMFDhr9B71MfalRHjFKE
fmdoypqLrri61YBc59P88Rw2/WUpTQjgNubSqa3A2+CKdaRyaRw+2fdF4TdR0h8W
zbg+lbaPtJHsV+3mJC7fq26MiJDRJa5ZztpMn8su20gbLgi2ShBOaHAYDDi5AQ0E
UdG9zwEIAMoOBq+QLNozAhxOOl5GL3StTStGRgPRXINfmViTsihrqGCWBBUfXlUE
OytC0mYcrDUQev/8ToVoyqw+iGSwDkcSXkrEUCKFtHV/GECWtk1keyHgR10YKI1R
mquSXoubWGqPeG1PAI74XWaRx8UrL8uCXUtmD8Q5J7mDjKR5NpxaXrwlA0bKsf2E
Gp9tu1kKauuToZhWHMRMqYSOGikQJwWSFYKT1KdNcOXLQF6+bfoJ6sjVYdwfmNQL
Ixn8QVhoTDedcqClSWB17VDEFDFa7MmqXZz2qtM3X1R/MUMHqPtegQzBGNhRdnI2
V45+1Nnx/uuCxDbeI4RbHzujnxDiq70AEQEAAYkBHwQYAQIACQUCUdG9zwIbDAAK
CRBnt+RIaSs4LNVeB/0Y2pZ8I7gAAcEM0Xw8drr4omg2fUoK1J33ozlA/RxeA/lJ
I3KnyCDTpXuIeBKPGkdL8uMATC9Z8DnBBajRlftNDVZS3Hz4G09G9QpMojvJkFJV
By+01Flw/X+eeN8NpqSuLV4W+AjEO8at/VvgKr1AFvBRdZ7GkpI1o6DgPe7ZqX+1
dzQZt3e13W0rVBb/bUgx9iSLoeWP3aq/k+/GRGOR+S6F6BBSl0SQ2EF2+dIywb1x
JuinEP+AwLAUZ1Bsx9ISC0Agpk2VeHXPL3FGhroEmoMvBzO0kTFGyoeT7PR/BfKv
+H/g3HsL2LOB9uoIm8/5p2TTU5ttYCXMHhQZ81AY
=AUp4
-----END PGP PUBLIC KEY BLOCK-----

[Ctrl-D]
</syntaxhighlight>

== Sync Android ==
<syntaxhighlight lang="bash">
cd sxr2130-la-1-0-sdx55-tn-1-0_amss_standard_oem_apq.git/sxr2130_apps/LINUX/android
./sync.sh
</syntaxhighlight>

== Build the application processor Android HLOS images ==
<syntaxhighlight lang="bash">
sudo apt-get install libxml*
source build/envsetup.sh
lunch kona-userdebug
./build.sh dist -j8 |& tee make-log.txt
</syntaxhighlight>

== Location of Android HLOS images ==
<pre>
ls out/target/product/kona
abl.elf dtb.img installed-files-vendor.json persist shareduid_violation_modules.json
android-info.txt dtbo.img installed-files-vendor.txt persist.img signed
appcompat dynamic_partition_metadata.txt integrity pgo_profile_file_missing.txt signed_encrypted
appcompat.zip fake_packages ipa prebuilt_dtbo.img soong_to_convert.txt
boot-debug.img filesmap kernel previous_build_config.mk super_empty.img
boot.img gen kona-apps-eng.ganzin.zip product_copy_files_ignored.txt super.img
boot.zip gensecimage_target.timestamp kona-coverage-eng.ganzin.zip product.img symbols
build_fingerprint.txt installed-files-odm.json kona-img-eng.ganzin.zip ramdisk system
build_system_stats.txt installed-files-odm.txt kona-symbols-eng.ganzin.zip ramdisk-debug.img system.img
build_thumbprint.txt installed-files-ramdisk-debug.json metadata ramdisk.img testcases
certificate_violation_modules.txt installed-files-ramdisk-debug.txt metadata.img ramdisk-recovery.img userdata.img
clean_steps.mk installed-files-ramdisk.json module-info.json recovery vbmeta.img
coverage installed-files-ramdisk.txt obj recovery.id vbmeta_system.img
data installed-files-recovery.json obj_arm recovery.img vendor
debug_ramdisk installed-files-recovery.txt odm recovery-two-step.img vendor.img
dexpreopt.config installed-files-root.json odm.img root verified_assembled_vendor_manifest.xml
dlkm installed-files-root.txt otatools.zip secimage.log wall_werror.txt

</pre>

== NON-HLOS images ==
=== bootloader ===
<syntaxhighlight lang="bash">
sudo apt-get install libtinfo* gcc-8 p7zip-full
cd <target_root>/boot_images/QcomPkg/
python ./buildex.py --variant LAA -r RELEASE -t 8250,QcomToolsPkg
</syntaxhighlight>

=== aDSP ===
<syntaxhighlight lang="bash">
cd sxr2130_adsp/adsp_proc/build/ms
python build_variant.py 8250.adsp.prod
</syntaxhighlight>

=== cDSP ===
<syntaxhighlight lang="bash">
cd sxr2130_cdsp/cdsp_proc/build/ms
python build_variant.py 8250.cdsp.prod
</syntaxhighlight>

=== SLIP ===
<syntaxhighlight lang="bash">
cp nanopb-0.3.6-linux-x86.tar.gz sxr2130_slpi/slpi_proc/ssc_api
cd sxr2130_slpi/slpi_proc
python ssc_api/build/config_nanopb_dependency.py -f nanopb-0.3.6-linux-x86
cd sxr2130_slpi/slpi_proc/build/ms
python ./build_variant.py 8250.slpi.prod SENSOR_VARIANT=xr USES_FLAGS=USES_SXR2130_ENABLE
</syntaxhighlight>

== Program images ==
* boot into fastboot mode in device
<pre>
#get device console first, and run following command
reboot bootloader
</pre>

* Check device availability
<pre>
tommy@tommy-ThinkPad-X1-Carbon-5th:~/projects/ganzin/kona_img$ fastboot devices
45ff8ad1 fastboot
</pre>

* Pre load test
<pre>
tommy@tommy-ThinkPad-X1-Carbon-5th:~/projects/ganzin/kona_img$ fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 2.831s]
booting...
OKAY [ 0.063s]
finished. total time: 2.893s
</pre>

* Start flash image if boot normally.....
<pre>
tommy@tommy-ThinkPad-X1-Carbon-5th:~/projects/ganzin/kona_img$ fastboot flash boot_a boot.img
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.950s]
writing 'boot_a'...
OKAY [ 0.209s]
finished. total time: 3.159s
</pre>

* Check marker in boot log
<pre>
#get console first!

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x51df805e]
[ 0.000000] Linux version 4.19.81+ (ganzin@ganzin-sw) (clang version 8.0.12 for Android NDK) #1 SMP PREEMPT Wed Jun 24 19:31:22 CST 2020
[ 0.000000] Machine model: Qualcomm Technologies, Inc. kona HDK
[ 0.000000] earlycon: msm_geni_serial0 at MMIO 0x0000000000a90000 (options '')
[ 0.000000] bootconsole [msm_geni_serial0] enabled
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] Memory limit set/overridden to 5065MB
[ 0.000000] OF: reserved mem: OVERLAP DETECTED!
</pre>

[[Category:Boards and SoCs]]

OpenSync

2026-08-23T10:01:22Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Packaging '''OpenSync''' for Yocto and OpenWrt, and the patches each needed.

== Yocto ==
* tree
<pre>
project-spec/meta-user/recipes-apps/opensync
├── files
│ ├── opensync-master.zip
│ └── protobuf-c.patch
├── opensync.bb

</pre>
*opensync.bb
<pre>
#
# Copyright (C) 2019 Tommy C. Liu
#

SUMMARY = "Opensync"
SECTION = "PETALINUX/apps"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

SRC_URI = "file://opensync-master.zip \
file://protobuf-c.patch"

S = "${WORKDIR}/opensync-master"
DEPENDS = "mosquitto libev jansson openssl protobuf-c libpcap"

INHIBIT_PACKAGE_STRIP = "1"

DIST_NAME = "zynq"
CPU_TYPE = "arm"

EXTRA_OEMAKE = "DIST_NAME='${DIST_NAME}' CPU_TYPE='${CPU_TYPE}' STRIP='${STRIP}' LD='${LD}' CC='${CC}' CFLAGS='${CFLAGS} -DCONFIG_INET_GRE_USE_GRETAP -DTARGET_NAME="\"$(TARGET)\""' LDFLAGS='${LDFLAGS} -Iljansson'"

do_install() {
install -d ${D}/${bindir}
install -m 0755 ${S}/work/native-${DIST_NAME}-${CPU_TYPE}/rootfs/usr/plume/bin/* ${D}/${bindir}
}
</pre>

*files - protobuf-c.patch
<syntaxhighlight lang="c">
diff -Nur a/src/lib/datapipeline/src/dppline.c b/src/lib/datapipeline/src/dppline.c
--- a/src/lib/datapipeline/src/dppline.c 2019-01-31 16:28:16.706026178 +0800
+++ b/src/lib/datapipeline/src/dppline.c 2019-02-01 12:07:44.301173505 +0800
@@ -27,7 +27,7 @@
#include <stdint.h>
#include <stdio.h>
#include <string.h>
-#include <protobuf-c.h>
+#include <protobuf-c/protobuf-c.h>
#include <unistd.h>

#include "target.h"
</syntaxhighlight>

== OpenWrt ==
*tree
<pre>
openwrt/package/network/utils/opensync/
├── Makefile
└── patches
├── 000-arm-mk.patch
├── 001-ssize.patch
└── 002-protobuf-c.patch
</pre>

* Makefile
<pre>
#
# Copyright (C) 2019 Tommy C. Liu
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#

include $(TOPDIR)/rules.mk

PKG_NAME:=opensync
PKG_VERSION:=master
PKG_RELEASE:=1
PKG_MAINTAINER:=Tommy C. Liu <tommy.using@gmail.com>

PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz

PKG_LICENSE:=GPL-2.0
PKG_LICENSE_FILES:=docs/LICENSE

PKG_USE_MIPS16:=0
#PKG_AUTOMAKE_PATHS:=src

PKG_SOURCE_PROTO:=git
PKG_SOURCE_URL:=https://github.com/plume-design/opensync
PKG_SOURCE_VERSION:=e368be0df2763895ed7877ae9e802c40fd38af40
PKG_MIRROR_HASH:=2036cedd366c9f38583986d27b1aabb49a0e120641cc9e9023c83e4ac5dae5ed

include $(INCLUDE_DIR)/package.mk
#CONFIGURE_PATH:=src
#MAKE_PATH:=src

define Package/opensync
SECTION:=net
CATEGORY:=Network
SUBMENU:=wireless
TITLE:=Cloud-agnostic software for the delivery, curation, and management of services for the modern home.
URL:=https://github.com/plume-design/opensync
DEPENDS:=+jansson +libev +libprotobuf-c +libopenssl +libmosquitto +zlib
CFLAGS="$(TARGET_CFLAGS) -Wall"
endef

define Package/opensync/description
It acts as a silicon, CPE, and cloud-agnostic connection between in-home hardware devices and the cloud. It provides modern utilities for collecting measurements and statistics from devices, controlling and managing devices, and provides capabilities for specific services including Wi-Fi meshing, access control, cyber security, parental controls, and IoT onboarding and telemetry.
endef

define Build/Compile
$(call Build/Compile/Default)
endef

define Package/opensync/install
$(INSTALL_DIR) $(1)/usr/sbin
$(INSTALL_BIN) $(PKG_BUILD_DIR)/work/native/bin/* $(1)/usr/sbin/
endef

$(eval $(call BuildPackage,opensync))
</pre>
*patche - 000-arm-mk.patch
<pre>
diff -Nur build/arm.mk build.new/arm.mk
--- a/build/arm.mk 1970-01-01 08:00:00.000000000 +0800
+++ b/build.new/arm.mk 2019-01-30 14:07:56.003034972 +0800
@@ -0,0 +1,61 @@
+# Copyright (c) 2015, Plume Design Inc. All rights reserved.
+#
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following conditions are met:
+# 1. Redistributions of source code must retain the above copyright
+# notice, this list of conditions and the following disclaimer.
+# 2. Redistributions in binary form must reproduce the above copyright
+# notice, this list of conditions and the following disclaimer in the
+# documentation and/or other materials provided with the distribution.
+# 3. Neither the name of the Plume Design Inc. nor the
+# names of its contributors may be used to endorse or promote products
+# derived from this software without specific prior written permission.
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+# DISCLAIMED. IN NO EVENT SHALL Plume Design Inc. BE LIABLE FOR ANY
+# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+# (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+# LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+#
+# native configuration
+#
+
+BUILD_SHARED_LIB = n
+
+DIST_NAME = $(shell if [ -e /etc/os-release ]; then . /etc/os-release; echo $$ID$$VERSION_ID; fi)
+ifneq ($(DIST_NAME),)
+endif
+
+SDK_ROOTFS = $(OBJDIR)/rootfs
+
+CC = arm-none-eabi-gcc
+CXX = arm-none-eabi-g++
+AR = arm-none-eabi-ar
+STRIP = arm-none-eabi-strip -g
+
+
+# Includes
+CFLAGS += -I/usr/include/protobuf-c
+# Flags
+CFLAGS += -O3 -pipe
+CFLAGS += -rdynamic
+CFLAGS += -fno-caller-saves
+CFLAGS += -fno-strict-aliasing
+CFLAGS += -fasynchronous-unwind-tables
+CFLAGS += -Wno-error=unused-but-set-variable
+CFLAGS += -Wno-error=cpp
+
+# Defines
+CFLAGS += -D_U_="__attribute__((unused))"
+
+export CC
+export CXX
+export CFLAGS
+export LIBS
+
</pre>

*patche - 001-ssize.patch
<syntaxhighlight lang="c">
diff -Nur a/src/lib/read_until/inc/read_until.h b/src/lib/read_until/inc/read_until.h
--- a/src/lib/read_until/inc/read_until.h 2019-01-30 14:26:18.296457064 +0800
+++ b/src/lib/read_until/inc/read_until.h 2019-01-30 14:25:59.911734213 +0800
@@ -29,6 +29,7 @@

#include <stdlib.h>
#include <string.h>
+#include <stdio.h>

/**
* This is quite similar to fgets() except that it works with non-blocking I/O
Binary files /home/tommy/Projects/plume/openwrt/build_dir/target-arm_cortex-a9+neon_musl_eabi/opensync-master/src/lib/read_until/inc/.read_until.h.swp and /home/tommy/Projects/plume/openwrt/build_dir/target-arm_cortex-a9+neon_musl_eabi/opensync-master.new/src/lib/read_until/inc/.read_until.h.swp differ
</syntaxhighlight>

*patche - 002-protobuf-c.patch
<syntaxhighlight lang="c">
diff -Nur a/src/lib/datapipeline/src/dppline.c b/src/lib/datapipeline/src/dppline.c
--- a/src/lib/datapipeline/src/dppline.c 2019-01-30 14:56:43.275897685 +0800
+++ b/src/lib/datapipeline/src/dppline.c 2019-01-30 14:56:11.527669148 +0800
@@ -27,7 +27,7 @@
#include <stdint.h>
#include <stdio.h>
#include <string.h>
-#include <protobuf-c.h>
+#include <protobuf-c/protobuf-c.h>
#include <unistd.h>

#include "target.h"
</syntaxhighlight>

[[Category:Software and Tools]]

ODROID-C4

2026-08-23T10:01:21Z

Tommy：Consistency: syntax highlighting for code, File: prefix

The '''ODROID-C4''' is an Amlogic S905X3 single-board computer. These notes cover its pin map and building Android for it.

[[File:C4_k.jpg|500px|ODROID-C4]]

== Board Description ==
[[File:C4_board.jpg|600px|ODROID-C4 Board]]
<br>
[[File:C4_board_detail.png|600px|ODROID-C4 Detail]]

== Pin definition ==
[[File:C4_40pinmap_rev0.4.png|500px|]]

* UART signals are driven at 1.8V.

== Build Android ==

=== Download Toolchains ===
; U-boot
: http://releases.linaro.org/archive/14.09/components/toolchain/binaries/gcc-linaro-aarch64-none-elf-4.9-2014.09_linux.tar.xz
: http://releases.linaro.org/archive/14.04/components/toolchain/binaries/gcc-linaro-arm-none-eabi-4.8-2014.04_linux.tar.xz
; Linux kernel
: https://releases.linaro.org/components/toolchain/binaries/6.3-2017.05/aarch64-linux-gnu/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu.tar.xz

=== Set PATH ===
<pre>
$ export PATH=$PATH:/opt/toolchains/gcc-linaro-aarch64-none-elf-4.9-2014.09_linux/bin
$ export PATH=$PATH:/opt/toolchains/gcc-linaro-arm-none-eabi-4.8-2014.04_linux/bin
$ export PATH=$PATH:/opt/toolchains/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu/bin
</pre>
=== Check out full source code ===
; 32 bit
<pre>
$ mkdir odroid-c4
$ cd odroid-c4
$ repo init -u https://github.com/hardkernel/android.git -b g12_9.0.0_master
$ repo sync
</pre>
; 64 bit
<pre>
$ mkdir odroid-c4
$ cd odroid-c4
$ repo init -u https://github.com/hardkernel/android.git -b g12_9.0.0_64_master
$ repo sync
</pre>

=== Build ===
<pre>
$ source build/envsetup.sh
$ lunch odroidc4-eng
$ make -j<core number>
</pre>

== One touch self install ==
; Create image
: make -j<core number> selfinstall

; Burn image
<pre>
$ sudo dd if=out/target/product/odroidc4/selfinstall-odroidc4.img of=/dev/sdd
$ sync
$ sudo eject /dev/sdd
</pre>

== Android note ==
* Disable ICMP for enable ping
** sysctl -w net.ipv4.icmp_echo_ignore_all=0

== Reference ==
* [https://wiki.odroid.com/odroid-c4/software/building_android ODROID-C4 Building android]
* [https://wiki.odroid.com/odroid-c4/odroid-c4 ODROID-C4]

[[Category:Boards and SoCs]]

Nordic, nRF52 Preview DK

2026-08-23T10:01:21Z

Tommy：Consistency: syntax highlighting for code, File: prefix

NXP, i.MX 6UL

2026-08-23T10:01:20Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Building a Yocto BSP for the NXP '''i.MX 6UL''', and the patches needed to get the older host tools to build.

[[File:Mcimx6ul-evk.jpg|500px|i.MX 6UL EVB]]
== Build ==
* Get fsl_yocto-L4.1.15_2.0.0-ga.tar.gz
** Install the `repo` utility: (only need to do this once)
<pre>
$: mkdir ~/bin
$: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$: chmod a+x ~/bin/repo
$: PATH=${PATH}:~/bin
</pre>

** Download the BSP Yocto Project Environment into your directory
<pre>
$: mkdir fsl-arm-yocto-bsp
$: cd fsl-arm-yocto-bsp
$: repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth
$: repo sync
</pre>

== Patches - m4-1.4.17 ==
* fseeko.patch
<syntaxhighlight lang="c">
--- ./tmp/work/x86_64-linux/m4-native/1.4.17-r0/m4-1.4.17/lib/fseeko.c 2019-11-13 22:03:56.999217823 +0800
+++ /home/tommy/Downloads/gnulib/lib/fseeko.c 2019-11-13 21:49:41.532465868 +0800
@@ -1,9 +1,9 @@
/* An fseeko() function that, together with fflush(), is POSIX compliant.
- Copyright (C) 2007-2013 Free Software Foundation, Inc.
+ Copyright (C) 2007-2019 Free Software Foundation, Inc.

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 3, or (at your option)
+ the Free Software Foundation; either version 2, or (at your option)
any later version.

This program is distributed in the hope that it will be useful,
@@ -12,7 +12,7 @@
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
- with this program; if not, see <http://www.gnu.org/licenses/>. */
+ with this program; if not, see <https://www.gnu.org/licenses/>. */

#include <config.h>

@@ -33,9 +33,9 @@
#endif
#if _GL_WINDOWS_64_BIT_OFF_T
# undef fseeko
-# if HAVE__FSEEKI64 /* msvc, mingw64 */
+# if HAVE__FSEEKI64 && HAVE_DECL__FSEEKI64 /* msvc, mingw since msvcrt8.0, mingw64 */
# define fseeko _fseeki64
-# else /* mingw */
+# else /* mingw before msvcrt8.0 */
# define fseeko fseeko64
# endif
#endif
@@ -47,11 +47,13 @@
#endif

/* These tests are based on fpurge.c. */
-#if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */
+#if defined _IO_EOF_SEEN || defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1
+ /* GNU libc, BeOS, Haiku, Linux libc5 */
if (fp->_IO_read_end == fp->_IO_read_ptr
&& fp->_IO_write_ptr == fp->_IO_write_base
&& fp->_IO_save_base == NULL)
-#elif defined __sferror || defined __DragonFly__ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin */
+#elif defined __sferror || defined __DragonFly__ || defined __ANDROID__
+ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin, Minix 3, Android */
# if defined __SL64 && defined __SCLE /* Cygwin */
if ((fp->_flags & __SL64) == 0)
{
@@ -79,7 +81,7 @@
#elif defined __minix /* Minix */
if (fp_->_ptr == fp_->_buf
&& (fp_->_ptr == NULL || fp_->_count == 0))
-#elif defined _IOERR /* AIX, HP-UX, IRIX, OSF/1, Solaris, OpenServer, mingw, NonStop Kernel */
+#elif defined _IOERR /* AIX, HP-UX, IRIX, OSF/1, Solaris, OpenServer, mingw, MSVC, NonStop Kernel, OpenVMS */
if (fp_->_ptr == fp_->_base
&& (fp_->_ptr == NULL || fp_->_cnt == 0))
#elif defined __UCLIBC__ /* uClibc */
@@ -115,17 +117,20 @@
off_t pos = lseek (fileno (fp), offset, whence);
if (pos == -1)
{
-#if defined __sferror || defined __DragonFly__ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin */
+#if defined __sferror || defined __DragonFly__ || defined __ANDROID__
+ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin, Minix 3, Android */
fp_->_flags &= ~__SOFF;
#endif
return -1;
}

-#if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */
+#if defined _IO_EOF_SEEN || defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1
+ /* GNU libc, BeOS, Haiku, Linux libc5 */
fp->_flags &= ~_IO_EOF_SEEN;
fp->_offset = pos;
-#elif defined __sferror || defined __DragonFly__ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin */
-# if defined __CYGWIN__
+#elif defined __sferror || defined __DragonFly__ || defined __ANDROID__
+ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin, Minix 3, Android */
+# if defined __CYGWIN__ || (defined __NetBSD__ && __NetBSD_Version__ >= 600000000) || defined __minix
/* fp_->_offset is typed as an integer. */
fp_->_offset = pos;
# else
@@ -147,8 +152,8 @@
fp_->_flags &= ~__SEOF;
#elif defined __EMX__ /* emx+gcc */
fp->_flags &= ~_IOEOF;
-#elif defined _IOERR /* AIX, HP-UX, IRIX, OSF/1, Solaris, OpenServer, mingw, NonStop Kernel */
- fp->_flag &= ~_IOEOF;
+#elif defined _IOERR /* AIX, HP-UX, IRIX, OSF/1, Solaris, OpenServer, mingw, MSVC, NonStop Kernel, OpenVMS */
+ fp_->_flag &= ~_IOEOF;
#elif defined __MINT__ /* Atari FreeMiNT */
fp->__offset = pos;
fp->__eof = 0;
</syntaxhighlight>
* freadahead.patch
<syntaxhighlight lang="c">
--- ./tmp/work/x86_64-linux/m4-native/1.4.17-r0/m4-1.4.17/lib/freadahead.c 2013-09-22 14:15:20.000000000 +0800
+++ /home/tommy/Downloads/gnulib/lib/freadahead.c 2019-11-13 21:49:41.528465850 +0800
@@ -1,5 +1,5 @@
/* Retrieve information about a FILE stream.
- Copyright (C) 2007-2013 Free Software Foundation, Inc.
+ Copyright (C) 2007-2019 Free Software Foundation, Inc.

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
@@ -12,7 +12,7 @@
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>. */
+ along with this program. If not, see <https://www.gnu.org/licenses/>. */

#include <config.h>

@@ -22,16 +22,26 @@
#include <stdlib.h>
#include "stdio-impl.h"

+#if defined __DragonFly__
+/* Defined in libc, but not declared in <stdio.h>. */
+extern size_t __sreadahead (FILE *);
+#endif
+
+/* This file is not used on systems that have the __freadahead function,
+ namely musl libc. */
+
size_t
freadahead (FILE *fp)
{
-#if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */
+#if defined _IO_EOF_SEEN || defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1
+ /* GNU libc, BeOS, Haiku, Linux libc5 */
if (fp->_IO_write_ptr > fp->_IO_write_base)
return 0;
return (fp->_IO_read_end - fp->_IO_read_ptr)
+ (fp->_flags & _IO_IN_BACKUP ? fp->_IO_save_end - fp->_IO_save_base :
0);
-#elif defined __sferror || defined __DragonFly__ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin */
+#elif defined __sferror || defined __DragonFly__ || defined __ANDROID__
+ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin, Minix 3, Android */
if ((fp_->_flags & __SWR) != 0 || fp_->_r < 0)
return 0;
# if defined __DragonFly__
@@ -52,7 +62,7 @@
if ((fp_->_flags & _IOWRITING) != 0)
return 0;
return fp_->_count;
-#elif defined _IOERR /* AIX, HP-UX, IRIX, OSF/1, Solaris, OpenServer, mingw, NonStop Kernel */
+#elif defined _IOERR /* AIX, HP-UX, IRIX, OSF/1, Solaris, OpenServer, mingw, MSVC, NonStop Kernel, OpenVMS */
if ((fp_->_flag & _IOWRT) != 0)
return 0;
return fp_->_cnt;

</syntaxhighlight>
* stdio-impl.patch
<syntaxhighlight lang="c">
--- ./tmp/work/x86_64-linux/m4-native/1.4.17-r0/m4-1.4.17/lib/stdio-impl.h 2013-09-22 14:20:02.000000000 +0800
+++ /home/tommy/Downloads/gnulib/lib/stdio-impl.h 2019-11-13 21:49:41.568466035 +0800
@@ -1,5 +1,5 @@
/* Implementation details of FILE streams.
- Copyright (C) 2007-2008, 2010-2013 Free Software Foundation, Inc.
+ Copyright (C) 2007-2008, 2010-2019 Free Software Foundation, Inc.

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
@@ -12,12 +12,23 @@
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>. */
+ along with this program. If not, see <https://www.gnu.org/licenses/>. */

/* Many stdio implementations have the same logic and therefore can share
the same implementation of stdio extension API, except that some fields
have different naming conventions, or their access requires some casts. */

+/* Glibc 2.28 made _IO_UNBUFFERED and _IO_IN_BACKUP private. For now, work
+ around this problem by defining them ourselves. FIXME: Do not rely on glibc
+ internals. */
+#if defined _IO_EOF_SEEN
+# if !defined _IO_UNBUFFERED
+# define _IO_UNBUFFERED 0x2
+# endif
+# if !defined _IO_IN_BACKUP
+# define _IO_IN_BACKUP 0x100
+# endif
+#endif

/* BSD stdio derived implementations. */

@@ -28,10 +39,11 @@

#include <errno.h> /* For detecting Plan9. */

-#if defined __sferror || defined __DragonFly__ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin */
+#if defined __sferror || defined __DragonFly__ || defined __ANDROID__
+ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin, Minix 3, Android */

# if defined __DragonFly__ /* DragonFly */
- /* See <http://www.dragonflybsd.org/cvsweb/src/lib/libc/stdio/priv_stdio.h?rev=HEAD&content-type=text/x-cvsweb-markup>. */
+ /* See <https://gitweb.dragonflybsd.org/dragonfly.git/blob_plain/HEAD:/lib/libc/stdio/priv_stdio.h>. */
# define fp_ ((struct { struct __FILE_public pub; \
struct { unsigned char *_base; int _size; } _bf; \
void *cookie; \
@@ -48,30 +60,89 @@
fpos_t _offset; \
/* More fields, not relevant here. */ \
} *) fp)
- /* See <http://www.dragonflybsd.org/cvsweb/src/include/stdio.h?rev=HEAD&content-type=text/x-cvsweb-markup>. */
+ /* See <https://gitweb.dragonflybsd.org/dragonfly.git/blob_plain/HEAD:/include/stdio.h>. */
# define _p pub._p
# define _flags pub._flags
# define _r pub._r
# define _w pub._w
+# elif defined __ANDROID__ /* Android */
+# ifdef __LP64__
+# define _gl_flags_file_t int
+# else
+# define _gl_flags_file_t short
+# endif
+ /* Up to this commit from 2015-10-12
+ <https://android.googlesource.com/platform/bionic.git/+/f0141dfab10a4b332769d52fa76631a64741297a>
+ the innards of FILE were public, and fp_ub could be defined like for OpenBSD,
+ see <https://android.googlesource.com/platform/bionic.git/+/e78392637d5086384a5631ddfdfa8d7ec8326ee3/libc/stdio/fileext.h>
+ and <https://android.googlesource.com/platform/bionic.git/+/e78392637d5086384a5631ddfdfa8d7ec8326ee3/libc/stdio/local.h>.
+ After this commit, the innards of FILE are hidden. */
+# define fp_ ((struct { unsigned char *_p; \
+ int _r; \
+ int _w; \
+ _gl_flags_file_t _flags; \
+ _gl_flags_file_t _file; \
+ struct { unsigned char *_base; size_t _size; } _bf; \
+ int _lbfsize; \
+ void *_cookie; \
+ void *_close; \
+ void *_read; \
+ void *_seek; \
+ void *_write; \
+ struct { unsigned char *_base; size_t _size; } _ext; \
+ unsigned char *_up; \
+ int _ur; \
+ unsigned char _ubuf[3]; \
+ unsigned char _nbuf[1]; \
+ struct { unsigned char *_base; size_t _size; } _lb; \
+ int _blksize; \
+ fpos_t _offset; \
+ /* More fields, not relevant here. */ \
+ } *) fp)
# else
# define fp_ fp
# endif

-# if (defined __NetBSD__ && __NetBSD_Version__ >= 105270000) || defined __OpenBSD__ || defined __ANDROID__ /* NetBSD >= 1.5ZA, OpenBSD, Android */
+# if (defined __NetBSD__ && __NetBSD_Version__ >= 105270000) || defined __OpenBSD__ || defined __minix /* NetBSD >= 1.5ZA, OpenBSD, Minix 3 */
/* See <http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/stdio/fileext.h?rev=HEAD&content-type=text/x-cvsweb-markup>
- and <http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libc/stdio/fileext.h?rev=HEAD&content-type=text/x-cvsweb-markup> */
+ and <https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libc/stdio/fileext.h?rev=HEAD&content-type=text/x-cvsweb-markup>
+ and <https://github.com/Stichting-MINIX-Research-Foundation/minix/blob/master/lib/libc/stdio/fileext.h> */
struct __sfileext
{
struct __sbuf _ub; /* ungetc buffer */
/* More fields, not relevant here. */
};
# define fp_ub ((struct __sfileext *) fp->_ext._base)->_ub
+# elif defined __ANDROID__ /* Android */
+ struct __sfileext
+ {
+ struct { unsigned char *_base; size_t _size; } _ub; /* ungetc buffer */
+ /* More fields, not relevant here. */
+ };
+# define fp_ub ((struct __sfileext *) fp_->_ext._base)->_ub
# else /* FreeBSD, NetBSD <= 1.5Z, DragonFly, Mac OS X, Cygwin */
# define fp_ub fp_->_ub
# endif

# define HASUB(fp) (fp_ub._base != NULL)

+# if defined __ANDROID__ /* Android */
+ /* Needed after this commit from 2016-01-25
+ <https://android.googlesource.com/platform/bionic.git/+/e70e0e9267d069bf56a5078c99307e08a7280de7> */
+# ifndef __SEOF
+# define __SLBF 1
+# define __SNBF 2
+# define __SRD 4
+# define __SWR 8
+# define __SRW 0x10
+# define __SEOF 0x20
+# define __SERR 0x40
+# endif
+# ifndef __SOFF
+# define __SOFF 0x1000
+# endif
+# endif
+
#endif

@@ -80,7 +151,7 @@
#ifdef __TANDEM /* NonStop Kernel */
# ifndef _IOERR
/* These values were determined by the program 'stdioext-flags' at
- <http://lists.gnu.org/archive/html/bug-gnulib/2010-12/msg00165.html>. */
+ <https://lists.gnu.org/r/bug-gnulib/2010-12/msg00165.html>. */
# define _IOERR 0x40
# define _IOREAD 0x80
# define _IOWRT 0x4
@@ -98,6 +169,8 @@
int _file; \
unsigned int _flag; \
} *) fp)
+# elif defined __VMS /* OpenVMS */
+# define fp_ ((struct _iobuf *) fp)
# else
# define fp_ fp
# endif
@@ -109,4 +182,31 @@
# define _flag __flag
# endif

+#elif defined _WIN32 && ! defined __CYGWIN__ /* newer Windows with MSVC */
+
+/* <stdio.h> does not define the innards of FILE any more. */
+# define WINDOWS_OPAQUE_FILE
+
+struct _gl_real_FILE
+{
+ /* Note: Compared to older Windows and to mingw, it has the fields
+ _base and _cnt swapped. */
+ unsigned char *_ptr;
+ unsigned char *_base;
+ int _cnt;
+ int _flag;
+ int _file;
+ int _charbuf;
+ int _bufsiz;
+};
+# define fp_ ((struct _gl_real_FILE *) fp)
+
+/* These values were determined by a program similar to the one at
+ <https://lists.gnu.org/r/bug-gnulib/2010-12/msg00165.html>. */
+# define _IOREAD 0x1
+# define _IOWRT 0x2
+# define _IORW 0x4
+# define _IOEOF 0x8
+# define _IOERR 0x10
+
#endif
</syntaxhighlight>

== Patches - bison_3.0.4.bb ==
* fseterr.patch
<syntaxhighlight lang="c">
--- ./tmp/work/x86_64-linux/bison-native/3.0.4-r0/bison-3.0.4/lib/fseterr.c 2015-01-05 00:43:50.000000000 +0800
+++ /home/tommy/Downloads/gnulib/lib/fseterr.c 2019-11-13 21:49:41.532465868 +0800
@@ -1,5 +1,5 @@
/* Set the error indicator of a stream.
- Copyright (C) 2007-2015 Free Software Foundation, Inc.
+ Copyright (C) 2007-2019 Free Software Foundation, Inc.

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
@@ -12,7 +12,7 @@
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
- along with this program. If not, see <http://www.gnu.org/licenses/>. */
+ along with this program. If not, see <https://www.gnu.org/licenses/>. */

#include <config.h>

@@ -23,21 +23,26 @@

#include "stdio-impl.h"

+/* This file is not used on systems that have the __fseterr function,
+ namely musl libc. */
+
void
fseterr (FILE *fp)
{
/* Most systems provide FILE as a struct and the necessary bitmask in
<stdio.h>, because they need it for implementing getc() and putc() as
fast macros. */
-#if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */
+#if defined _IO_EOF_SEEN || defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1
+ /* GNU libc, BeOS, Haiku, Linux libc5 */
fp->_flags |= _IO_ERR_SEEN;
-#elif defined __sferror || defined __DragonFly__ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin */
+#elif defined __sferror || defined __DragonFly__ || defined __ANDROID__
+ /* FreeBSD, NetBSD, OpenBSD, DragonFly, Mac OS X, Cygwin, Minix 3, Android */
fp_->_flags |= __SERR;
#elif defined __EMX__ /* emx+gcc */
fp->_flags |= _IOERR;
#elif defined __minix /* Minix */
fp->_flags |= _IOERR;
-#elif defined _IOERR /* AIX, HP-UX, IRIX, OSF/1, Solaris, OpenServer, mingw, NonStop Kernel */
+#elif defined _IOERR /* AIX, HP-UX, IRIX, OSF/1, Solaris, OpenServer, mingw, MSVC, NonStop Kernel, OpenVMS */
fp_->_flag |= _IOERR;
#elif defined __UCLIBC__ /* uClibc */
fp->__modeflags |= __FLAG_ERROR;
</syntaxhighlight>

== Patches - rpm-native ==
<pre>
Index: rpm/rpmio/rpmio.h
=== = ===
--- rpm.orig/rpmio/rpmio.h
+++ rpm/rpmio/rpmio.h
@@ -23,7 +23,9 @@
*/
/*@{*/
#if !defined(__LCLINT__) && !defined(__UCLIBC__) && defined(__GLIBC__) && \
- (__GLIBC__ > 2 || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 2))
+ (__GLIBC__ > 2 || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 2)) && \
+ !defined(__UCLIBC__)
#define USE_COOKIE_SEEK_POINTER 1
+#define _IO_off64_t __off64_t
typedef _IO_off64_t _libio_off_t;
typedef _libio_off_t * _libio_pos_t;
Index: rpm/rpmio/rpmio.h
=== = ===
--- rpm.orig/rpmio/bson.c
+++ rpm/rpmio/bson.c
@@ -3586,7 +3586,7 @@

#if defined(__linux__)
-static uint16_t
+__pid_t
gettid (void)
{
return syscall (SYS_gettid);
</pre>

[[Category:Boards and SoCs]]

Maixduino

2026-08-23T10:01:20Z

Tommy：Consistency: syntax highlighting for code, File: prefix

The '''Maixduino''' is a Kendryte K210 RISC-V board. These notes cover the toolchain, building and customising the firmware, and flashing it.

== Booting message ==
<pre>
[MAIXPY]Pll0:freq:832000000
[MAIXPY]Pll1:freq:398666666
[MAIXPY]Pll2:freq:45066666
[MAIXPY]cpu:freq:416000000
[MAIXPY]kpu:freq:398666666
[MAIXPY]Flash:0xc8:0x17
open second core...
mallocmallocmallocmallocgc heap=0x8027ccb0-0x802fccb0(524288)
[MaixPy] init end

__ __ _____ __ __ _____ __ __
| \/ | /\ |_ _| \ \ / / | __ \ \ \ / /
| \ / | / \ | | \ V / | |__) | \ \_/ /
| |\/| | / /\ \ | | > < | ___/ \ /
| | | | / ____ \ _| |_ / . \ | | | |
|_| |_| /_/ \_\ |_____| /_/ \_\ |_| |_|

Official Site : https://www.sipeed.com
Wiki : https://maixpy.sipeed.com

MicroPython v0.5.0 on 2019-12-11; Sipeed_M1 with kendryte-k210
Type "help()" for more information.
>>>
</pre>
== Toolchain ==
<syntaxhighlight lang="bash">
git clone https://github.com/kendryte/kendryte-gnu-toolchain
cd kendryte-gnu-toolchain
git submodule update --init --recursive
</syntaxhighlight>
=== Prerequisites ===
<syntaxhighlight lang="bash">
sudo apt-get install autoconf automake autotools-dev curl libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev libexpat-dev
</syntaxhighlight>
=== Build ===
<syntaxhighlight lang="bash">
./configure --prefix=/opt/kendryte-toolchain --with-cmodel=medany --with-arch=rv64imafc --with-abi=lp64f
make -j8
</syntaxhighlight>

== FW ==
<syntaxhighlight lang="bash">
git clone https://github.com/sipeed/MaixPy.git
git submodule update --recursive --init
</syntaxhighlight>
=== Install dependencies ===
<syntaxhighlight lang="bash">
sudo apt update
sudo apt install python3 python3-pip build-essential cmake
sudo pip3 install -r requirements.txt
</syntaxhighlight>
=== Configure project ===
<syntaxhighlight lang="bash">
cd MaixPy
cd projects/maixpy_k210
python3 project.py --toolchain /opt/kendryte-toolchain/bin --toolchain-prefix riscv64-unknown-elf- config
</syntaxhighlight>
=== Customize FW ===
<pre>
python3 project.py menuconfig
</pre>
=== Build ===
<pre>
python3 project.py build
</pre>

=== Flash to the board ===
<pre>
python3 project.py -B maixduino -p /dev/ttyUSB0 -b 1500000 -S flash
or,
kflash -B maixduino -p /dev/ttyUSB0 hello_world.bin
</pre>

== Example ==
<syntaxhighlight lang="python">
import sensor
import image
import lcd

lcd.init()
sensor.reset()
sensor.set_pixformat(sensor.RGB565)
sensor.set_framesize(sensor.QVGA)
sensor.run(1)
while True:
img=sensor.snapshot()
lcd.display(img)
</syntaxhighlight>

[[Category:Boards and SoCs]]

Hikey960

2026-08-23T10:01:19Z

Tommy：Consistency: syntax highlighting for code, File: prefix

The '''HiKey960''' is a 96Boards platform. These notes cover building and flashing Android on it, the kernel build, and enabling its 1.8 V UART.

[[File:Hikey-960-SD-front.jpg|300px|Hikey960 Front]]
[[File:Hikey-960-SD-back.jpg|300px|Hikey960 Back]]

== Pin definition ==
[[File:Hikey960-pin-def.jpg]]

* UART signals are driven at 1.8V.

== Build FW ==

* Download the Android source tree:
** repo init -u https://android.googlesource.com/platform/manifest -b master
** repo sync -j8

*Build:
** . ./build/envsetup.sh
** lunch hikey960-userdebug
** make -j24

== Installing initial images ==
*Select fastboot mode by turning ON switch 3 (for details, refer to the HiKey 960 Getting Started guide).
*Power the board.
*Flash initial images:
** cd device/linaro/hikey/installer/hikey960
*Turn OFF switch 3 and power cycle the board.

== Flashing images ==
*Enter fastboot mode by turning ON switch 3.
*Flash images by running the following commands:
** fastboot flash boot out/target/product/hikey960/boot.img
*Turn OFF switch 3 and power cycle the board.

== Building the kernel ==
*Run the following commands:
**mkdir repo-common
**cd repo-common
**repo init -u https://android.googlesource.com/kernel/manifest -b hikey-linaro-android-4.19
**repo sync -j8 -c
**rm -rf out
**rm build.config
**BUILD_CONFIG=hikey-linaro/build.config.hikey960 ./build/build.sh
*Update the kernel in the boot image.
**Copy hi3660-hikey960.dtb (out/android-hikey-linaro-4.19/dist/hi3660-hikey960.dtb) to the hikey-kernel directory as file hi3660-hikey960.dtb-4.19.
**Copy the Image file (out/android-hikey-linaro-4.19/dist/Image.gz-dtb) to the hikey-kernel directory as file Image.gz-dtb-hikey960-4.19.
<pre>
cp repo-common/out/android-hikey-linaro-4.19/dist/hi3660-hikey960.dtb hikey960/device/linaro/hikey-kernel/hi3660-hikey960.dtb-4.19
cp repo-common/out/android-hikey-linaro-4.19/dist/Image.gz-dtb hikey960/device/linaro/hikey-kernel/Image.gz-dtb-hikey960-4.19
</pre>
*Make the boot image:
**make bootimage -j24

== Enable UART ==
* In repo-common/hikey-linaro
<pre>
diff --git a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi
index 80334e500..a2f1de30b 100644
--- a/arch/arm64/boot/dts/hisilicon/hi3660.dtsi
+++ b/arch/arm64/boot/dts/hisilicon/hi3660.dtsi
@@ -494,7 +494,7 @@
clock-names = "uartclk", "apb_pclk";
pinctrl-names = "default";
pinctrl-0 = <&uart0_pmx_func &uart0_cfg_func>;
- status = "disabled";
+ status = "ok";
};

uart1: serial@fdf00000 {
@@ -508,7 +508,7 @@
clock-names = "uartclk", "apb_pclk";
pinctrl-names = "default";
pinctrl-0 = <&uart1_pmx_func &uart1_cfg_func>;
- status = "disabled";
+ status = "ok";
};

uart2: serial@fdf03000 {
</pre>

== Setting the serial number ==
=== To set the random serial number, run ===
**fastboot getvar nve:SN@16\_DIGIT\_NUMBER
*Bootloader exports the generated serial number to the kernel using androidboot.serialno=.

=== Setting monitor resolution ===
*Edit the device/linaro/hikey/hikey960/BoardConfig.mk parameter BOARD_KERNEL_CMDLINE and configure the video setting. For example, the setting for a 24-inch monitor is video=HDMI-A-1:1280x800@60.

== Android note ==
* Disable ICMP for enable ping
** sysctl -w net.ipv4.icmp_echo_ignore_all=0

== Reference ==
* [https://source.android.com/setup/build/devices Build steps]
* [https://snapshots.linaro.org/96boards/hikey960/linaro/aosp-master/latest/ Pre build image]

[[Category:Boards and SoCs]]

ESP8266, Wi-Fi SoC

2026-08-23T10:01:19Z

Tommy：Consistency: syntax highlighting for code, File: prefix

The '''ESP8266''' is a Wi-Fi SoC usually met on a NodeMCU DevKit board. These notes cover flashing the NodeMCU firmware, the ESPlorer and Arduino IDE toolchains, and a few Lua examples.

[[File:Esp8266 nodemcu.jpg|thumb|300px|ESP8266 NodeMCU]]
== Pin definition ==
[[File:Esp8266 Pinout.png| ESP8266 pin definition]]
== Pre-build firmware ==
* Download
** git clone https://github.com/nodemcu/nodemcu-firmware/releases
== NodeMCU flasher ==
<pre>
NodeMCU flasher is a firmware programmer for NodeMCU DEVKIT V0.9.
You can use it to program NodeMCU DEVKIT or your own ESP8266 board.
You MUST set GPIO0 to LOW before programming, and NodeMCU DEVKIT V0.9 will do it automatically.
</pre>
[[File:ESP8266Flasher_1.png|250px|ESP8266Flasher_1]][[File:ESP8266Flasher_2.png|250px|ESP8266Flasher_2]][[File:ESP8266Flasher_3.png|250px|ESP8266Flasher_3]][[File:ESP8266Flasher_4.png|250px|ESP8266Flasher_4]][[File:ESP8266Flasher_5.png|250px|ESP8266Flasher_5]]
* Download
** git clone https://github.com/nodemcu/nodemcu-flasher
** Choice the Win32 / Win64 against your environment
* Prepare & running
** So far, it seems like only can flash success in Windows environment

== ESPlorer ==
[[File:Esplorer.jpg|500px|Esplorer]]
* Download
** http://esp8266.ru/esplorer/#download
* Build from source
<pre>
1. Install Netbeans 8.1, download from here. I used the "All", but I think Java SE should be enough.
2. Install JDK 1.7 (I wasn't able to use JDK 1.8), download from here.
3. Download rsyntaxtextarea 2.5.6.jar (I wasn't able to use any other version) from here, put it somewhere and remember where (e.g.: inside the ESPlorer root dir)
4. Open the project.properties file in a texteditor, and edit file.reference.rsyntaxtextarea-2.5.6.jar to point to where you put rsyntaxtextarea 2.5.6.jar
5. Open netbeans
6. Open the ESPlorer project, you should get an error about the JDK platform
7. Click resolve, add platform
8. Add the JDK 1.7 dir, and where it says Name you should see "JDK 1.7", rename that to "JDK1.7" (notice the lack of a space), close the dialog 9 press F11 to build
9. The ESPLorer .jar should be under the dist subdir
</pre>
* Prepare & running
** Install java
** java -jar EXPlorer.jar

== Breathing LED ==
<syntaxhighlight lang="lua">
pwm.setup(2, 500, 512)
pwm.start(2)

pwm.setduty(2, 0)
i = 0

while true do
while i < 512 do
pwm.setduty(2, i)
i=i+5
tmr.delay(20000)
end

tmr.delay(100000)

while i > 0 do
pwm.setduty(2, i)
i=i-5
tmr.delay(20000)
end

tmr.delay(50000)
end
</syntaxhighlight>

== httpserver to control GPIO ==
* Lua script ( <span style="color:#ff0000">wifi.sta.config SHOULD provide real AP information</span>)
<syntaxhighlight lang="lua">
wifi.setmode(wifi.STATION)
wifi.sta.config("YOUR_NETWORK_NAME","YOUR_NETWORK_PASSWORD")
print(wifi.sta.getip())
led1 = 3
led2 = 4
gpio.mode(led1, gpio.OUTPUT)
gpio.mode(led2, gpio.OUTPUT)
srv=net.createServer(net.TCP)
srv:listen(80,function(conn)
conn:on("receive", function(client,request)
local buf = "";
local _, _, method, path, vars = string.find(request, "([A-Z]+) (.+)?(.+) HTTP");
if(method == nil)then
_, _, method, path = string.find(request, "([A-Z]+) (.+) HTTP");
end
local _GET = {}
if (vars ~= nil)then
for k, v in string.gmatch(vars, "(%w+)=(%w+)&*") do
_GET[k] = v
end
end
buf = buf.."<h1> ESP8266 Web Server</h1>";
buf = buf.."<p>GPIO0 <a href=\"?pin=ON1\"><button>ON</button></a> <a href=\"?pin=OFF1\"><button>OFF</button></a></p>";
buf = buf.."<p>GPIO2 <a href=\"?pin=ON2\"><button>ON</button></a> <a href=\"?pin=OFF2\"><button>OFF</button></a></p>";
local _on,_off = "",""
if(_GET.pin == "ON1")then
gpio.write(led1, gpio.HIGH);
elseif(_GET.pin == "OFF1")then
gpio.write(led1, gpio.LOW);
elseif(_GET.pin == "ON2")then
gpio.write(led2, gpio.HIGH);
elseif(_GET.pin == "OFF2")then
gpio.write(led2, gpio.LOW);
end
client:send(buf);
client:close();
collectgarbage();
end)
end)
</syntaxhighlight>
* Accessing your web server
<pre>
When your ESP8266 restarts it prints in your serial monitor the IP address of your ESP8266.
If you type your ESP8266 IP address in your web browser, you can access your web server.
In my case it’s http://192.168.1.8.
</pre>
[[File:Esp8266_httpserver.png|250px| http server for GPIO control ]]

== Using Arduino IDE as ESP8266 development tool ==
* Download the Arduino IDE 1.8.2 above
* Go to File --> Preferences and add the link http://arduino.esp8266.com/stable/package_esp8266com_index.json to the Additional Boards Manager URLS.
* Go to Tools --> Board --> Boards manager
* You should now have the esp8266 as an option there since you've added it to the Additional Boards. Select it and press Install
* Wait, and then, ....
* Now, You have the ESP8266 boards configure. Choose the board you have, "Generic ESP8266 Module" if you got the regular module

== Related projects ==
* [[application - wifi node (Alexa / IFTTT)]]

== Reference ==
* [https://zh.wikipedia.org/zh-tw/NodeMCU wiki - NodeMCU]
* [http://nodemcu.com/index_en.html NodeMCU]
* [https://github.com/nodemcu/nodemcu-flasher NMCU flasher]
* [http://www.esp8266.com/viewtopic.php?f=22&t=882 ESPlorer]
* [https://github.com/devyte/nodemcu-platform/wiki/How-to-build-ESPlorer-from-sources How-to-build-ESPlorer-from-sources]
* [http://randomnerdtutorials.com/esp8266-web-server/ ESP8266 Web Server Tutorial]
* [http://www.whatimade.today/esp8266-easiest-way-to-program-so-far/ ESP8266 - Easiest way to program so far (Using Arduino IDE)]

[[Category:Boards and SoCs]]

CAN bus

2026-08-23T10:01:19Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Bringing up a '''CAN bus''' with an SN65HVD251 transceiver, looped between the two CAN controllers of an mbed LPC1768.

== CAN TRANSCEIVER Module - SN65HVD251 ==
[[File:CAN_TRANSCEIVER_Module.jpg|border|350px|CAN TRANSCEIVER Module]]
[[File:CAN_TRANSCEIVER_Module_01.jpg|CAN TRANSCEIVER Module]]

== Setup CAN bus ==
* loops the data between the mbed LPC1768's two CAN buses.
[[File:Can.jpg|border|350px|CAN bus + LPC1768]]
[[File:CAN_self_test.png|border|350px|CAN bus looping]]

== Code ==
<syntaxhighlight lang="c">
#include "mbed.h"
#include "CAN.h"

Ticker ticker;
DigitalOut led1(LED1);
DigitalOut led2(LED2);
CAN can1(p9, p10);
CAN can2(p30, p29);
Serial pc(USBTX, USBRX);
char counter = 0;

void send() {
//pc.printf("send()\n");
if(can1.write(CANMessage(1337, &counter, 1))) {
//pc.printf("wloop()\n");
counter++;
//pc.printf("Message sent: %d\n", counter);
}
led1 = !led1;
}

int main() {
pc.printf("main()\n");
ticker.attach(&send, 1);
CANMessage msg;
while(1) {
//pc.printf("loop()\n");
if(can2.read(msg)) {
pc.printf("Message received: %4d\n\r", msg.data[0]);
led2 = !led2;
}
wait(0.2);
}
}

</syntaxhighlight>

== Result ==
* stty -F /dev/ttyACM0 speed 9600 -crtscts cs8 -cstopb -parenb -icrnl
* cat < /dev/ttyACM0
<pre>
The following will using CAN bus to send counting message from 0 to 255 and repeat again:
...
Message received: 246
Message received: 247
Message received: 248
Message received: 249
Message received: 250
Message received: 251
Message received: 252
Message received: 253
Message received: 254
Message received: 255
Message received: 0
Message received: 1
Message received: 2
Message received: 3
Message received: 4
Message received: 5
...
</pre>

== Reference ==
* [https://developer.mbed.org/handbook/CAN ARMmbed CAN]

[[Category:Connectivity]]

Arduino Pro Mini, ATMega328P

2026-08-23T10:01:18Z

Tommy：Consistency: syntax highlighting for code, File: prefix

The '''Arduino Pro Mini''' is a small ATmega328P board. These notes cover the avr-gcc toolchain, the port mapping and programming it without the Arduino IDE.

== Toolchain ==
* sudo apt-get install gcc-avr # A port of GCC to AVR target processor
* sudo apt-get install gdb-avr # AVR GNU debugger
* sudo apt-get install binutils-avr #low-level utilities for building & manipulating object files
* sudo apt-get install avr-libc # AVR Library files
* sudo apt-get install avrdude # command-line program for programming AVR chips.

== Pin definition ==
[[File:ProMiniPinout.png|ProMiniPinout]]
== PORT mapping ==
* PORTD maps to Arduino digital pins 0 to 7
** DDRD - The Port D Data Direction Register - read/write
** PORTD - The Port D Data Register - read/write
** PIND - The Port D Input Pins Register - read only

* PORTB maps to Arduino digital pins 8 to 13 The two high bits (6 & 7) map to the crystal pins and are not usable
** DDRB - The Port B Data Direction Register - read/write
** PORTB - The Port B Data Register - read/write
** PINB - The Port B Input Pins Register - read only

* PORTC maps to Arduino analog pins 0 to 5. Pins 6 & 7 are only accessible on the Arduino Mini
** DDRC - The Port C Data Direction Register - read/write
** PORTC - The Port C Data Register - read/write
** PINC - The Port C Input Pins Register - read only

== LED blinking example ==
* Make sure your makefile have defined F_CPU for clock
<syntaxhighlight lang="c">
#ifndef F_CPU
#define F_CPU 16000000UL // 16 MHz clock speed
#endif

#include <avr/io.h>
#include <util/delay.h>

int main(void)
{
DDRC = 0xFF; //Nakes PORTC as Output
while(1) //infinite loop
{
PORTC = 0xFF; //Turns ON All LEDs
_delay_ms(1000); //1 second delay
PORTC= 0x00; //Turns OFF All LEDs
_delay_ms(1000); //1 second delay
}
}
</syntaxhighlight>

== Program ==
[[File:IMAG0194.jpg|250px|Arduino_FTDI connectivity]]
* The connections to make from the FTDI FT232RL and the Pro Mini are:
<pre>
FTDI232 Arduino_mini
GND --> GND

CTS --> GND

VCC --> VCC (5V for Ardunio Pro Mini 328 - DEV-1113)

TXD --> RXD

RXD --> TXD

DTR --> DTR
</pre>

* Program command
** make program ...or
** sudo avrdude -q -c arduino -P /dev/ttyUSB2 -b 57600 -p atmega328p -U flash:w:led.hex
<pre>
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x1e950f
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "led.hex"
avrdude: input file led.hex auto detected as Intel Hex
avrdude: writing flash (146 bytes):
avrdude: 146 bytes of flash written
avrdude: verifying flash memory against led.hex:
avrdude: load data flash data from input file led.hex:
avrdude: input file led.hex auto detected as Intel Hex
avrdude: input file led.hex contains 146 bytes
avrdude: reading on-chip flash data:
avrdude: verifying ...
avrdude: 146 bytes of flash verified

avrdude: safemode: Fuses OK

avrdude done. Thank you.
</pre>

== Related projects ==
* [[Application - BMA250, triaxial acceleration sensor]]

== Reference ==
* [https://electrosome.com/blinking-led-atmega32-avr-microcontroller/ Blinking LED using Atmega32 Microcontroller and Atmel Studio]
* [https://www.arduino.cc/en/Reference/PortManipulation Port Registers]

[[Category:Boards and SoCs]]

Application - Wifi AP

2026-08-23T10:01:18Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Turning a Raspberry Pi into a '''Wi-Fi access point''' with hostapd and udhcpd, including the NAT configuration for sharing its uplink.

[[File:DSC 2515.JPG|thumb|350px|Wifi AP with GPS]]
== USB wifi dongle ==
ID 148f:3572 Ralink Technology, Corp. RT3572 Wireless Adapter

== Software ==
sudo apt-get install hostapd udhcpd

=== dhcp server ===
*Edit the file /etc/udhcpd.conf and configure it like this:
<pre>
start 192.168.42.2 # This is the range of IPs that the hostspot will give to client devices.
end 192.168.42.20
interface wlan0 # The device uDHCP listens on.
remaining yes
opt dns 8.8.8.8 4.2.2.2 # The DNS servers client devices will use.
opt subnet 255.255.255.0
opt router 192.168.42.1 # The Pi's IP address on wlan0 which we will set up shortly.
opt lease 864000 # 10 day DHCP lease time in seconds
</pre>
*Edit the file /etc/default/udhcpd and change the line:
<pre>
DHCPD_ENABLED="no"
to
#DHCPD_ENABLED="no"
</pre>

=== Hostapd ===
*edit the file /etc/hostapd/hostapd.conf
<pre>
interface=wlan0
driver=nl80211
ssid=My_AP
hw_mode=g
channel=6
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=My_Passphrase
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
</pre>

*Edit the file /etc/default/hostapd
<pre>
#DAEMON_CONF=""
to:
DAEMON_CONF="/etc/hostapd/hostapd.conf"
</pre>

=== Configure NAT (Network Address Translation) ===
* fordwarding
sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
* iptables
<syntaxhighlight lang="bash">
sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
sudo iptables -A FORWARD -i eth0 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -A FORWARD -i wlan0 -o eth0 -j ACCEPT

sudo sh -c "iptables-save > /etc/iptables.ipv4.nat"
up iptables-restore < /etc/iptables.ipv4.nat
</syntaxhighlight>

=== Service enable ===
* makae sure your runlevel
<pre>
$runlevel
N 5
</pre>
* make symbolic link to rcS
<syntaxhighlight lang="bash">
cd /etc/init.d/rc5.d
# put udhcpd to the last
ln -s ../init.d/udhcpd S05udhcpd
ln -s ../init.d/hostapd S01hostapd
</syntaxhighlight>
* service
<syntaxhighlight lang="bash">
sudo systemctl enable hostapd.service
sudo systemctl enable udhcpd.service
</syntaxhighlight>

== Reference ==
[http://elinux.org/RPI-Wireless-Hotspot RPI-Wireless-Hotspot]

[[Category:Projects]]

Application - Speech Recognition

2026-08-23T10:01:17Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Driving Raspberry Pi GPIO from '''speech recognition''', mapping recognised phrases onto pins through a shell script.

[[File:RPi3 TR10.jpg|450px|RPi3 + TR10]]
[[File:Rpi_speech_gpio.gif|450px|RPi3 control GPIO by speech recogination]]
== Open source ==
<syntaxhighlight lang="bash">
apt-get install rpi-update
apt-get install git-core
rpi-update

-> Connect your USB microphone (or camera+mic) and
-> reboot the RPi at this point

vi /etc/modprobe.d/alsa-base.conf

# change as follows:
# Comment this line
# options snd-usb-audio index=-2
# and add the following:
options snd-usb-audio index=0

-> close the file and reload alsa:

alsa force-reload

wget http://sourceforge.net/projects/cmusphinx/files/sphinxbase/\
0.8/sphinxbase-0.8.tar.gz/download
mv download sphinxbase-0.8.tar.gz
wget http://sourceforge.net/projects/cmusphinx/files/\
pocketsphinx/0.8/pocketsphinx-0.8.tar.gz/download
mv download pocketsphinx-0.8.tar.gz
tar -xzvf sphinxbase-0.8.tar.gz
tar -xzvf pocketsphinx-0.8.tar.gz

apt-get install bison
apt-get install libasound2-dev

cd sphinxbase-0.8
./configure --enable-fixed
make
make install

cd ../pocketsphinx-0.8/
./configure
make
sudo make install
</syntaxhighlight>

== GPIO MAP ==
pi@raspberrypi:~/projects/rpi/speech $ gpio readall
+-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| | | 3.3v | | | 1 || 2 | | | 5v | | |
| 2 | 8 | SDA.1 | IN | 1 | 3 || 4 | | | 5V | | |
| 3 | 9 | SCL.1 | IN | 1 | 5 || 6 | | | 0v | | |
| 4 | 7 | GPIO. 7 | IN | 1 | 7 || 8 | 0 | IN | TxD | 15 | 14 |
| | | 0v | | | 9 || 10 | 1 | IN | RxD | 16 | 15 |
| 17 | 0 | GPIO. 0 | IN | 0 | 11 || 12 | <span style="color:#FF0000">0</span> | OUT | GPIO. 1 | 1 | 18 |
| 27 | 2 | GPIO. 2 | IN | 0 | 13 || 14 | | | 0v | | |
| 22 | 3 | GPIO. 3 | IN | 0 | 15 || 16 | <span style="color:#FF0000">0</span> | OUT | GPIO. 4 | 4 | 23 |
| | | 3.3v | | | 17 || 18 | <span style="color:#FF0000">0</span> | OUT | GPIO. 5 | 5 | 24 |
| 10 | 12 | MOSI | IN | 0 | 19 || 20 | | | 0v | | |
| 9 | 13 | MISO | IN | 0 | 21 || 22 | <span style="color:#FF0000">0</span> | OUT | GPIO. 6 | 6 | 25 |
| 11 | 14 | SCLK | IN | 0 | 23 || 24 | 1 | IN | CE0 | 10 | 8 |
| | | 0v | | | 25 || 26 | 1 | IN | CE1 | 11 | 7 |
| 0 | 30 | SDA.0 | IN | 1 | 27 || 28 | 1 | IN | SCL.0 | 31 | 1 |
| 5 | 21 | GPIO.21 | IN | 1 | 29 || 30 | | | 0v | | |
| 6 | 22 | GPIO.22 | IN | 1 | 31 || 32 | 0 | IN | GPIO.26 | 26 | 12 |
| 13 | 23 | GPIO.23 | IN | 0 | 33 || 34 | | | 0v | | |
| 19 | 24 | GPIO.24 | IN | 0 | 35 || 36 | 0 | IN | GPIO.27 | 27 | 16 |
| 26 | 25 | GPIO.25 | IN | 0 | 37 || 38 | 0 | IN | GPIO.28 | 28 | 20 |
| | | 0v | | | 39 || 40 | 0 | IN | GPIO.29 | 29 | 21 |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+

== GPIO Adapter (using GPIO 12, 16, 18 and 22)==
<syntaxhighlight lang="c">
#include <stdio.h>
#include <string.h>
int main(int argc, char *argv[])
{
char tmp[125];
system("gpio mode 1 out");
system("gpio mode 4 out");
system("gpio mode 5 out");
system("gpio mode 6 out");

while(1)
{
scanf("%s",&tmp);
if(tmp != "\n")
{
if(!strcmp(tmp,"TOMMY"))
system("gpio write 1 1");
else
system("gpio write 1 0");

if(!strcmp(tmp,"MOLLY"))
system("gpio write 4 1");
else
system("gpio write 4 0");

if(!strcmp(tmp,"DAISY"))
system("gpio write 5 1");
else
system("gpio write 5 0");

if(!strcmp(tmp,"ANNIE"))
system("gpio write 6 1");
else
system("gpio write 6 0");

if(!strcmp(tmp,"OKAY"))
{
system("gpio write 1 1");
system("gpio write 4 1");
system("gpio write 5 1");
system("gpio write 6 1");
}
}
}
return 0;
}

</syntaxhighlight>

== GPIO MAP (says, OKAY) ==
pi@raspberrypi:~/projects/rpi/speech $ gpio readall
+-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| | | 3.3v | | | 1 || 2 | | | 5v | | |
| 2 | 8 | SDA.1 | IN | 1 | 3 || 4 | | | 5V | | |
| 3 | 9 | SCL.1 | IN | 1 | 5 || 6 | | | 0v | | |
| 4 | 7 | GPIO. 7 | IN | 1 | 7 || 8 | 0 | IN | TxD | 15 | 14 |
| | | 0v | | | 9 || 10 | <span style="color:#FF0000">1</span> | IN | RxD | 16 | 15 |
| 17 | 0 | GPIO. 0 | IN | 0 | 11 || 12 | <span style="color:#FF0000">1</span> | OUT | GPIO. 1 | 1 | 18 |
| 27 | 2 | GPIO. 2 | IN | 0 | 13 || 14 | | | 0v | | |
| 22 | 3 | GPIO. 3 | IN | 0 | 15 || 16 | <span style="color:#FF0000">1</span> | OUT | GPIO. 4 | 4 | 23 |
| | | 3.3v | | | 17 || 18 | <span style="color:#FF0000">1</span> | OUT | GPIO. 5 | 5 | 24 |
| 10 | 12 | MOSI | IN | 0 | 19 || 20 | | | 0v | | |
| 9 | 13 | MISO | IN | 0 | 21 || 22 | 1 | OUT | GPIO. 6 | 6 | 25 |
| 11 | 14 | SCLK | IN | 0 | 23 || 24 | 1 | IN | CE0 | 10 | 8 |
| | | 0v | | | 25 || 26 | 1 | IN | CE1 | 11 | 7 |
| 0 | 30 | SDA.0 | IN | 1 | 27 || 28 | 1 | IN | SCL.0 | 31 | 1 |
| 5 | 21 | GPIO.21 | IN | 1 | 29 || 30 | | | 0v | | |
| 6 | 22 | GPIO.22 | IN | 1 | 31 || 32 | 0 | IN | GPIO.26 | 26 | 12 |
| 13 | 23 | GPIO.23 | IN | 0 | 33 || 34 | | | 0v | | |
| 19 | 24 | GPIO.24 | IN | 0 | 35 || 36 | 0 | IN | GPIO.27 | 27 | 16 |
| 26 | 25 | GPIO.25 | IN | 0 | 37 || 38 | 0 | IN | GPIO.28 | 28 | 20 |
| | | 0v | | | 39 || 40 | 0 | IN | GPIO.29 | 29 | 21 |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+

== Shell example ==
* pi@raspberrypi:~/project/rpi/speech $ pocketsphinx_continuous -lm 7610.lm -dict 7610.dic -inmic yes | ./adapter

== Reference ==
* [https://wolfpaulus.com/journal/embedded/raspberrypi2-sr/ Raspberry Pi 2 – Speech Recognition on device]
* [https://pypi.python.org/pypi/SpeechRecognition/3.2.0 SpeechRecognition 3.2.0]
* [http://www.speech.cs.cmu.edu/tools/lmtool-new.html Sphinx Knowledge Base Tool]

[[Category:Projects]]

Application - Monitor GPIO interrupt in userspace

2026-08-23T10:01:17Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Watching a '''GPIO interrupt from userspace''' on a Raspberry Pi with a small GLib program, rather than polling the pin.

== Monitor GPIO 4 interrupt ==
=== watch-button-glib.cpp ===
<syntaxhighlight lang="c">
#include <glib.h>
#include <fcntl.h>
#include <iostream>
using namespace std;
#define buf_sz 10
static int onButtonEvent(GIOChannel *channel, GIOCondition condition, gpointer user_data)
{
static char buf[buf_sz];
cerr << "onButtonEvent" <<endl;
GError *error = 0;
gsize bytes_read = 0;
g_io_channel_seek_position(channel, 0, G_SEEK_SET, 0);
GIOStatus rc = g_io_channel_read_chars(channel, buf, buf_sz - 1, &bytes_read, &error);
cerr << "rc:" << rc << " data:" << buf <<endl;
return 1;
}

int main(int argc, char** argv)
{
GMainLoop* loop = g_main_loop_new(0,0);
int fd = open("/sys/class/gpio/gpio4/value", O_RDONLY | O_NONBLOCK);
GIOChannel* channel = g_io_channel_unix_new(fd);
GIOCondition cond = GIOCondition( G_IO_PRI);
guint id = g_io_add_watch(channel, cond, onButtonEvent, 0);

g_main_loop_run(loop);
}

</syntaxhighlight>

=== Makefile ===
<pre>
watch-button-glib: watch-button-glib.cpp Makefile
g++ watch-button-glib.cpp -o watch-button-glib -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -lglib-2.0
</pre>

[[Category:Projects]]

Application - MX35LFxGE4AB, SPI NAND Flash

2026-08-23T10:01:16Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Reading and writing a '''MX35LFxGE4AB''' SPI NAND flash from a Raspberry Pi, which needed an extra transfer function added to libbcm2835.

[[File:rpi2_with_spi_nand_flash.jpg|thumb|200px|RPi2 with SPI NAND Flash(MX35LFxGE4AB)]]

== HW connection ==
<pre>
PRi2 -- MX35LFxGE4AB
VCC -- VCC(3.3V)
VCC -- HOLD(3.3V)
GPIO19(MOSI) -- SI
GPIO21(MISO) -- SO
GPIO23(CLK) -- SCLK
GPIO24(CS0) -- CS
Gnd -- Gnd
Gnd -- WP
</pre>
[[File:read_devid_timing.jpg|thumb|200px|MX35LFxGE4AB read device ID timing]]
== Timing ==
[[File:MX35LFxGE4AB_cmd.jpg]]
== Hack libbcm2835 ==
*Add bcm2835_spi_transfernb_adv() in bcm2835.c
<syntaxhighlight lang="c">
/* Writes an number of bytes to SPI and read an number of bytes from SPI*/
void bcm2835_spi_transfernb_adv(char* tbuf, char* rbuf, uint32_t tx_len, uint32_t rx_len)
{
volatile uint32_t* paddr = bcm2835_spi0 + BCM2835_SPI0_CS/4;
volatile uint32_t* fifo = bcm2835_spi0 + BCM2835_SPI0_FIFO/4;
uint32_t TXCnt=0;
uint32_t RXCnt=0;

/* This is Polled transfer as per section 10.6.1
// BUG ALERT: what happens if we get interupted in this section, and someone else
// accesses a different peripheral?
*/

/* Clear TX and RX fifos */
bcm2835_peri_set_bits(paddr, BCM2835_SPI0_CS_CLEAR, BCM2835_SPI0_CS_CLEAR);

/* Set TA = 1 */
bcm2835_peri_set_bits(paddr, BCM2835_SPI0_CS_TA, BCM2835_SPI0_CS_TA);

/* Use the FIFO's to reduce the interbyte times */

/* TX fifo not full, so add some more bytes */
while(TXCnt < len)
while((BCM2835_SPI0_CS_TXD & bcm2835_peri_read(paddr)))
{
bcm2835_peri_write_nb(fifo, tbuf[TXCnt]);
TXCnt++;
}

/* read dummy */
while(RXCnt < tx_len)
while((BCM2835_SPI0_CS_RXD & bcm2835_peri_read(paddr)))
{
rbuf[RXCnt] = bcm2835_peri_read_nb(fifo);
RXCnt++;
}
RXCnt = 0;

/* Rx fifo not empty, so get the next received bytes */
while((BCM2835_SPI0_CS_RXD & bcm2835_peri_read(paddr)))
{
rbuf[RXCnt] = bcm2835_peri_read_nb(fifo);
RXCnt++;
}
/* Wait for DONE to be set */
while (!(bcm2835_peri_read_nb(paddr) & BCM2835_SPI0_CS_DONE))
;

/* Set TA = 0, and also set the barrier */
bcm2835_peri_set_bits(paddr, 0, BCM2835_SPI0_CS_TA);
}

</syntaxhighlight>

== Example code ==
<syntaxhighlight lang="c">
#include <bcm2835.h>
#include <stdio.h>

int main(int argc, char **argv)
{
int i, tx_len=2, rx_len=2;
if (!bcm2835_init())
return 1;

bcm2835_spi_begin();
bcm2835_spi_setBitOrder(BCM2835_SPI_BIT_ORDER_MSBFIRST); // The default
bcm2835_spi_setDataMode(BCM2835_SPI_MODE0); // The default
bcm2835_spi_setClockDivider(BCM2835_SPI_CLOCK_DIVIDER_512); // The default
bcm2835_spi_chipSelect(BCM2835_SPI_CS0); // The default
bcm2835_spi_setChipSelectPolarity(BCM2835_SPI_CS0, LOW); // the default

// Send a byte to the slave and simultaneously read a byte back from the slave
// If you tie MISO to MOSI, you should read back what was sent
usleep(500);
uint8_t tx_data[]={0x9f, 0x44};
static uint8_t rx_data[10]={0};
bcm2835_spi_transfernb_adv(tx_data,rx_data, tx_len, rx_len);

for(i=0;i<rx_len;i++)
printf("Read from SPI: 0x%.2X \n", rx_data[i]);

bcm2835_spi_end();
bcm2835_close();
return 0;
}

</syntaxhighlight>

[[Category:Projects]]

Application - MPR121, capacitive touch sensor controller

2026-08-23T10:01:16Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Reading twelve touch electrodes from an '''MPR121''' over I2C on an STM32F4, including the interrupt path and the library changes it needed.

[[File:Mpr121_leds.gif|thumb|400px|STM32F4+MPR121+LEDs]]

== Library pinouts ==
<pre>
PINS PACK 1 PINS PACK 2 PINS PACK 3 PINS PACK 4
I2Cx SCL SDA SCL SDA SCL SDA SCL SDA
I2C1 PB6 PB7 PB8 PB9 PB6 PB9
I2C2 PB10 PB11 PF1 PF0 PH4 PH5
I2C3 PA8 PC9 PH7 PH8
I2C4 PD12 PD13 PF1 PF0 PF14 PF15 PH11 PH12
</pre>

== HW connection ==
<pre>
STM32F4 -- MPR121
VCC -- VCC(3.3V)
GND -- GND
IRQ -- IRQ(selected)
PB7 -- SDA
PB8 -- SCL
</pre>

== I²C Slave Address Pin Selects ==
* Connect to VSS, VDD, SDA, SCL to choose address 0x5A, 0x5B, 0x5C, 0x5D respectively
* Default was connected to VSS (0x5A)

== Timing ==
*I2C reg read, 0x5D = 0x24 (Default)
[[File:Mpr121_read.jpg| MPR121 - Read reg]]
* IRQ, negative edge interrupt
[[File:Mpr121_irq.jpg| MPR121 - Read reg]]

== library hacking ==
* The API HAL_I2C_Master_Transmit() always generate stop bit
<pre>
/* Generate Stop */
//hi2c->Instance->CR1 |= I2C_CR1_STOP;
</pre>
*Control stop bit and start bit in main function
<pre>
I2cHandle.Instance->CR1 &= ~I2C_CR1_STOP;
I2cHandle.Instance->CR1 |= I2C_CR1_START;
</pre>
* The API HAL_I2C_Master_Receive() wait for busy flag until timeout
<pre>
#if 0
/* Wait until BUSY flag is reset */
if(I2C_WaitOnFlagUntilTimeout(hi2c, I2C_FLAG_BUSY, SET, I2C_TIMEOUT_BUSY_FLAG) != HAL_OK)
{
return HAL_BUSY;
}
#endif
</pre>

== mpr121 read/write API ==
<syntaxhighlight lang="c">
uint8_t mpr121Read(uint8_t reg)
{
uint8_t data;

if(HAL_I2C_Master_Transmit(&I2cHandle,(uint16_t)I2C_ADDRESS<<1 , &reg, 1, 10000) != HAL_OK) {
//Todo
}

I2cHandle.Instance->CR1 &= ~I2C_CR1_STOP;
I2cHandle.Instance->CR1 |= I2C_CR1_START;

/* Receive multiple byte */
if(HAL_I2C_Master_Receive(&I2cHandle, (uint16_t)I2C_ADDRESS<<1, data, 1, 10000) != HAL_OK) {
//Todo
}
return data;
}

void mpr121Write(uint8_t register_address, uint8_t data) {
uint8_t d[2];

/* Format array to send */
d[0] = register_address;
d[1] = data;

/* Try to transmit via I2C */
if (HAL_I2C_Master_Transmit(&I2cHandle,(uint16_t)I2C_ADDRESS<<1, (uint8_t *)d, 2, 1000) != HAL_OK) {
Error_Handler();
}
I2cHandle.Instance->CR1 |= I2C_CR1_STOP;
}
</syntaxhighlight>

== mpr121 interrupt API ==
<syntaxhighlight lang="c">
Note that, the IRQ would be triggered in both pressed and released!!

void EXTI3_IRQHandler(void)
{
uint16_t touchstatus=0;
touchstatus = mpr121Read(0x01) << 8;
touchstatus |= mpr121Read(0x00);

if(touchstatus & 0x0001)
BSP_LED_On(LED4);
else
BSP_LED_Off(LED4);

if(touchstatus & 0x0002)
BSP_LED_On(LED5);
else
BSP_LED_Off(LED5);

if(touchstatus & 0x0004)
BSP_LED_On(LED6);
else
BSP_LED_Off(LED6);

EXTI->PR = 0x0008; //clear interrupt flag for EXTI3
GPIOE->ODR |= 0x0100; //added to show the execution of IRQ function
GPIOE->ODR &= 0x0100; //end of execution, about 300ns later
}
</syntaxhighlight>

== Reference ==
* [http://www.robot-electronics.co.uk/i2c-tutorial Using the I2C Bus]
* [http://stm32f4-discovery.com/2015/07/hal-library-16-i2c-for-stm32fxxx-devices/ HAL Library 16- I2C for STM32Fxxx devices]

[[Category:Projects]]

Application - LPC1768, SPI communication

2026-08-23T10:01:15Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Talking to an NXP '''LPC1768''' from a Raspberry Pi over SPI using the bcm2835 library.

[[File:PRi_SPI_LPC1768.jpg|border|350px|SPI communication between RPi and LPC1768]]
== Hardware ==
[[File:GPIOs.png|thumb|RPi GPIO]]
[[File:LPC1768_pinout.png|thumb|NXP LPC1768 pinout]]
[[File:spi_timing.png|thumb|SPI timing]]
<pre width=100>
RPi2 NXP LPC1768
MOSI(GPIO10) -- MOSI(p5)
MISO(GPIO09) -- MISO(p6)
SCLK(GPIO11) -- SCLK(p7)
CE0(GPIO08) -- (p8)
</pre>

== Software ==
* RPi using libbcm2835
** gcc -o spi spi.c -lbcm2835
** unknown why BCM2835_SPI_MODE1 is more stable??
<syntaxhighlight lang="c">
#include <bcm2835.h>
#include <stdio.h>

int main(int argc, char **argv)
{
if (!bcm2835_init())
return 1;

bcm2835_spi_begin();
bcm2835_spi_setBitOrder(BCM2835_SPI_BIT_ORDER_MSBFIRST); // The default
bcm2835_spi_setDataMode(BCM2835_SPI_MODE1); // The default
bcm2835_spi_setClockDivider(BCM2835_SPI_CLOCK_DIVIDER_65536); // The default
bcm2835_spi_chipSelect(BCM2835_SPI_CS0); // The default
bcm2835_spi_setChipSelectPolarity(BCM2835_SPI_CS0, LOW); // the default

// Send a byte to the slave and simultaneously read a byte back from the slave
// If you tie MISO to MOSI, you should read back what was sent
uint8_t data = bcm2835_spi_transfer(0x12);
printf("Read from SPI: %02X\n", data);

bcm2835_spi_end();
bcm2835_close();
return 0;
}

</syntaxhighlight>

*NXP LPC1768

<syntaxhighlight lang="c">
#include "mbed.h"

SPISlave device(p5, p6, p7, p8); // mosi, miso, sclk, ssel

Serial pc(USBTX, USBRX);
int main() {
device.reply(0x00); // Prime SPI with first reply
while(1) {
if(device.receive()) {
int v = device.read(); // Read byte from master
device.reply(v); // Make this the next reply
pc.printf("reply: %02x\n", v);
}
}
}
</syntaxhighlight>

== Reference ==
* [https://developer.mbed.org/questions/1331/How-to-Delay-SPI-Slave-to-Master-Respons/ How to Delay SPI Slave to Master Response?]

* [http://www.mathworks.com/help/supportpkg/raspberrypiio/ug/use-the-spi-interface-on-the-raspberry-pi-hardware.html Use the Raspberry Pi SPI Interface to Connect to a Device]

* [http://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus wiki, Serial Peripheral Interface Bus]

* [http://www.airspayce.com/mikem/bcm2835/group__spi.html#gad623657d9513faa89d22ae1dc87eec38 libbcm2835]

* [http://www.petervis.com/Raspberry_PI/SPI_Seria Raspberry Pi SPI]

[[Category:Projects]]

Application - Keyes 38KHz IR Infrared Transmitter Module

2026-08-23T10:01:15Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Sending and receiving 38 kHz infrared with a '''Keyes IR module''', using LIRC on a Raspberry Pi and the IRremote library on Arduino.

== install lirc ==
sudo apt-get install lirc liblircclient-dev

== /etc/modules ==
<pre>
add following two lines:

lirc_dev
lirc_rpi gpio_in_pin=18
</pre>

==/etc/lirc/hardware.conf ==
<pre>
# Arguments which will be used when launching lircd
LIRCD_ARGS="--uinput"

# Don't start lircmd even if there seems to be a good config file
# START_LIRCMD=false

# Don't start irexec, even if a good config file seems to exist.
# START_IREXEC=false

# Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="default"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/lirc0"
MODULES="lirc_rpi"

# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""
</pre>

== Keyes IR Transmitter/Receiver with Arduino ==
[[File:Keyes ir trans recv.jpg|thumb| Keyes, IR Transmitter/receiver package]]
[[File:Keyes ir receiver.jpg|thumb| Keyes, IR receiver]]
[[File:VS1838B.jpg|thumb| Keyes, IR receiver/VS1838B]]
<pre>
型号:VS1838B
1．简介：
VS1838B 内含高速高灵敏度 PIN 光电二极管和低功耗、高增益前
置放大 IC,采用环氧树脂封装外加外屏蔽抗干挠设计，该产品已
经通过
REACH
和
SGS
认证属于环保产品，
在红外遥控系统中作为
接收器使用。
2.特性：
●环氧树脂封装外加外屏蔽抗干挠设计；
●宽工作电压，2.7-5.5V；
●低功耗；宽角度及长距离接收；
●抗干挠能力强，能抵挡环境干挠；
●输出匹配 TTL、CMOS 电平，低电平有效。
3．应用:
■视听器材(音箱,电视,DVD,卫星接收机等)；
■家庭电器(空调,电风扇,灯饰等)；
■其它红外线遥控产品。
</pre>

== Reference ==
* [http://www.lirc.org/ LIRC, Linux Infrared Remote Control]
* [http://ozzmaker.com/2013/10/24/how-to-control-the-gpio-on-a-raspberry-pi-with-an-ir-remote/ How to Control the GPIO on a Raspberry Pi with an IR Remote]

[[Category:Projects]]

Application - HC-SR04, Ultrasonic ranging module

2026-08-23T10:01:15Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Measuring distance with an '''HC-SR04''' ultrasonic module on a Raspberry Pi, using the bcm2835 GPIO library.

[[File:IMAG1074.jpg|thumb|200px|RPi2 with ultrasonic ranging module(HC-SR04)]]

== HW connection ==
<pre>
PRi2 -- HC-SR04
VCC -- VCC(5V)
Trig -- GPIO17(output)
Echo -- GPIO27(input)
Gnd -- Gnd
</pre>

== Timing ==
[[File:hc-sr04-timing.png|thumb|700px|HC-SR04 timing diagram]]
<pre>
The Timing diagram is shown below. You only need to
supply a short 10uS
pulse to the trigger input to start the ranging, an
d then the module will send out
an 8 cycle burst of ultrasound at 40 kHz and raise
its echo. The Echo is a
distance object that is pulse width and the range i
n proportion .You can
calculate the range through the time interval betwe
en sending trigger signal and
receiving echo signal. Formula: uS / 58 = centimete
rs or uS / 148 =inch; or: the
range = high level time * velocity (340M/S) / 2; we
suggest to use over 60ms
measurement cycle, in order to prevent trigger sign
al to the echo signal.

</pre>

== GPIO control with gpio library ==
* Install gpio library
<syntaxhighlight lang="bash">
wget http://www.airspayce.com/mikem/bcm2835/bcm2835-1.25.tar.gz
gunzip /bcm2835-1.25.tar.gz
tar xvf bcm2835-1.25.tar
cd bcm2835-1.25
./configure
make
sudo make install
</syntaxhighlight>
*For RPi2, should modify the bcm2835.h before compile
** #define BCM2835_PERI_BASE 0x3F000000

*C example
<syntaxhighlight lang="c">
#include <bcm2835.h>
#include <stdio.h>
#include <time.h>
#include <sys/time.h>

//GPIO 17
#define TRIG_PIN RPI_V2_GPIO_P1_11

//GPIO 27
#define ECHO_PIN RPI_V2_GPIO_P1_13

int main()
{
uint8_t value;
struct timeval t1, t2;
double d1,d2;
double dist=0;

if(!bcm2835_init())
{
perror("Init error!");
return 1;
}

bcm2835_gpio_fsel(TRIG_PIN, BCM2835_GPIO_FSEL_OUTP);

bcm2835_delayMicroseconds(3000);

bcm2835_gpio_write(TRIG_PIN, HIGH);

bcm2835_delayMicroseconds(10);

bcm2835_gpio_write(TRIG_PIN, LOW);

//wait first echo and timestamps to t1
while( (value=bcm2835_gpio_lev(ECHO_PIN)) == 0)
;
gettimeofday(&t1, NULL);

//wait second echo and timestamps to t1
while( (value=bcm2835_gpio_lev(ECHO_PIN)) == 1)
;
gettimeofday(&t2, NULL);

d1 = t1.tv_sec + (t1.tv_usec/1000000.0);
d2 = t2.tv_sec + (t2.tv_usec/1000000.0);

dist = (d2-d1) * 17000 ;

printf("Distance: %5.2f cm\n", dist);
return 0;
}
</syntaxhighlight>

* Compile with gpio library
**gcc -o sensor sensor.c -lbcm2835

== Debugfs for GPIO ==
*Show gpio status
<syntaxhighlight lang="bash">
sudo mount -t debugfs debug /home/pi/debugfs/
sudo cat /home/pi/debugfs/gpio
---->
GPIOs 0-53, platform/3f200000.gpio, pinctrl-bcm2835:
gpio-9 (sysfs ) in lo
gpio-10 (sysfs ) out lo
gpio-35 (led1 ) in hi
gpio-47 (led0 ) out lo
</syntaxhighlight>

*For specific GPIO pin
<pre>
#!/bin/bash
#set gpio 17 as trig pin
echo 17 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio17/direction

#set gpio 27 as echo pin
echo 27 > /sys/class/gpio/export
echo in > /sys/class/gpio/gpio27/direction
</pre>

== Testing ==
[[File:ranging_test.jpg|Ranging testing using C]]
[[File:Ranging test data.png|thumb|300px|Ranging data from C]]
<pre>
- Test with C code -
# 5cm 10cm 25cm
1 6 8.12 24.14
2 6.07 8.21 23.1
3 6.12 8.5 23.07
4 6.07 8.18 23.02
5 5.97 8.58 24.16
6 7.21 8.52 22.97
7 6.07 8.06 23.1
8 6.39 8.6 22.99
9 6.1 8.58 23.12
10 6.1 8.43 23

Average 6.21 8.378 23.267
</pre>
[[File:Python hc-sr04.jpg|thumb|300px|Ranging data from Python]]
<pre>
- Test with Python code -
# 5cm 10cm 25cm
1 6.6 10.3 24.6
2 6.7 10.2 24.5
3 6.6 10.1 24.5
4 6.6 10 24.6
5 6.6 10.1 24.5
6 6.7 10.1 24.6
7 6.6 9.7 24.6
8 6.6 9.6 24.6
9 6.6 9.6 24.6
10 6.6 9.7 24.6

Average 6.62 9.94 24.57
</pre>

== Reference ==
[http://www.bytecreation.com/blog/2013/10/13/raspberry-pi-ultrasonic-sensor-hc-sr04 Using an Ultrasonic Sensor (HC-SR04) on a Raspberry Pi with Python]

[http://coldnew.github.io/blog/2013/06/27_1aced.html gpio c library]

[http://www.micropik.com/PDF/HCSR04.pdf datasheet]

[[Category:Projects]]

Application - BMA250, triaxial acceleration sensor

2026-08-23T10:01:14Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Example code for reading the '''BMA250''' triaxial acceleration sensor.

== Example code ==
<syntaxhighlight lang="c">
#include "Wire.h"
byte range=0x03;
float divi=16;
int addr = 0x18;
void setup()
{
Serial.begin(115200);
Wire.begin();
Wire.beginTransmission(addr); // address of the accelerometer

// Start I2C Transmission
Wire.beginTransmission(addr);
// Select range selection register
Wire.write(0x0F);
// Set range +/- 2g
Wire.write(0x03);
// Stop I2C Transmission
Wire.endTransmission();

// Start I2C Transmission
Wire.beginTransmission(addr);
// Select bandwidth register
Wire.write(0x10);
// Set bandwidth 7.81 Hz
Wire.write(0x10);
// Stop I2C Transmission
Wire.endTransmission();

// low pass filter
Wire.beginTransmission(addr);
Wire.write(0x20); //register address
Wire.write(0x05); //can be set at"0x05""0x04"......"0x01""0x00", refer to Datashhet on wiki
Wire.endTransmission();

}

void AccelerometerInit()
{
unsigned int data[0];
// Start I2C Transmission
Wire.beginTransmission(addr);
// Select Data Registers (0x02 − 0x07)
Wire.write(0x02);
// Stop I2C Transmission
Wire.endTransmission();

// Request 6 bytes
Wire.requestFrom(addr, 6);
// Read the six bytes
// xAccl lsb, xAccl msb, yAccl lsb, yAccl msb, zAccl lsb, zAccl msb

while(!Wire.available())
;

data[0] = Wire.read();
data[1] = Wire.read();
data[2] = Wire.read();
data[3] = Wire.read();
data[4] = Wire.read();
data[5] = Wire.read();

delay(10);

// Convert the data to 10 bits
float xAccl = ((data[1] * 256.0) + (data[0] & 0xC0)) / 64;
if (xAccl > 511)
{
xAccl -= 1024;
}
float yAccl = ((data[3] * 256.0) + (data[2] & 0xC0)) / 64;
if (yAccl > 511)
{
yAccl -= 1024;
}
float zAccl = ((data[5] * 256.0) + (data[4] & 0xC0)) / 64;
if (zAccl > 511)
{
zAccl -= 1024;
}

// Output data to the serial monitor
Serial.print("X-Axis :");
Serial.print(xAccl);
Serial.print(" ");
Serial.print("Y-Axis :");
Serial.print(yAccl);
Serial.print(" ");
Serial.print("Z-Axis :");
Serial.println(zAccl);
}

void loop()
{
/*
switch(range) //change the data dealing method based on the range u've set
{
case 0x00:divi=16; break;
case 0x01:divi=8; break;
case 0x02:divi=4; break;
case 0x03:divi=2; break;
default: Serial.println("range setting is Wrong,range:from 0to 3.Please check!");while(1);
}
*/
AccelerometerInit();
}
</syntaxhighlight>

[[Category:Projects]]

Application - AWS IoT

2026-08-23T10:01:14Z

Tommy：Consistency: syntax highlighting for code, File: prefix

Setting up the '''AWS IoT''' command line and Lambda tooling, and registering things from a Raspberry Pi.

== Setup your AWS CLI installation ==
** sudo apt install awscli
* Go to IAM service to get the Access keys
** aws configure
<pre>
$ aws configure
AWS Access Key ID [None]: AKIAIOSFODNN7EXAMPLE
AWS Secret Access Key [None]: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Default region name [None]: us-west-2
Default output format [None]: json
</pre>
* AWS development package - boto3
** pip install tornado nose
** pip install boto3
* Get AWS FreeRTOS
** https://github.com/aws/amazon-freertos
* Create IoT thing
** vim freertos/tools/aws_config_quick_start/configure.json
** cd freertos/tools/aws_config_quick_start
** python SetupAWS.py setup
* Toolchain version(5.2.0 is better)
<pre>
$ xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc (crosstool-NG crosstool-ng-1.22.0-80-g6c4433a) 5.2.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
</pre>
* Build
<syntaxhighlight lang="bash">
cd freertos
mkdir build
cmake -DVENDOR=espressif -DBOARD=esp32_wrover_kit -DCOMPILER=xtensa-esp32 -DCMAKE_BUILD_TYPE=Debug -S . -B build
cd build
make all -j4
</syntaxhighlight>

== lambda ==
* <span style="color:red">Note that if you use Alexa-hosted skill for lambda, you may not configure the permission for AWSIoTFullAccess</span>
*Function example(node.js)
<pre>

var AWS = require('aws-sdk');

var iotdata = new AWS.IotData({endpoint:"a1q79ntmqqqssy-ats.iot.us-west-2.amazonaws.com"});

exports.handler = function(event, context, callback) {

console.log("found iotdata",iotdata);

var params = {
topic: 'iotdemo/topic/2',
payload: 'on',
qos: 0
};

iotdata.publish(params, function(err, data){
if(err){
console.log("Error occured : ",err);
}
else{
console.log("success.....");
}
});

callback();
};
</pre>
* Trigger
** Allow Alexa skill kit with ARN
* IAM Permission
** AWSIoTFullAccess

* Reference
https://docs.aws.amazon.com/zh_tw/freertos/latest/userguide/getting_started_espressif.html

[[Category:Projects]]

ASTAR

2026-08-23T10:01:13Z

Tommy：Consistency: syntax highlighting for code, File: prefix

'''ASTAR''' was an internal IP media player project on the RealTek RTD1073. This page is its release log, 2010-2011.

''The repository referenced below (<code>192.168.50.188</code>) no longer exists. These notes are the surviving record of the project.''

==Project info==
Customer: internal<br>
Product: IP media player<br>
Chip: RealTek RTD1073<br>

==SVN info==
[[File:ASTAR_REPO_20110527_03.png]]<br>
'''webcam'''
svn+ssh://192.168.50.188/svnroot/ASTAR.old/branches/webcam
'''BT'''
svn+ssh://192.168.50.188/svnroot/ASTAR.old/branches/bt
'''radiotime'''
svn+ssh://192.168.50.188/svnroot/ASTAR/branches/radiotime
'''libopera'''
svn+ssh://192.168.50.188/svnroot/ASTAR/branches/libopera
'''android'''
svn+ssh://192.168.50.188/svnroot/ASTAR/branches/android
[[File:ASTAR_OS_20110527.gif]]<br>
'''OS'''
svn+ssh://192.168.50.188/svnroot/NTV350OS/branches/ASTAR-OS

==Release info==
=== ASTAR OS ===
==== ASTAR-OS-0.0.0.1 ====
svn+ssh://192.168.50.188/svnroot/NTV350OS/tags/ASTAR-OS-0.0.0.1
===== release date =====
2010/12/01
===== release note =====
* Enable UVCVIDEO driver
* porting ffmpeg & ffserver
* stopwebcam utility for kill ffmpeg & ffserver processes
* optional compile for webcam
==== ASTAR-OS-0.0.0.2 ====
svn+ssh://192.168.50.188/svnroot/NTV350OS/tags/ASTAR-OS-0.0.0.2
===== release date =====
2010/12/08
===== release note =====
* Add recording script
==== ASTAR-OS-0.0.0.3 ====
svn+ssh://192.168.50.188/svnroot/NTV350OS/tags/ASTAR-OS-0.0.0.3
===== release date =====
2010/12/15
===== release note =====
* Release with ASTAR-NTV350-0.0.0.1
==== ASTAR-OS-1.0.1.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350OS/tags/ASTAR-OS-1.0.1.0
===== release date =====
2011/05/27
===== release note =====
* Add USB audio modules
* Add VoIP.conf for ffserver[....thinking remove]
* Add S54VoIP
* Add soundcore, audio and sound modules
* Porting pjsip under /usr/local/VoIP/ ''(using mipsel-linux-gcc 3.4.4)''
* Fix pjsip buffer issue by double the frames
* improve usb storage search rule(would confuse with usb camera before)

=== ASTAR AP ===
==== Trunk ====
===== ASTAR-1.0.0.1 =====
svn+ssh://192.168.50.188/svnroot/ASTAR/tags/ASTAR-1.0.0.1
====== release date ======
2011/05/27
====== release note ======
* Enable Opera browser
* Enable webcam application
* VoIP inside(not presented in UI!)
* Add thread for remote control over IP
* Modify logo,string,image to independent to customer
* Build install.img with ASTAR-OS-1.0.1.0

==== Branch ====
===== ASTAR-NTV350-0.0.0.1 =====
svn+ssh://192.168.50.188/svnroot/ASTAR/tags/ASTAR-NTV350-0.0.0.1
====== release date ======
2010/12/15
====== release note ======
* Using ASTAR-OS-0.0.0.3
* Add Webcam application
* Add RadioTime service
* Add Video Repeat function

=== ASTAR AP.old ===
==== Trunk ====
===== ASTAR-AP-0.0.0.1 =====
svn+ssh://192.168.50.188/svnroot/ASTAR.old/tags/ASTAR-AP-0.0.0.1
====== release date ======
2010/12/02

====== release note ======
* Using ASTAR-OS-0.0.0.1
* Internet media/webcam
* available webcam
** Logitech C200 (046d:0802)
* unavailable webcam
** IPEVO P2V (1778:0204)

==== Branch ====
===== ASTAR-webcam-0.0.0.1 =====
svn+ssh://192.168.50.188/svnroot/ASTAR.old/tags/ASTAR-webcam-0.0.0.1
====== release date ======
2010/12/08
====== release note ======
* Using ASTAR-OS-0.0.0.2
* Add recording function
* Add RSS script functions for usb plugin check
* Add RSS script functions for webcam plugin check

[[Category:Boards and SoCs]]

如何用正確的方法來寫出品質好的軟體的75條體會

2026-08-23T09:57:19Z

Tommy：Add a lead sentence

'''七十五條軟體開發心得''' — 一份關於原始碼管理、缺陷追蹤、測試流程與團隊協作的檢查清單。

==如何用正確的方法來寫出品質好的軟體的75條體會==
===1. 你們的專案組使用源代碼管理工具了麼？===
應該用。VSS、CVS、PVCS、ClearCase、CCC/Harvest、FireFly都可以。我的選擇是VSS。

===2. 你們的專案組使用缺陷管理系統了麼？===
應該用。ClearQuest太複雜，我的推薦是BugZilla。

===3. 你們的測試組還在用Word寫測試用例麼？===
不要用Word寫測試用例（Test Case）。應該用一個專門的系統，可以是Test Manager，也可以是自己開發一個ASP.NET的小網站。主要目的是Track和Browse。

===4. 你們的專案組有沒有建立一個門戶網站？===
要有一個門戶網站，用來放Contact Info、Baselined Schedule、News等等。推薦Sharepoint Portal Server 2003來實現，15分鐘就搞定。買不起SPS 2003可以用WSS (Windows Sharepoint Service)。

===5. 你們的項目組用了你能買到最好的工具麼？===
應該用儘量好的工具來工作。比如，應該用VS.NET而不是Notepad來寫C#。用Notepad寫程式多半只是一種炫耀。但也要考慮到經費，所以說是「你能買到最好的」。

===6. 你們的程式員工作在安靜的環境裏麼？===
需要安靜環境。這點極端重要，而且要保證每個人的空間大於一定面積。

===7. 你們的員工每個人都有一部電話麼？===
需要每人一部電話。而且電話最好是帶留言功能的。當然，上這麼一套帶留言電話系統開銷不小。不過至少每人一部電話要有，千萬別搞得經常有人站起來喊：「某某某電話」。《人件》裏面就強烈譴責這種做法。

===8. 你們每個人都知道出了問題應該找誰麼？===
應該知道。任何一個Feature至少都應該有一個Owner，當然，Owner可以繼續Dispatch給其他人。

===9. 你遇到過有人說「我以為…」麼？===
要消滅「我以為」。Never assume anything。

===10. 你們的項目組中所有的人都坐在一起麼？===
需要。我反對Virtual Team，也反對Dev在美國、Test在中國這種開發方式。能坐在一起就最好坐在一起，好處多得不得了。

===11. 你們的進度表是否反映最新開發進展情況？ ===
應該反映。但是，應該用Baseline的方法來管理進度表：維護一份穩定的Schedule，再維護一份最新更改。Baseline的方法也應該用於其他的Spec。Baseline是變更管理裏面的一個重要手段。

===12. 你們的工作量是先由每個人自己估算的麼？===
應該讓每個人自己估算。要從下而上估算工作量，而不是從上往下分派。除非有其他原因，比如政治任務工期固定等。

===13. 你們的開發人員從專案一開始就加班麼？===
不要這樣。不要一開始就搞疲勞戰。從專案一開始就加班，只能說明專案進度不合理。當然，一些對日軟體外包必須天天加班，那屬於剝削的範疇。

===14. 你們的專案計畫中Buffer Time是加在每個小任務後面的麼？===
不要。Buffer Time加在每個小任務後面，很容易輕易的就被消耗掉。Buffer Time要整段的加在一個Milestone或者checkpoint前面。

===15. 值得再多花一些時間，從95%做到100%好===
值得，非常值得。尤其當專案後期人困馬乏的時候，要堅持。這會給產品帶來質的區別。

===16. 登記新缺陷時，是否寫清了重現步驟？===
要。這屬於Dev和Test之間的溝通手段。面對面溝通需要，詳細填寫Repro Steps也需要。

===17. 寫新代碼前會把已知缺陷解決麼？===
要。每個人的缺陷不能超過10個或15個，否則必須先解決老的bug才能繼續寫新代碼。

===18. 你們對缺陷的輕重緩急有事先的約定麼？===
必須有定義。Severity要分1、2、3，約定好：藍屏和Data Lost算Sev 1，Function Error算Sev 2，介面上的算Sev 3。但這種約定可以根據產品品質現狀適當進行調整。

===19. 你們對意見不一的缺陷有三國會議麼？===
必須要有。要有一個明確的決策過程。這類似於CCB (Change Control Board)的概念。

===20. 所有的缺陷都是由登記的人最後關閉的麼？===
Bug應該由Opener關閉。Dev不能私自關閉Bug。

===21. 你們的程式師厭惡修改老的代碼麼？===
厭惡是正常的。解決方法是組織Code Review，單獨留出時間來。XP也是一個方法。

===22. 你們項目組有Team Morale Activity麼？===
每個月都要搞一次，吃飯、唱歌、Outing、打球、開卡丁車等等，一定要有。不要剩這些錢。

===23. 你們項目組有自己的Logo麼？===
要有自己的Logo。至少應該有自己的Codename。

===24. 你們的員工有印有公司Logo的T-Shirt麼？===
要有。能增強歸屬感。當然，T-Shirt要做的好看一些，最好用80支的棉來做。別沒穿幾次就破破爛爛的。

===25. 總經理至少每月參加次專案組會議===
要的。要讓team member覺得高層關注這個項目。

===26. 你們是給每個Dev開一個分支麼？===
反對。Branch的管理以及Merge的工作量太大，而且容易出錯。

===27. 有人長期不Check-In代碼麼？===
不可以。對大部分項目來說，最多兩三天就應該Check-In。

===28. 在Check-In代碼時都填寫註釋了麼？===
要寫的，至少一兩句話，比如「解決了Bug No.225」。如果往高處拔，這也算做「配置審計」的一部分。

===29. 有沒有設定每天Check-In的最後期限？===
要的，要明確Check-In Deadline。否則會Build Break。

===30. 你們能把所有源碼一下子編譯成安裝檔嗎？ ===
要的。這是每日編譯（Daily Build）的基礎。而且必須要能夠做成自動的。

===31. 你們的項目組做每日編譯麼？===
當然要做。有三樣東西是軟體專案/產品開發必備的：1. bug management; 2. source control; 3. daily build。

===32. 你們公司有沒有積累一個項目風險列表？===
要。Risk Inventory。否則，下個專案開始的時候，又只能拍腦袋分析Risk了。

===33. 設計越簡單越好===
越簡單越好。設計時候多一句話，將來可能就帶來無窮無盡的煩惱。應該從一開始就勇敢的砍。這叫scope management。

===34. 儘量利用現有的產品、技術、代碼===
千萬別什麼東西都自己Coding。BizTalk和Sharepoint就是最好的例子，有這兩個作為基礎，可以把起點提高很多。或者可以儘量多用現成的Control之類的。或者儘量用XML，而不是自己去Parse一個文字檔案；儘量用RegExp，而不是自己從頭操作字串，等等等等。這就是「軟體複用」的體現。

===35. 你們會隔一段時間就停下來夯實代碼麼？===
要。最好一個月左右一次。傳言去年年初Windows組在Stevb的命令下停過一個月增強安全。Btw，「夯」這個字念「hang」，第一聲。

===36. 你們的項目組每個人都寫Daily Report麼？===
要寫。五分鐘就夠了，寫10句話左右，告訴自己小組的人今天我幹了什麼。一則為了溝通，二則鞭策自己（要是遊手好閒一天，自己都會不好意思寫的）。

===37. 你們的專案經理會發出Weekly Report麼？===
要。也是為了溝通。內容包括目前進度，可能的風險，品質狀況，各種工作的進展等。

===38. 你們專案組是否至少每週全體開會一次？===
要。一定要開會。程式師討厭開會，但每個禮拜開會時間加起來至少應該有4小時。包括team meeting, spec review meeting, bug triage meeting。千萬別大家悶頭寫code。

===39. 你們專案組的會議、討論都有記錄麼？===
會前發meeting request和agenda，會中有人負責主持和記錄，會後有人負責發meeting minutes，這都是effective meeting的要點。而且，每個會議都要形成agreements和action items。

===40. 其他部門知道你們專案組在幹什麼麼？===
要發一些Newsflash給整個大組織。Show your team’s value。否則，當你坐在電梯裏面，其他部門的人問：「你們在幹嘛」，你回答「ABC項目」的時候，別人全然不知，那種感覺不太好。

===41. 通過Email進行所有正式溝通===
Email的好處是免得抵賴。但也要避免矯枉過正，最好的方法是先用電話和當面說，然後Email來確認。

===42. 為項目組建立多個Mailing Group===
如果在AD+Exchange裏面，就建Distribution List。比如，我會建ABC Project Core Team，ABC Project Dev Team，ABC Project All Testers，ABC Project Extended Team等等。這樣發起Email來方便，而且能讓該收到email的人都收到、不該收到不被騷擾。

===43. 每個人都知道哪裡可以找到全部的文檔麼？===
應該每個人都知道。這叫做知識管理（Knowledge Management）。最方便的就是把文檔放在一個集中的File Share，更好的方法是用Sharepoint。

===44. 你做決定、做變化時，告訴大家原因了麼？===
要告訴大家原因。Empower team member的手段之一是提供足夠的information，這是MSF一開篇的幾個原則之一。的確如此，tell me why是人之常情，tell me why了才能有understanding。中國人做事喜歡搞限制，限制資訊，似乎能夠看到某一份檔的人就是有身份的人。大錯特錯。權威、權力，不在於是不是能access information/data，而在於是不是掌握資源。

===45. Stay agile and expect change===
要這樣。需求一定會變的，已經寫好的代碼一定會被要求修改的。做好心理準備，對change不要抗拒，而是expect change。

===46. 你們有沒有專職的軟體測試人員？===
要有專職測試。如果人手不夠，可以peer test，交換了測試。千萬別自己測試自己的。

===47. 你們的測試有一份總的計畫來規定做什麼和怎麼做麼？===
這就是Test Plan。要不要做性能測試？要不要做Usability測試？什麼時候開始測試性能？測試通過的標準是什麼？用什麼手段，自動的還是手動的？這些問題需要用Test Plan來回答。

===48. 你是先寫Test Case然後再測試的麼？===
應該如此。應該先設計再編程、先test case再測試。當然，事情是靈活的。我有時候在做第一遍測試的同時補上test case。至於先test case再開發，我不喜歡，因為不習慣，太麻煩，至於別人推薦，那試試看也無妨。

===49. 你是否會為各種輸入組合創建測試用例？===
不要，不要搞邊界條件組合。當心組合爆炸。有很多test case工具能夠自動生成各種邊界條件的組合——但要想清楚，你是否有時間去運行那麼多test case。

===50. 你們的程式師能看到測試用例麼？===
要。讓Dev看到Test Case吧。我們都是為了同一個目的走到一起來的：提高品質。

===51. 你們是否隨便抓一些人來做易用性測試？===
要這麼做。自己看自己寫的程式介面，怎麼看都是順眼的。這叫做審美疲勞——臭的看久了也就不臭了，不方便的永久了也就習慣了。

===52. 你對自動測試的期望正確麼？===
別期望太高。依我看，除了性能測試以外，還是暫時先忘掉「自動測試」吧，忘掉WinRunner和LoadRunner吧。對於國內的軟體測試的現狀來說，只能「矯枉必須過正」了。

===53. 你們的性能測試是等所有功能都開發完才做的麼？===
不能這樣。性能測試不能被歸到所謂的「系統測試」階段。早測早改正，早死早升天。

===54. 你注意到測試中的殺蟲劑效應了麼？===
蟲子有抗藥性，Bug也有。發現的新Bug越來越少是正常的。這時候，最好大家交換一下測試的area，或者用用看其他工具和手法，就又會發現一些新bug了。

===55. 你們專案組中有人能說出產品的當前整體品質情況麼？===
要有。當老闆問起這個產品目前品質如何，Test Lead/Manager應該負責回答。

===56. 你們有單元測試麼？===
單元測試要有的。不過沒有單元測試也不是不可以，我做過沒有單元測試的專案，也做成功了——可能是僥倖，可能是大家都是熟手的關係。還是那句話，軟體工程是非常實踐、非常工程、非常靈活的一套方法，某些方法在某些情況下會比另一些方法好，反之亦然。

===57. 你們的程式師是寫完代碼就扔過牆的麼？===
大忌。寫好一塊程式以後，即便不做單元測試，也應該自己先跑一跑。雖然有了專門的測試人員，做開發的人也不可以一點測試都不做。微軟還有Test Release Document的說法，程式太爛的話，測試有權踢回去。

===58. 你們的程式中所有的函數都有輸入檢查麼？===
不要。雖然說做輸入檢查是write secure code的要點，但不要做太多的輸入檢查，有些內部函數之間的參數傳遞就不必檢查輸入了，省點功夫。同樣的道理，未必要給所有的函數都寫註釋。寫一部分主要的就夠了。

===59. 產品有統一的錯誤處理機制和報錯介面麼？===
要有。最好能有統一的error message，然後每個error message都帶一個error number。這樣，用戶可以自己根據error number到user manual裏面去看看錯誤的具體描述和可能原因，就像SQL Server的錯誤那樣。同樣，ASP.NET也要有統一的Exception處理。可以參考有關的Application Block。

===60. 你們有統一的代碼書寫規範麼？===
要有。Code Convention很多，搞一份來發給大家就可以了。當然，要是有FxCop這種工具來檢查代碼就更好了。

===61. 你們的每個人都瞭解項目的商業意義麼？===
要。這是Vision的意思。別把專案只當成工作。有時候要想著自己是在為中國某某行業的資訊化作先驅者，或者時不時的告訴team member，這個項目能夠為某某某國家部門每年節省多少多少百萬的納稅人的錢，這樣就有動力了。平凡的事情也是可以有個崇高的目標的。

===62. 產品各部分的介面和操作習慣一致麼？===
要這樣。要讓用戶覺得整個程式好像是一個人寫出來的那樣。

===63. 有可以作為宣傳亮點的Cool Feature麼？===
要。這是增強團隊凝聚力、信心的。而且，「一俊遮百醜」，有亮點就可以掩蓋一些問題。這樣，對於客戶來說，會感覺產品從品質角度來說還是acceptable的。或者說，cool feature或者說亮點可以作為品質問題的一個事後彌補措施。

===64. 盡可能縮短產品的啟動時間===
要這樣。軟體啟動時間（Start-Up time）是客戶對性能好壞的第一印象。

===65. 不要過於注重內在品質而忽視了第一眼的外在印象===
程式師容易犯這個錯誤：太看重性能、穩定性、存儲效率，但忽視了外在感受。而高層經理、客戶正相反。這兩方面要兼顧，協調這些是PM的工作。

===66. 你們根據詳細產品功能說明書做開發麼？===
要這樣。要有設計才能開發，這是必須的。設計文檔，應該說清楚這個產品會怎麼運行，應該採取一些講故事的方法。設計的時候千萬別鑽細節，別鑽到資料庫、代碼等具體實現裏面去，那些是後面的事情，一步步來不能著急。

===67. 開始開發和測試之前每個人都仔細審閱功能設計麼？===
要做。Function Spec review是用來統一思想的。而且，review過以後形成了一致意見，將來再也沒有人可以說「你看，當初我就是反對這麼設計的，現在吃苦頭了吧」

===68. 所有人都始終想著The Whole Image麼？===
要這樣。專案裏面每個人雖然都只是在製造一片葉子，但每個人都應該知道自己在製造的那片葉子所在的樹是怎麼樣子的。我反對軟體藍領，反對過分的把軟體製造看成流水線、車間。參見第61條。

===69. Dev工作的劃分是單純縱向或橫向的麼？===
不能單純的根據功能模組分，或者單純根據表現層、中間層、資料庫層分。我推薦這麼做：首先根據功能模組分，然後每個「層」都有一個Owner來Review所有人的設計和代碼，保證consistency。

===70. 你們的程式師寫程式設計說明文檔麼？===
要。不過我聽說微軟的程式師1999年以前也不寫。所以說，寫不寫也不是絕對的，偷懶有時候也是可以的。參見第56條。

===71. 你在招人面試時讓他寫一段程式麼？===
要的。我最喜歡讓人做字串和鏈表一類的題目。這種題目有很多迴圈、判斷、指針、遞迴等，既不偏向過於考演算法，也不偏向過於考特定的API。

===72. 你們有沒有技術交流講座？===
要的。每一兩個禮拜搞一次內部的Tech Talk或者Chalk Talk吧。讓組員之間分享技術心得，這筆花錢送到外面去培訓划算。

===73. 你們的程式師都能專注於一件事情麼？===
要讓程式師專注一件事。例如說，一個部門有兩個專案和10個人，一種方法是讓10個人同時參加兩個項目，每個項目上每個人都花50%時間；另一種方法是5個人去項目A，5個人去項目B，每個人都100%在某一個項目上。我一定選後面一種。這個道理很多人都懂，但很多領導實踐起來就把屬下當成可以任意拆分的資源了。

===74. 你們的程式師會誇大完成某項工作所需要的時間麼？
會的，這是常見的，尤其會在項目後期誇大做某個change所需要的時間，以次來抵制change。解決的方法是坐下來慢慢磨，磨掉程式師的逆反心理，一起分析，並把估算時間的顆粒度變小。

===75. 儘量不要用Virtual Heads===
最好不要用Virtual Heads。Virtual heads意味著resource is not secure，shared resource會降低resource的工作效率，容易增加出錯的機會，會讓一心二用的人沒有太多時間去review spec、review design。一個dedicated的人，要強過兩個只能投入50%時間和精力的人。我是吃過虧的：7個part time的tester，發現的Bug和幹的活，加起來還不如兩個full-time的。參見第73條。73條是針對程式師的，75條是針對Resource Manager的。

[[Category:Software Engineering]]

U-boot

2026-08-23T09:57:19Z

Tommy：Add a lead sentence

Building '''U-Boot''' for the Raspberry Pi, preparing an SD card with it, and booting a kernel from USB.

== source ==
* <nowiki>git clone https://github.com/gonzoua/u-boot-pi.git</nowiki>
* <nowiki>svn co file:///var/svn/rpi_uboot/trunk</nowiki>

== Toolchain ==
* <nowiki>git clone https://github.com/raspberrypi/tools</nowiki>

== Build ==
* export ARCH=arm
* export CROSS_COMPILE=arm-linux-gnueabi-
* make rpi_b

== prepare SD card for your u-boot ==
* ./tools/mkimage/imagetool-uncompressed.py u-boot-pi/u-boot.bin
* cp kernel.img RASPBIAN_BOOT_PARTATION

== boot to kernel from USB ==
* prepare your zImage in usb disk, and you should try another usb port if not working while load to ram
* U-Boot> usb start
** use usb sub-system to check avaliable dev and part
*** U-Boot> usb dev
*** U-Boot> usb part {dev}
** use ext2load to check where your zImage existed or not
*** U-Boot> ext2ls usb {dev}:{part}
* U-Boot> ext2load usb {dev}:{part} ${loadaddr} zImage
* U-Boot> bootz ${loadaddr}

== Reference ==
* [http://elinux.org/RPi_U-Boot RPi U-Boot]

[[Category:Software and Tools]]

Tiny6410

2026-08-23T09:57:19Z

Tommy：Add a lead sentence

'''Tiny6410''' was an internal ARM11 evaluation board project on the Samsung S3C6410. This page is the release log for its camera work.

''The repository referenced below (<code>192.168.50.188</code>) no longer exists. These notes are the surviving record of the project.''

==Project info==
Customer: internal<br>
Product: ARM11 evalution board<br>
Chip: Samsung S3C6410 / 533MHZ<br>

==SVN info==
[[image:Tiny6410_REPO_20110926_01.png]]<br>
'''camera'''
svn+ssh://192.168.50.188/svnroot/tiny6410/branches/camera

==Release info==
=== camera ===
==== tiny6410-camera-0.0.0.1 ====
svn+ssh://192.168.50.188/svnroot/NTV350OS/tags/
===== release date =====

''Not recorded. The repository this page refers to is gone, so this cannot be recovered.''

===== release note =====
* disable preview thread
* add 176x144 size for USB Camera C200
* combine V4l2 process into picture thread
* store image in temp file and re-open to get image data for Camera.apk
(please create tommy_test.jpg in root for r/w, and need to optimize this process)

[[Category:Boards and SoCs]]

Teensy 4.0

2026-08-23T09:57:18Z

Tommy：Add a lead sentence

'''Teensy 4.0''' is a 600 MHz Cortex-M7 board built on the NXP i.MX RT1062. These notes cover the pinout, memory map, and building for it with Teensyduino, PlatformIO and the NXP MCUXpresso SDK.

== Technical Specifications ==
* ARM Cortex-M7 at 600 MHz
* 1024K RAM (512K is tightly coupled)
* 2048K Flash (64K reserved for recovery & EEPROM emulation)
* 2 USB ports, both 480 MBit/sec
* 3 CAN Bus (1 with CAN FD)
* 2 I2S Digital Audio
* 1 S/PDIF Digital Audio
* 1 SDIO (4 bit) native SD
* 3 SPI, all with 16 word FIFO
* 3 I2C, all with 4 byte FIFO
* 7 Serial, all with 4 byte FIFO
* 32 general purpose DMA channels
* 31 PWM pins
* 40 digital pins, all interrrupt capable
* 14 analog pins, 2 ADCs on chip
* Cryptographic Acceleration
* Random Number Generator
* RTC for date/time
* Programmable FlexIO
* Pixel Processing Pipeline
* Peripheral cross triggering
* Power On/Off management
* FPU support
<pre>
Teensy 4.0's Cortex-M7 processor includes a floating point unit (FPU) which supports both 64 bit "double" and 32 bit "float".
With M4's FPU on Teensy 3.5 & 36, and also Atmel SAMD51 chips, only 32 bit float is hardware accelerated.
Any use of double, double functions like log(), sin(), cos() means slow software implemented math.
Teensy 4.0 executes all of these with FPU hardware.
</pre>

== PIN assignment ==
[[File:Card10a_rev1_web.png|500px|top side]]
[[File:Card10b_rev1_web.png|500px|back side]]

== Schematic ==
[[File:Schematic40.png|500px|Teensy 4.0 shematic]]
[[File:Schematic41.png|500px|Teensy 4.1 shematic]]

== Memory Map ==
* Teensy 4.0 has 1 Mbyte of RAM and 2 Mbyte of Flash memory. The RAM is divided into 2 physically separate banks.
[[File:Teensy4_memory.png|Teensy 4.0 Memory Layout]]

== Teensyduino IDE installation ==
* Download & Extract Arduino
* Install udev Rules
** The udev rule file gives non-root users permission to use the Teensy devices (serial, HID, etc). More Linux tips below.

sudo cp 49-teensy.rules /etc/udev/rules.d/

== PlatformIO ==
* Install VSCode(Visual Studio Code)
** Install PlatformIO from extensions

== MCUXpresso IDE ==

Teensy 4.0 carries an NXP i.MX RT1062, so NXP's own tools can be used to study
the chip even though Teensy itself is normally programmed through Teensyduino or
PlatformIO. MCUXpresso IDE is NXP's free Eclipse-based IDE for i.MX RT, LPC and
Kinetis parts; it bundles the GNU Arm toolchain and supports the SDK examples
built in the NXP SDK section below.

* Download from NXP (account required)
* Import an SDK as a zip, then '''Import SDK example''' to build the EVK projects
* Debug over the EVK's on-board CMSIS-DAP; Teensy 4.0 has no SWD header brought
out, so the IDE is useful for reference builds rather than flashing a Teensy

== MCUXpresso Config Tools ==

A standalone GUI for generating the start-up code for an i.MX RT part. It has
three sub-tools:

* '''Pins''' - assign peripheral signals to package pins, flags conflicts
* '''Clocks''' - configure the PLLs and clock tree, shows the resulting frequencies
* '''Peripherals''' - configure a peripheral and emit its init struct

Output is written back into the project as pin_mux.c, clock_config.c and
peripherals.c. It can run standalone or from inside MCUXpresso IDE.

== MCUXpresso SDK ==

The per-board driver and example package. Build one for a given board with the
SDK Builder at https://mcuxpresso.nxp.com and choose the toolchain when
generating it - the armgcc variant is what the NXP SDK section below builds.

Contents:
* '''devices/''' - CMSIS headers, start-up code and peripheral drivers (fsl_*.c)
* '''boards/''' - board-specific examples, one directory per example
* '''middleware/''' - optional stacks such as USB, FatFs and lwIP

For Teensy 4.0 the relevant board is EVK-MIMXRT1060, whose MIMXRT1062 is the same
part as the one on the Teensy.

== NXP SDK ==
<pre>
export ARMGCC_DIR=$TOOLCHAIN_PATH
cd SDK_2.7.0_EVK-MIMXRT1060/boards/evkmimxrt1060/driver_examples/gpio/led_output/armgcc
chmod 777 build_all.sh
./build_all.sh
arm-none-eabi-objcopy -O ihex flexspi_nor_release/igpio_led_output.elf flexspi_nor_release/igpio_led_output.hex
teensy_loader_cli -v -w --mcu=imxrt1062 flexspi_nor_release/igpio_led_output.hex
</pre>

* For led_output example, need to modify gpio mapping in board.h (refer to schematic)
<pre>
/*! @brief The USER_LED used for board */
#define LOGIC_LED_ON (0U)
#define LOGIC_LED_OFF (1U)
#ifndef BOARD_USER_LED_GPIO
#define BOARD_USER_LED_GPIO GPIO2 <----- modify
#endif
#ifndef BOARD_USER_LED_GPIO_PIN
#define BOARD_USER_LED_GPIO_PIN (3U) <----- modify
#endif
</pre>

== Upload binary standalone ==
* teensy_loader_cli -mmcu=imxrt1062 -w evkmimxrt1060_freertos_hello_teensy.hex -v

== SPI Timing ==
* CS_OFF around 40 ns
[[File:Teensy_4_spi_cs.jpg|400px|SPI CS_OFF width]]

* SPI CLK in 16M
[[File:Teensy_4_spi_16M.jpg|400px|SPI CLK in 16M]]

* Sampling rate evaluation
** CS_ON+CS_OFF around 1.46 us
** For 32 Ch in 16M SPI_CLK, the sampling rate for each channel would be:
*** (1000000/1.46*32)/1000=21.4KS

== SDIO 4 bit ==
[[File:Teensy_4_sdio_4_bit.JPG|500px|SDIO4 bit mode]]
* Format SD before running
* Change pin define in code
** SD.begin(BUILTIN_SDCARD)
<pre>
/*
SD card datalogger

This example shows how to log data from three analog sensors
to an SD card using the SD library.

The circuit:
* analog sensors on analog ins 0, 1, and 2
* SD card attached to SPI bus as follows:
** MOSI - pin 11, pin 7 on Teensy with audio board
** MISO - pin 12
** CLK - pin 13, pin 14 on Teensy with audio board
** CS - pin 4, pin 10 on Teensy with audio board

created 24 Nov 2010
modified 9 Apr 2012
by Tom Igoe

This example code is in the public domain.

*/

#include <SD.h>
#include <SPI.h>

// On the Ethernet Shield, CS is pin 4. Note that even if it's not
// used as the CS pin, the hardware CS pin (10 on most Arduino boards,
// 53 on the Mega) must be left as an output or the SD library
// functions will not work.

// change this to match your SD shield or module;
// Arduino Ethernet shield: pin 4
// Adafruit SD shields and modules: pin 10
// Sparkfun SD shield: pin 8
// Teensy audio board: pin 10
// Teensy 3.5 & 3.6 on-board: BUILTIN_SDCARD
// Wiz820+SD board: pin 4
// Teensy 2.0: pin 0
// Teensy++ 2.0: pin 20
//const int chipSelect = 36;

void setup()
{
//UNCOMMENT THESE TWO LINES FOR TEENSY AUDIO BOARD:
//SPI.setMOSI(37); // Audio shield has MOSI on pin 7
//SPI.setSCK(36); // Audio shield has SCK on pin 14

// Open serial communications and wait for port to open:
Serial.begin(9600);
while (!Serial) {
; // wait for serial port to connect. Needed for Leonardo only
}

Serial.print("Initializing SD card...");

// see if the card is present and can be initialized:
if (!SD.begin(BUILTIN_SDCARD)) {
Serial.println("Card failed, or not present");
// don't do anything more:
return;
}
Serial.println("card initialized.");
}

void loop()
{
// make a string for assembling the data to log:
String dataString = "";

// read three sensors and append to the string:
for (int analogPin = 0; analogPin < 3; analogPin++) {
int sensor = analogRead(analogPin);
dataString += String(sensor);
if (analogPin < 2) {
dataString += ",";
}
}

// open the file. note that only one file can be open at a time,
// so you have to close this one before opening another.
File dataFile = SD.open("datalog.txt", FILE_WRITE);

// if the file is available, write to it:
if (dataFile) {
dataFile.println(dataString);
dataFile.close();
// print to the serial port too:
Serial.println(dataString);
}
// if the file isn't open, pop up an error:
else {
Serial.println("error opening datalog.txt");
}
}
</pre>

== Related projects ==
* [[Application - ADS1256]]

[[Category:Boards and SoCs]]

TI, CC3220SF

2026-08-23T09:57:18Z

Tommy：Add a lead sentence

The TI '''CC3220SF''' is a Wi-Fi MCU. These notes cover installing the SimpleLink SDK, building the FreeRTOS example, and programming the board.

[[File:Ti-cc3220sf-launchxl-large.jpg|CC3220SF LAUNCHXL]]
== Introduction ==
This guide is intended to assist users in the initial setup and demonstration of running their first sample application. The guide explains how to install the SimpleLinkTM CC3220TM SDK and lists the various other tools required to get started with the first application
== Prerequisites ==

The user is expected to have the following:

* SimpleLink CC3220 LaunchPad
* At least one of the following IDE supported by the SimpleLink CC3220 SDK:
** CCS 7.3.0
** IAR for ARM 8.11.1 or higher
* GNU ARM Embedded Toolchain, 6-2017-q1
* FreeRTOSv9.0.0 (Optional)
** The SimpleLink CC3220 SDK does not deliver FreeRTOS sources.
** If the User wants to use FreeRTOS with the SDK, the user is expected to download the FreeRTOS sources from www.freertos.org
*TI Uniflash

== SDK - Download and Installation ==
* You can also download the SimpleLink CC3220 SDK from TI Resource Explorer or the software product page on TI’s website.

== Compile ==
* Running CCS
* Import the existing example from SDK

== a:freeRTOS online example ==
[[File:ConnectToAWSIoT.jpg|thumb|Connect To AWS IoT]]
* Go to https://console.aws.amazon.com/iot/home?region=us-east-1#/software/freertos
* Software configurations
** Hardware platform - CC3220SF-LAUNCHXL
** Libraries & Demo projects
*** MQTT
*** Greengrass Discovery
*** OTA Updates
*** thing shadow
**** Edit AmazonFreeRTOS/demos/common/include/aws_clientcredential.h for
***** MQTT Broker endpoint,
***** clientcredentialIOT_THING_NAME
***** clientcredentialWIFI_SSID
***** clientcredentialWIFI_PASSWORD
** Give it a name and Create

== Program FW ==
[[File:UserFile.jpg|thumb|User File]]
[[File:ImageCreator.jpg|thumb| Generate Image]]
* Running UniFlash
* User Files
** Add file
*** simplelink_cc32xx_sdk_1_02_02_00\tools\cc32xx_tools\certificate-playground\dummy-root-ca-cert
*** Select "Failsafe"
** Select MCU Image
*** YOUR_APP.bin
*** Select "Failsafe", "Secure" and "Public Write"
*** Private key
**** simplelink_cc32xx_sdk_1_02_02_00\tools\cc32xx_tools\certificate-playground\dummy-root-ca-cert-key
*** Select "dummy-root-ca-cert" from "Certificate File name" dropdown menu
* Service Packed
** simplelink_cc32xx_sdk_1_02_02_00\tools\cc32xx_tools\servicepack-cc3x20\sp_3.2.0.0_2.0.0.0_2.2.0.4.bin
* Trusted Root Certificate Catalog
** Source File
*** simplelink_cc32xx_sdk_1_02_02_00\tools\cc32xx_tools\certificate-playground\certcatalogPlayGround20160911.lst
** Signature Source File
*** simplelink_cc32xx_sdk_1_02_02_00\tools\cc32xx_tools\certificate-playground\certcatalogPlayGround20160911.lst.signed.bin
* Generate Image
** Save Image as .sli and program later, or
** Program Image(Create & Program)

== Console ==
* /dev/ttyACM0, 115200 8N1

== Reference ==
* [http://dev.ti.com/tirex/#/ TI Resource Explorer]
* [https://console.aws.amazon.com/iot/home?region=us-east-1#/software/freertos a:freeRTOS for MCUs]

[[Category:Boards and SoCs]]

Software version

2026-08-23T09:57:17Z

Tommy：Add a lead sentence

'''Software versioning''' is the process of assigning identifiers to distinct releases of a piece of software. This article surveys the schemes in use.

==Schemes==
A variety of version numbering schemes have been created to keep track of different versions of a piece of software. The ubiquity (the ability to be everywhere at the same time) of computers has also led to these schemes being used in contexts outside computing.

===Sequence-based identifiers===
[[Image:VersionNumbers.svg|right|Version number sequence|1000x500px]]
In sequence-based software versioning schemes, each [[software release]] is assigned a unique identifier that consists of one or more sequences of numbers or letters. This is the extent of the commonality, however: schemes vary widely in areas such as the quantity of sequences, the attribution of meaning to individual sequences, and the means of incrementing the sequences.

====Change significance====
In some schemes, sequence-based identifiers are used to convey the significance of changes between releases: changes are classified by significance level, and the decision of which sequence to change between releases is based on the significance of the changes from the previous release, whereby the first sequence is changed for the most significant changes, and changes to sequences after the first represent changes of decreasing significance.

For instance, in a scheme that uses a four-sequence identifier, the first sequence may be incremented only when the code is completely rewritten, while a change to the user interface or the documentation may only warrant a change to the fourth sequence.

This practice permits users (or potential adopters) to evaluate how much real-world testing a given software release has undergone. If changes are made between, say, 1.3rc4 and the production release of 1.3, then that release, which asserts that it has had a production-grade level of testing in the real world, in fact contains changes which have not necessarily been tested in the real world ''at all''.{{Clarify|January 2010|date=January 2010}} This approach commonly permits the third level of numbering ("change"), but does not apply this level of rigor to changes in that number: 1.3.1, 1.3.2, 1.3.3, 1.3.4... 1.4b1, etc.{{Clarify|January 2010|date=January 2010}}

In principle, in subsequent releases, the ''major'' number is increased when there are significant jumps in functionality, the ''minor'' number is incremented when only minor features or significant fixes have been added, and the ''revision'' number is incremented when minor bugs are fixed. A typical product might use the numbers 0.9 (for beta software), 0.9.1, 0.9.2, 0.9.3, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.1, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.2, etc. Developers have at times jumped (for example) from version 5.0 to 5.5 to indicate that significant features have been added, but not enough to warrant incrementing the major version number, though this is [[Software_versioning#Separating_sequences|improper]].{{Clarify|January 2010|date=January 2010}}

A different approach is to use the ''major'' and ''minor'' numbers, along with an alphanumeric string denoting the release type, i.e. "alpha", "beta" or "release candidate". A release train using this approach might look like 0.5, 0.6, 0.7, 0.8, 0.9 == 1.0b1, 1.0b2 (with some fixes), 1.0b3 (with more fixes) == 1.0rc1 (which, if it is stable ''enough'') == 1.0. If 1.0rc1 turns out to have bugs which must be fixed, it turns into 1.0rc2, and so on. The important characteristic of this approach is that the first version of a given level (beta, RC, production) ''must be identical'' to the last version of the release below it: you cannot make any changes at all from the last beta to the first RC, or from the last RC to production. If you do, you must roll out another release at that lower level.

However, since version numbers are human-generated, not computer-generated, there is nothing that prevents arbitrary changes that violate such guidelines: for example, the first sequence could be incremented between versions that differ by not even a single line of code, to give the (false) impression that very significant changes were made.

Other schemes impart meaning on individual sequences:
:''<nowiki>major.minor[.build[.revision]]</nowiki>''
or
:''<nowiki>major.minor[.maintenance[.build]]</nowiki>''

Again, in these examples, the definition of what constitutes a "major" as opposed to a "minor" change is entirely arbitrary and up to the author, as is what defines a "build", or how a "revision" differs from a "minor" change.

In most proprietary software, the first released version of a software product has version 1.

====Designating development stage====
Some schemes use a zero in the first sequence to designate [[Software release life cycle#Alpha|alpha]] or [[Software release life cycle#Beta|beta]] status for releases that are not stable enough for general or practical deployment and are intended for testing or internal use only.

It can be used in the third position:
* 0 for alpha (status)
* 1 for beta (status)
* 2 for release candidate
* 3 for (public) release

For instance:
* 1.2.0.1 instead of 1.2-a
* 1.2.1.2 instead of 1.2-b2 (beta with some bug fixes)
* 1.2.2.3 instead of 1.2-rc (release candidate)
* 1.2.3.0 instead of 1.2-r (commercial distribution)
* 1.2.3.5 instead of 1.2-r5 (commercial distribution with many bug fixes)

====Separating sequences====
When printed, the sequences may be separated with characters. The choice of characters and their usage varies by scheme. The following list shows hypothetical examples of separation schemes for the same release (the thirteenth third-level revision to the fourth second-level revision to the second first-level revision):

* A scheme may use the same character between all sequences: 2.4.13, 2/4/13, 2-4-13
* A scheme choice of which sequences to separate may be inconsistent, separating some sequences but not others: 2.413
* A scheme's choice of characters may be inconsistent within the same identifier: 2.4_13

When a period is used to separate sequences, it does ''not'' represent a decimal point, and the sequences do ''not'' have positional significance. An identifier of ''2.5'', for instance, is not "two and a half" or "half way to version three", it is the ''fifth second-level revision of the second first-level revision''.

====Number of sequences====

There is sometimes a fourth, unpublished number which denotes the software build (as used by [[Microsoft]]). [[Adobe Flash]] notably publicly indicates a 4-part version, as in 10.1.53.64. Some companies also include the build date. Version numbers may also include letters and other characters, such as [[Lotus 1-2-3]] Release 1a.

====Incrementing sequences====

There are two schools of thought regarding how numeric version numbers are incremented: Most [[free software]] packages treat numbers as a continuous stream, therefore a free software or open source product may have version numbers 1.7.0, 1.8.0, 1.8.1, 1.9.0, 1.10.0, 1.11.0, 1.11.1, 1.11.2, etc. An example of such a software package is [[MediaWiki]]. However, many programs treat version numbers in another way, generally as decimal numbers, and may have version numbers such as 1.7, 1.8, 1.81, 1.82, 1.9, etc. In software packages using this way of numbering 1.81 is the next minor version after 1.8. Maintenance releases (i.e. bug fixes only) would generally be denoted as 1.81a, 1.81b, etc.

The standard [[GNU]] version numbering scheme is major.minor.revision, but [[emacs]] is notably using another scheme where the major number ("1") was dropped and a "user site" revision was added which is always zero in original emacs packages but increased by distributors.<ref name="advogato"/> Similarly, [[Debian]] package numbers are prefixed with an optional "epoch", which is used to allow the versioning scheme to be changed.<ref>Debian Policy Manual, [http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version 5.6.12 Version]</ref>

====Using negative numbers====
There exist some projects that use negative version numbers. One example is the [[smalleiffel]] compiler which started from -1.0 and counted upwards to 0.0.<ref name="advogato">{{Cite web|url=http://www.advogato.org/article/40.html|title=Advogato: Version numbering madness|accessdate=2009-04-11|date=2000-02-28}}</ref>

====Degree of compatibility====
Some projects use the major version number to indicate incompatible releases. Two examples are Apache APR<ref name="apr">{{Cite web|url=http://apr.apache.org/versioning.html|title=Versioning Numbering Concepts - The Apache Portable Runtime Project|accessdate=2009-04-11}}</ref> and the FarCry CMS.<ref name="farcry">{{Cite web|url=http://blog.daemon.com.au/archives/000276.html|title=Daemonite: The science of version numbering|date=2004-09-14|accessdate=2009-04-11}}</ref>

===Date===
The [[Wine (software)|Wine]] project used a date versioning scheme, which uses the year followed by the month followed by the day of the release; for example, "Wine 20040505". Wine is now on a "standard" release track; the most current stable version (as of [[2010]]) is 1.2. [[Ubuntu Linux]] uses a similar versioning scheme—Ubuntu 10.04, for example, was released April 2010.

When using dates in versioning, for instance, file names, it is common to use the ISO scheme<ref name="ISO Date">{{Cite web|url=http://www.cl.cam.ac.uk/~mgk25/iso-time.html|title=International standard date and time notation|author=Markus Kuhn|accessdate=2009-04-11|date=2004-12-19|publisher=[[University of Cambridge]]}}</ref>: YYYY-MM-DD, as this is easily string sorted to increasing/decreasing order. The hyphens are sometimes omitted.

[[Microsoft Office]] build numbers are actually an encoded date.<ref name="ms">{{Cite web|url=http://www.codinghorror.com/blog/archives/000793.html|title=Coding Horror: What's In a Version Number, Anyway?|date=2007-02-15|accessdate=2009-04-11|author=Jeff Atwood}}</ref>

===Year of release===
Other examples, identifying versions by year ([[Adobe Illustrator]] 88, [[WordPerfect Office]] 2003). Although when a date is used to denote version it is generally for marketing purposes, and an actual version number exists. For example, [[Microsoft Windows 2000 Server]] is internally versioned as Windows NT 5.0 ("NT" being a reference to the original product name).

===Alphanumeric codes=== 
Examples:
* [[Macromedia Flash]] MX
* [[Adobe Photoshop]] CS2

===TeX===
[[TeX]] has an [[idiosyncratic]] version numbering system. Since version 3, updates have been indicated by adding an extra digit at the end, so that the version number [[asymptote|asymptotically]] approaches [[pi|π]]; this is a form of [[Unary numeral system|unary numbering]] – the version number is the number of digits. The current version is 3.1415926. This is a reflection of the fact that TeX is now very stable, and only minor updates are anticipated. TeX developer [[Donald Knuth]] has stated that the "absolutely final change (to be made after my death)" will be to change the version number to π, at which point all remaining bugs will become permanent features.<ref>Donald E. Knuth. [http://www.ntg.nl/maps/05/34.pdf ''The future of TeX and METAFONT''], NTG journal MAPS (1990), 489. Reprinted as chapter 30 of ''Digital Typography'', p. 571.</ref>

In a similar way, the version number of [[METAFONT]] asymptotically approaches [[E (mathematical constant)|e]].

===Apple===
Apple has a formalised version number structure based around the NumVersion struct, which specifies a one- or two-digit major version, a one-digit minor version, a one-digit "bug" (i.e. revision) version, a stage indicator (drawn from the set development/prealpha, alpha, beta and final/release), and a one-byte (i.e. having values in the range 0–255) pre-release version, which is only used at stages prior to final. In writing these version numbers as strings, the convention is to omit any parts after the minor version whose value are zero (with "final" being considered the zero stage), thus writing 1.0.2b12, 1.0.2 (rather than 1.0.2f0), and 1.1 (rather than 1.1.0f0).

===Other schemes===
Some software producers use different schemes to denote releases of their software. For example, the [[Microsoft Windows]] operating system was first labelled with standard numerical version numbers ([[Windows 1.0]] through [[Windows 3.1x|Windows 3.11]]). Later, Microsoft started using separate version names for marketing purposes, first using years ([[Windows 95]] (4.0), [[Windows 98]] (4.10), [[Windows 2000]] (5.0)), then using alphanumeric codes ([[Windows Me]] (4.90), [[Windows XP]] (5.1)), then using brand names ([[Windows Vista]] (6.0)). With the release of [[Windows 7]] it appears that Microsoft has returned to using numerical version numbers, although the official version number for Windows 7 is 6.1<ref>Enter the "ver" command in Windows 7 command prompt</ref>.

The [[Debian]] project uses a major/minor versioning scheme for releases of its operating system, but uses code names from the movie ''[[Toy Story]]'' during development to refer to stable, unstable and testing releases.

[[Category:Software Engineering]]

Seeed + Hackaday, Tiny BLE

2026-08-23T09:57:17Z

Tommy：Add a lead sentence

The '''Tiny BLE''' is a Seeed nRF51822 board. These notes cover its source and measured LED power consumption.

[[File:Tiny_BLE.jpg|300px|HW]]
== Intro ==
<pre>
The Tiny BLE is a Bluetooth Low Energy development board designed with low energy consumption and small size in mind.
It's integrated with current measurement feature to provide real time energy consumption data, which is essential for
developers to optimize software to design long battery life devices. It supports ARM mbed cloud-based IDE with an handy C/C++ SDK
and a large number of open source libraries, which makes prototyping and development extremely easy. Further, to keep it small,
we use modular design to enable it divide into two parts - CMSIS DAP interface part and BLE part.
</pre>
[[File:Tiny_ble.png|300px|HW]]
== LED power consumption ==
[[File:Tiny_ble_RGB_current.jpg|current consumption]]
== Reference ==
[https://github.com/Seeed-Studio/Tiny_BLE Github - Seeed-Studio/Tiny_BLE]

[[Category:Boards and SoCs]]

ST, STM32F4 Discovery

2026-08-23T09:57:16Z

Tommy：Add a lead sentence

The '''STM32F4 Discovery''' is an ST Cortex-M4 board. These notes cover the GNU/ARM toolchain, building and flashing with ST-Link, and debugging with GDB.

[[File:IMAG4572 BURST001.jpg|thumb|200px|Dot matrix + servo + touch sensor]]
== Download the GNU/ARM toolchain ==
* tar -xvjf gcc-arm-none-eabi-4_8-2014q2-20131204-linux.tar.bz2
* export PATH=$PATH:~/gcc-arm-none-eabi-4_8-2014q2/bin
== Download and Build STLINK ==
* sudo apt-get install autoconf pkg-config libusb-1.0 git
* git clone https://github.com/texane/stlink.git
<pre>
cd ~/stlink
./autogen.sh
./configure
make
</pre>
== Download STM32 Libraries and Blinky Example ==
* git clone https://github.com/rowol/stm32_discovery_arm_gcc
== Compile Your Source Code ==
* Edit Makefile
** STLINK=/home/rowol/stlink #Example, change to your location
** STM_COMMON=/home/rowol/stm32_discovery_arm_gcc/STM32F4-DISCOVERY_FW_V1.1.0
** make it
== Program ARM's Flash and Run Code ==
* make burn
or
* st-flash write STM32F4-Discovery.bin 0x08000000

== Using external ST-Link ==
* Remove CN3 jumper
<pre>
ST-Link STM32F4
VCC 3V
SWIO PA13
SWCLK PA14
VDD VDD ( depends on product, could range from 1.8v - 5v )
GND GND
</pre>

== GDB ==
<pre>
In the directory with your source code, I've also add a .gdbinit file which contains:

define reload
kill
monitor jtag_reset
load
end

target extended localhost:4242
load

This will execute whenever you start GDB in the source directory

To start up:

~/stlink/st-util #Start GDB server
arm-none-eabi-gdb main.elf #In a second terminal window, start GDB

continue #Starts code running, or use other GDB commands to
# set breakpoints, etc first...

</pre>

== Related projects ==
* [[Application - MPR121, capacitive touch sensor controller]]
* [[Application - MAX7219, Serially Interfaced, 8-Digit LED Display Drivers (interact with MPR121)]]
* [[Application - MAX7219, Serially Interfaced, 8-Digit LED Display Drivers (scrolling text)]]
* [[application - CS43L22, built-in DAC(audio playback)]]
* [[Application - MG90S, Metal Gear Servo]]
* [[Application - Joystick]]
* [[Application - nRF52, (BLE - UART - STM32F4)]]
* [[Application - MeArm, mini robotic arm]]

== Reference ==
* [https://launchpad.net/gcc-arm-embedded/+download ARM toolchain]
* [http://www.wolinlabs.com/blog/linux.stm32.discovery.gcc.html STM32 Discovery Development On Linux]

* [http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419 STM32F4 Discovery Kit Resource Page]
* [http://www.arm.com/products/processors/cortex-m/cortex-microcontroller-software-interface-standard.php CMSIS - Cortex Microcontroller Software Interface Standard]
* [http://rusefi.com/wiki/index.php?title=Hardware:stm32f4discovery_repair Hardware:stm32f4discovery repair]

[[Category:Boards and SoCs]]

SCCB, Arducam/OVM7251

2026-08-23T09:57:16Z

Tommy：Add a lead sentence

Talking to an '''OVM7251''' camera over SCCB, Omnivision's I2C-like bus, on an Arducam module.

[[File:bp_rpi_ov7251.jpg|400px|bus priate hacking ovm7251]]

== I2C init cmd ==
<pre>
HiZ>m
1. HiZ
2. 1-WIRE
3. UART
4. I2C
5. SPI
6. 2WIRE
7. 3WIRE
8. LCD
x. exit(without change)

(1)>4
Set speed:
1. ~5KHz
2. ~50KHz
3. ~100KHz
4. ~400KHz

(1)>4
Ready
I2C>P
Pull-up resistors ON
Warning: no voltage on Vpullup pin
I2C>W
POWER SUPPLIES ON
I2C>
HiZ>m
1. HiZ
2. 1-WIRE
3. UART
4. I2C
5. SPI
6. 2WIRE
7. 3WIRE
8. LCD
x. exit(without change)

(1)>4
Set speed:
1. ~5KHz
2. ~50KHz
3. ~100KHz
4. ~400KHz

(1)>4
Ready
I2C>P
Pull-up resistors ON
Warning: no voltage on Vpullup pin
I2C>W
POWER SUPPLIES ON
I2C>
</pre>

== SCCB Read/Write ==
<pre>
I2C>[0xc0 0x35 0x02][0xc1 r]
I2C START BIT
WRITE: 0xC0 ACK
WRITE: 0x35 ACK
WRITE: 0x02 ACK
I2C STOP BIT
I2C START BIT
WRITE: 0xC1 ACK
READ: 0x80
NACK
I2C STOP BIT

I2C>[0xc0 0x35 0x02 0xf0]
I2C START BIT
WRITE: 0xC0 ACK
WRITE: 0x35 ACK
WRITE: 0x02 ACK
WRITE: 0xF0 ACK
I2C STOP BIT

I2C>[0xc0 0x35 0x02][0xc1 r]
I2C START BIT
WRITE: 0xC0 ACK
WRITE: 0x35 ACK
WRITE: 0x02 ACK
I2C STOP BIT
I2C START BIT
WRITE: 0xC1 ACK
READ: 0xF0
NACK
I2C STOP BIT

</pre>

[[File:IMG_20201117_171416598.jpg|1200px|SCCB_write_01]]

[[File:IMG_20201117_171508585.jpg|1200px|SCCB_write_02]]

[[Category:Sensors and Modules]]

RoboPeak Mini USB Display

2026-08-23T09:57:16Z

Tommy：Add a lead sentence

The '''RoboPeak Mini USB Display''' is a small USB-attached framebuffer screen. These notes cover building its Linux kernel driver, natively and cross-compiled, and getting X11 output onto it.

[[File:Rpusbdisp01.jpg|thumb|600px|rpusbdisp with RPi2]]
== RoboPeak Mini USB Display ==
# git clone https://github.com/robopeak/rpusbdisp

Drivers and Tools for RoboPeak Mini USB Display Project

Visit RoboPeak Website for details.

== How to Integrate the Driver in the Kernel build operation ==

1) Copy the content of linux-driver folder in your kernel source (ideally in a new folder called robopeak inside the drivers/video folder)
2) Replace the Makefile file by the NewMakefile one
3) Edit the Kconfig file of the drivers/video file and insert the line
* source "drivers/video/robopeak/Kconfig"
after the line
* comment "Frame buffer hardware drivers"
4) Change the .config of your kernel through the menuconfig
* make ARCH=your_architecture your_defconfig menuconfig
5) In the menu "Device Drivers -> Graphic supports -> Support for frame buffer display" a Robopeak USB Display menu appears
6) Set the Robopeak USB Display as module (this selection activates automatically the requested frame buffer option, see Prerequites of How to build the Linux Kernel Driver chapter)
7) Generate your kernel

== How to Build the Linux Kernel Driver ==

Here we only provide you the basic building process. Please refer to the related documents for details.
=== I. Prerequisite ===

As a linux kernel driver, it requires you to provide the target system's kernel header or the full source code to build.

Before building the driver, you may need to config the linux kernel to enable the features required by the driver. Otherwise, the building process will fail.

If you want to use the driver with your current kernel (without recompiling the kernel and replacing it with the current one), please make sure the kernel header, the config and the related build scripts you used is belonged to this version of kernel.

Please make sure the following kernel features have been enabled. (via make menuconfig under your kernel source)

0) framebuffer support (CONFIG_FB=y)

1) deferred io support in framebuffer (CONFIG_FB_DEFERRED_IO=y)

2) fb file operation support

* CONFIG_FB_CFB_FILLRECT=y
* CONFIG_FB_CFB_COPYAREA=y
* CONFIG_FB_CFB_IMAGEBLIT=y
* CONFIG_FB_SYS_FILLRECT=m
* CONFIG_FB_SYS_COPYAREA=m
* CONFIG_FB_SYS_IMAGEBLIT=m
* CONFIG_FB_SYS_FOPS=m
* CONFIG_FB_MODE_HELPERS=y

3) Input event support (Generic input layer support)

You may modify the .config directly to enable these features.

Alternatively, here is a tricky method: Select the Displaylink display driver ( Device Drivers-> Graphics support -> Support for frame buffer devices-> Displaylink USB Framebuffer support) as an external module. By doing so, the above features will be selected by the menuconfiger.

You may need to recompile the kernel if the above configuration changes have been made.
=== II. Native Build - build the kernel driver for the current machine ===

You should have followed the steps described in the prerequisite section already. Here let's assume the location of the Linux kernel header(or source) is ~/workspace/linux-kernel.

Enter the Robopeak USB Displayer linux kernel driver folder (i.e. rpusbdisp/drivers/linux-driver), using the following command:

$ make KERNEL_SOURCE_DIR=~/workspace/linux-kernel

You should find the build result under the current folder: rp_usbdisplay.ko
=== III. Cross Compile - build the kernel driver for other platforms ===

You should have followed the steps described in the prerequisite section already. Here let's assume the location of the Linux kernel header(or source) is ~/workspace/target-linux-kernel.

Let's also assume the target platform is ARMv7. We need to use the cross-compiler : arm-linux-gnueabihf-gcc.

Enter the following command to build the kernel driver for the target:

make CROSS_COMPILE=arm-linux-gnueabihf- ARCH=arm KERNEL_SOURCE_DIR=~/workspace/target-linux-kernel

You should find the build result under the current folder: rp_usbdisplay.ko
== How to Use the Kernel Driver ==
=== I. Deploy the dependencies modules ===

If you had re-configed and recompiled the Linux kernel as required by the building process, you need to deploy the new kernel and all the kernel modules to the target system.

To be specific, you need to deploy AT LEAST the following kernel module to the target system's /lib/module/ folder along with the new kenrel image:

sysfillrect.ko
syscopyarea.ko
sysimgblt.ko
fb_sys_fops.ko

=== II. Deploy the compiled kernel driver ===

Reboot the target system to using the new kernel. Copy the compiled usb display driver (rp_usbdisplay.ko) to the following location:

/lib/modules/`uname -r`/kernel

Enter the above folder and execute the following command:

depmod

=== III. Load the kernel driver ===

Once you had deployed the kernel driver and all of its dependencies, you can ask the kernel to load the driver using :

modprobe rp_usbdisplay

By default the frame per seconds is set to 16. You can change it with the fps option when you load the driver :

modprobe rp_usbdisplay fps=25

In this case the frame per seconds is set to 25.

If you want to let the kernel load the driver automatically each time when the system starts, you can added the following line into the file /etc/modules: rp_usbdisplay

(i.e. echo rp_usbdisplay >> /etc/modules)
=== IV. Verify the driver ===

Using the lsmod command to check whether the driver has been loaded correctlly. You should get the output similar to the following text:

# lsmod
Module Size Used by
rp_usbdisplay 12171 0 [permanent]
fb_sys_fops 1412 1 rp_usbdisplay
sysimgblt 2199 1 rp_usbdisplay
sysfillrect 3295 1 rp_usbdisplay
syscopyarea 3112 1 rp_usbdisplay

Also, you should find the following message in the dmesg log:

[ 7.535799] input: RoboPeakUSBDisplayTS as /devices/virtual/input/input0
[ 7.548115] usbcore: registered new interface driver rp-usbdisp

To verify the driver work with the RoboPeak USB Display, connect the display to the target system via the USB cable. The display should display RoboPea Logo and turn to black (or something else) for about 3 second.

If the display keeps showing the white noise animation and the message : Waiting for signal, you should check the dmesg to see what happens. Normally, the driver will prompt the following message when the display has been pluged in :

[ 1814.173232] rp-usbdisp 4-1:1.0: RP USB Display found (#1), Firmware Version: X.XX, S/N: XXXXXXXXXXXX

Once the driver recognizes the display, a framebuffer device will be created. (e.g. /dev/fb0)

Use the following command to see whether framebuffer device is belonged to the USB display:

# cat /proc/fb
2 rpusbdisp-fb <

In the above example, /dev/fb2 is the related framebuffer device. To test whether the framebuffer device works, you may using the following command:

# cat /dev/urandom > /dev/fb2

You should see the display screen is filled with random color dots.
=== V. Make X11 output to the USB display ===

There is a sample X11 config file under the source folder: rpusbdisp/drivers/linux-driver/xserver_conf/10-disp.conf. You can use this sample file as the template to make X11 on your target system to output to the USB display.

STEP1: determine the framebuffer device name of the display. use the command cat /proc/fb

STEP2: modify the 10-disp.conf, change the framebuffer device name to the one determined in STEP1.

STEP3: copy the file 10-disp.conf to the X11's config folder (/usr/share/X11/xorg.conf.d for most systems).

STEP4: restart the X11 server

The X11 desktop should appear on the USB display.
== User Mode SDK ==

Besides the Linux kernel driver, we also provide a user mode sdk which is available on Windows, OS X, and Linux.

You can find the SDK in the drivers/usermode-sdk subdirectory.

== Useful commands ==
# you should see the display screen is filled with random color dots.
cat /dev/urandom > /dev/fb0

=== Show a picture on the screen ===
# picture.bmp requirement is bmp format with a resolution of 320 * 240,16 bitmap
# In linux, use gimp -> save as -> advance options -> 16-bit color
cat /tmp/picture.bmp > /dev/fb0

# Clear the screen
dd if=/dev/zero of=/dev/fb0

# Save the contents of the fb0
dd if=/dev/fb0 of=fbfile

# Write back in the screen
dd if=fbfile of=/dev/fb0

=== Input string to display on screen ===

Let’s check if the virtual console of the frame buffer has been created:

# ls /sys/class/vtconsole/vtcon*
/sys/class/vtconsole/vtcon0:
bind name subsystem uevent
/sys/class/vtconsole/vtcon1:
bind name subsystem uevent

The console has been created. Let’s check that it belongs to the frame buffer:

# cat /sys/class/vtconsole/vtcon1/name

(M) frame buffer device

# cat /sys/class/vtconsole/vtcon1/bind
1

#echo hellowrtnode > /dev/vcs1

=== Input string to display on screen ===
Let’s check if the virtual console of the frame buffer has been created:

# ls /sys/class/vtconsole/vtcon*
/sys/class/vtconsole/vtcon0:
bind name subsystem uevent
/sys/class/vtconsole/vtcon1:
bind name subsystem uevent

The console has been created. Let’s check that it belongs to the frame buffer:

# cat /sys/class/vtconsole/vtcon1/name

(M) frame buffer device

# cat /sys/class/vtconsole/vtcon1/bind
1

#chmod 777 /dev/vcs1
#echo hellowrtnode > /dev/vcs1

== Refresh firmware and do the following ==

A new device has to be created in the directory /dev:

#ls /dev/input/ -l
crw-r--r-- 1 root root 13, 64 Sep 17 18:44 event0

#cat /proc/bus/input/devices
I: Bus=0003 Vendor=0000 Product=0000 Version=0000
N: Name="RoboPeakUSBDisplayTS"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=1000003

#cat /dev/input/event0 |hexdump

Touch RoboPeak Mini USB Display, printed on the wrtnode

== Reference ==
* [http://wiki.wrtnode.com/index.php?title=WRTnode_add_support_for_RoboPeak_Mini_USB_Display WRTnode add support for RoboPeak Mini USB Display]
* [http://docs.robopeak.net/doku.php?id=rpusbdisp_faq#q11 RoboPeak Mini USB Display FAQ]

[[Category:Sensors and Modules]]

Raspberry Pi

2026-08-23T09:57:15Z

Tommy：Add a lead sentence

The '''Raspberry Pi''' is the single-board computer most of the projects on this wiki are built around. This page collects its GPIO pinout.

== GPIO connector ==
RPi A+,B+ GPIO J8 40-pin pinout.
[http://www.raspberrypi.org/documentation/hardware/raspberrypi/schematics/Raspberry-Pi-B-Plus-V1.2-Schematics.pdf]
Models A and B have only the first 26 pins.

{| class="wikitable"
! GPIO#
! 2nd fun
! pin#
!
! pin#
! 2nd fun
! GPIO#
|-
| -
| +3V3
| style="background:orange"| 1
|
| style="background:red"| 2
| +5V
| -
|-
| GPIO2
| SDA1 (I2C)
| style="background:#00FFFF"| 3
|
| style="background:red"| 4
| +5V
| -
|-
| GPIO3
| SCL1 (I2C)
| style="background:#00FFFF"| 5
|
| style="background:black; color:white"| 6
| GND
| -
|-
| GPIO4
| GCLK
| style="background:green"| 7
|
| style="background:#00FF80"| 8
| TXD0 (UART)
| GPIO14
|-
| -
| GND
| style="background:black; color:white"| 9
|
| style="background:#00FF80"|10
| RXD0 (UART)
| GPIO15
|-
| GPIO17
| GEN0
| style="background:green"|11
|
| style="background:green"|12
| GEN1
| GPIO18
|-
| GPIO27
| GEN2
| style="background:green"|13
|
| style="background:black; color:white"|14
| GND
| -
|-
| GPIO22
| GEN3
| style="background:green"|15
|
| style="background:green"|16
| GEN4
| GPIO23
|-
| -
| +3V3
| style="background:orange"|17
|
| style="background:green"|18
| GEN5
| GPIO24
|-
| GPIO10
| MOSI (SPI)
| style="background:#FF00FF"|19
|
| style="background:black; color:white"|20
| GND
| -
|-
| GPIO9
| MISO (SPI)
| style="background:#FF00FF"|21
|
| style="background:green"|22
| GEN6
| GPIO25
|-
| GPIO11
| SCLK (SPI)
| style="background:#FF00FF"|23
|
| style="background:#FF00FF"|24
| CE0_N (SPI)
| GPIO8
|-
| -
| GND
| style="background:black; color:white"|25
|
| style="background:#FF00FF"|26
| CE1_N (SPI)
| GPIO7
|-
| align="center" colspan="7" | ''(Models A and B stop here)''
|-
| EEPROM
| ID_SD
| style="background:yellow"|27
|
| style="background:yellow"|28
| ID_SC
| EEPROM
|-
| GPIO5
| -
| style="background:green"|29
|
| style="background:black; color:white"|30
| GND
| -
|-
| GPIO6
| -
| style="background:green"|31
|
| style="background:green"|32
| -
| GPIO12
|-
| GPIO13
| -
| style="background:green"|33
|
| style="background:black; color:white"|34
| GND
| -
|-
| GPIO19
| -
| style="background:green"|35
|
| style="background:green"|36
| -
| GPIO16
|-
| GPIO26
| -
| style="background:green"|37
|
| style="background:green"|38
| -
| GPIO20
|-
| -
| GND
| style="background:black; color:white"|39
|
| style="background:green"|40
| -
| GPIO21
|-
|}

Model B rev 2 also has a pad P6 of 8 pins offering access to an additional 4 GPIO connections.
[http://www.raspberrypi.org/documentation/hardware/raspberrypi/schematics/Raspberry-Pi-Rev-2.1-Model-AB-Schematics.pdf]

{| class="wikitable"
! Function
! pin#
!
! pin#
! Function
|-
| +5V
| style="background:red"| 1
|
| style="background:orange"| 2
| +3V3
|-
| GPIO_GEN7
| style="background:green"|3
|
| style="background:green"|4
| GPIO_GEN8
|-
| GPIO_GEN9
| style="background:green"|5
|
| style="background:green"|6
| GPIO_GEN10
|-
| GND
| style="background:black; color:white"| 7
|
| style="background:black; color:white"| 8
| GND
|}

Models A and B provide GPIO access to the ACT status LED using GPIO 16.
Models A+ and B+ provide GPIO access to the ACT status LED using GPIO 47, and the Power status LED using GPIO 35.

== Related projects ==

* [[Application - MX35LFxGE4AB, SPI NAND Flash]]
* [[Application - Keyes 38KHz IR Infrared Transmitter Module]]
* [[Application - u-blox NEO-6M, GPS module]]
* [[Application - DS1302, RTC module]]
* [[Application - HC-SR04, Ultrasonic ranging module]]
* [[Application - LPC1768, SPI communication]]
* [[Application - MAX7219, Serially Interfaced, 8-Digit LED Display Drivers (scrolling text)]]
* [[Application - MAX7219, Serially Interfaced, 8-Digit LED Display Drivers (interact with MPR121)]]
* [[Bluetooth keyboard auto connect]]
* [[RoboPeak Mini USB Display]]
* [[Application - Wifi AP]]
* [[Application - GPS tracker]]
* [[Application - Speech Recognition]]
* [[Application - Alexa]]
* [[Application - Greengrass]]
* [[Application - Google Assistant]]
* [[Application - Monitor GPIO interrupt in userspace]]
* [[Application - 3-axis accelerometer, GID-SSS/U10]]
* [[Application - RFID, RC522]]
* [[U-boot]]
* [[Kernel]]
* [[Android]]

[[Category:Boards and SoCs]]

RTD1073

2026-08-23T09:57:15Z

Tommy：Add a lead sentence

'''RTD1073''' was a RealTek-based IP media player built for NetGear. This page is the release log for its diagnostic and RadioTime firmware, 2010-2011.

''The repository referenced below (<code>192.168.50.188</code>) no longer exists. These notes are the surviving record of the project.''

==Project info==
Customer: NetGear<br>
Product: IP media player<br>
Chip: RealTek RTD1073<br>

==SVN info==
[[image:NTV350_REPO_20101123.jpg]]<br>
'''Diag'''
svn+ssh://192.168.50.188/svnroot/NTV350SDK/branches/diag
'''UI'''
svn+ssh://192.168.50.188/svnroot/NTV350SDK/branches/UI
'''RadioTime'''
svn+ssh://192.168.50.188/svnroot/NTV350SDK/branches/radioTime
<br>
'''Diag kernel'''
svn+ssh://192.168.50.188/svnroot/NTV350OS/branches/diagOS
'''RadioTime kernel'''
svn+ssh://192.168.50.188/svnroot/NTV350OS/branches/radioTimeOS

==Release info==
=== Diag ===
==== diag-1.0.0.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/diag-1.0.0.0
===== release date =====
2010/08/31
===== release note =====
First release with alpha version<br>
Supported command:
* play
* speed
* stop
* reset
* setDigiOutputMode
* setTVSystem
* usbDetect
* ver
* help
* exit

==== NTV350_Diag_1.0.1.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.0
===== release date =====
2010/09/01
===== release note =====
* Fix: Dummy message from USB scan
* Fix: exit command - kill self before leaving
* Add: "Unihan" sign before come in diag
* Add: Display "Firmware version" in ver command
==== NTV350_Diag_1.0.1.1 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.1
===== release date =====
2010/09/02

===== release note =====
* Add: add "getAppCRC" command for calculate and get crc of DvdPlayer
* Fix : Re-open the IR thread
* Add : Merge the card detecting solution
* Fix : Printf("Firmware Version: v") is printed with the version is found from DvdPlay binary file.
* Fix : memory card insert/remove message.
==== NTV350_Diag_1.0.1.2 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.2
===== release date =====
2010/09/03

===== release note =====
* Fix : trim the version string with control character in ASCII
==== NTV350_Diag_1.0.1.3 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.3
===== release date =====
2010/09/07
===== release note =====
* Fix : system revision
==== NTV350_Diag_1.0.1.4 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.1.4
===== release date =====
2010/09/09

===== release note =====
* Add getKernelCRC command:calculate CRC of kernel, need size as input parameter.
* Add getSquashCRC command:calculate CRC of last block of SquashFS, need size as input parameter.
==== NTV350_Diag_1.0.2.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.2.0
===== release date =====
2010/09/27
===== release note =====
* Enhance Diag launch time from ~11s to ~6s
Add: Remove sleep(5) in main.cpp to increase start up speed.

==== NTV350_Diag_1.0.3.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.0
===== release date =====
2010/10/15
===== release note =====
*Add : Auto play default video(demp.mpg) from USB
*Add : Remove WatchDog before running diag
*Fix : Stopall utility not kill DvdPlayer all the time
==== NTV350_Diag_1.0.3.1 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.1
===== release date =====
2010/10/20
===== release note =====

''Not recorded. The repository this page refers to is gone, so this cannot be recovered.''

==== NTV350_Diag_1.0.3.2 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.2
===== release date =====
2010/10/22
===== release note =====
* Disable DHCP when DvdPlayer launched
* Add : play Demo1/Demo2
==== NTV350_Diag_1.0.3.3 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.3
===== release date =====
2010/10/27
===== release note =====
-Fix: adjust searching Firmware and System version offset.
==== NTV350_Diag_1.0.3.4 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_Diag_1.0.3.4
===== release date =====
2010/11/23
===== release note =====
Add two command lines.
A. “play” command line:
1. play Demo1 (Demo1 = HD-underwater.mpg)
2. play Demo2 (Demo2 = Unihan_Jerry_CBARS100_1K_Tone.ts)
3. play file_location (example: play /mnt/usbmounts/sdb1/movie1.mpg)
4. play link_url (example: play http://192.168.50.194:8080/music/qianli.mp3)
B. “setVolumeRate” command line:
setVolumeRate rate_value (where rate value = 0 ~ 30)
Example: setVolumeRate 30 (set volume rate to MAX)

=== RadioTime ===
==== NTV350_RadioTime_1.0.0.0 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.0
===== release date =====
2010/09/06
===== release note =====
* First release UI prototype to NetGear
* Including search function
* Still can not play stream from RadioTime due to DTS license
==== NTV350_RadioTime_1.0.0.1 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.1
===== release date =====
2010/09/07
===== release note =====
* Remove network WORKGROUP layer
* Downsize the 20MB to 2MB for indexing
* Win7 PlayTo - Add backward & forward functions
==== NTV350_RadioTime_1.0.0.2 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.2
===== release date =====
2010/09/20

===== release note =====
* Add display status of xml,
* Add main menu for home and search submenu,
* Add new UI for NETGEAR,
* Add function to get radio channel bitrate and formats,
* Add category for each linking note.
* Add Netgear request UI(page1,page2,page3,search).

==== NTV350_RadioTime_1.0.0.3 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.3
===== release date =====
2010/09/27
===== release note =====
* Add WN111v2 driver and insert module automatically
* Add network connecting detection.
* Add first and last rolling detection.
* Modify UI as Netgear requested.

==== NTV350_RadioTime_1.0.0.4 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.4
===== release date =====
2010/10/07
===== release note =====
* Add rolling text in page2 and search.
* Change page3 to vertical scrolling.
==== NTV350_RadioTime_1.0.0.5 ====
svn+ssh://192.168.50.188/svnroot/NTV350SDK/tags/NTV350_RadioTime_1.0.0.5
===== release date =====
2010/11/03
===== release note =====
* Add check font length of scrolling string,
* Start scrolling after 1 second,
* Parsing M3U list for continue playing stream in list,
* Shrink logo screen and button,
* Add return playing error scheme.

[[Category:Boards and SoCs]]

Qualcomm, HDK8250(SM8250)

2026-08-23T09:57:14Z

Tommy：Add a lead sentence

Building Android for the Qualcomm '''HDK8250''' (SM8250) - the HLOS images, the non-HLOS images, and programming them to the board.

== Build tool ==
* Snapdragon LLVM Arm toolchain

* GCC Linaro GNU 4.9 – 2014.07 

* Install toolchain - Hexagon 8.3.04 and Hexagon 8.3.06
** export HEXAGON_ROOT=$PATH_OF_INTALLL_DIR

* Make bash in the default shell(symlink /bin/sh → dash to /bin/sh → bash)
<pre>
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh
</pre>
* install repo (dependency with python and git) ... prefer to use python 2.7
<pre>
curl https://storage.googleapis.com/git-repo-downloads/repo-1 > ~/bin/repo
chmod a+x ~/bin/repo
rm -rf ~/.repo* ~/.gnupg
gpg --import

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.11 (GNU/Linux)

mQENBFHRvc8BCADFg45Xx/y6QDC+T7Y/gGc7vx0ww7qfOwIKlAZ9xG3qKunMxo+S
hPCnzEl3cq+6I1Ww/ndop/HB3N3toPXRCoN8Vs4/Hc7by+SnaLFnacrm+tV5/OgT
V37Lzt8lhay1Kl+YfpFwHYYpIEBLFV9knyfRXS/428W2qhdzYfvB15/AasRmwmor
py4NIzSs8UD/SPr1ihqNCdZM76+MQyN5HMYXW/ALZXUFG0pwluHFA7hrfPG74i8C
zMiP7qvMWIl/r/jtzHioH1dRKgbod+LZsrDJ8mBaqsZaDmNJMhss9g76XvfMyLra
9DI9/iFuBpGzeqBv0hwOGQspLRrEoyTeR6n1ABEBAAG0H0NvbmxleSBPd2VucyA8
Y2NvM0BhbmRyb2lkLmNvbT6JATgEEwECACIFAlHRvc8CGwMGCwkIBwMCBhUIAgkK
CwQWAgMBAh4BAheAAAoJEGe35EhpKzgsP6AIAJKJmNtn4l7hkYHKHFSo3egb6RjQ
zEIP3MFTcu8HFX1kF1ZFbrp7xqurLaE53kEkKuAAvjJDAgI8mcZHP1JyplubqjQA
xvv84gK+OGP3Xk+QK1ZjUQSbjOpjEiSZpRhWcHci3dgOUH4blJfByHw25hlgHowd
a/2PrNKZVcJ92YienaxxGjcXEUcd0uYEG2+rwllQigFcnMFDhr9B71MfalRHjFKE
fmdoypqLrri61YBc59P88Rw2/WUpTQjgNubSqa3A2+CKdaRyaRw+2fdF4TdR0h8W
zbg+lbaPtJHsV+3mJC7fq26MiJDRJa5ZztpMn8su20gbLgi2ShBOaHAYDDi5AQ0E
UdG9zwEIAMoOBq+QLNozAhxOOl5GL3StTStGRgPRXINfmViTsihrqGCWBBUfXlUE
OytC0mYcrDUQev/8ToVoyqw+iGSwDkcSXkrEUCKFtHV/GECWtk1keyHgR10YKI1R
mquSXoubWGqPeG1PAI74XWaRx8UrL8uCXUtmD8Q5J7mDjKR5NpxaXrwlA0bKsf2E
Gp9tu1kKauuToZhWHMRMqYSOGikQJwWSFYKT1KdNcOXLQF6+bfoJ6sjVYdwfmNQL
Ixn8QVhoTDedcqClSWB17VDEFDFa7MmqXZz2qtM3X1R/MUMHqPtegQzBGNhRdnI2
V45+1Nnx/uuCxDbeI4RbHzujnxDiq70AEQEAAYkBHwQYAQIACQUCUdG9zwIbDAAK
CRBnt+RIaSs4LNVeB/0Y2pZ8I7gAAcEM0Xw8drr4omg2fUoK1J33ozlA/RxeA/lJ
I3KnyCDTpXuIeBKPGkdL8uMATC9Z8DnBBajRlftNDVZS3Hz4G09G9QpMojvJkFJV
By+01Flw/X+eeN8NpqSuLV4W+AjEO8at/VvgKr1AFvBRdZ7GkpI1o6DgPe7ZqX+1
dzQZt3e13W0rVBb/bUgx9iSLoeWP3aq/k+/GRGOR+S6F6BBSl0SQ2EF2+dIywb1x
JuinEP+AwLAUZ1Bsx9ISC0Agpk2VeHXPL3FGhroEmoMvBzO0kTFGyoeT7PR/BfKv
+H/g3HsL2LOB9uoIm8/5p2TTU5ttYCXMHhQZ81AY
=AUp4
-----END PGP PUBLIC KEY BLOCK-----

[Ctrl-D]
</pre>

== Sync Android ==
<pre>
cd sxr2130-la-1-0-sdx55-tn-1-0_amss_standard_oem_apq.git/sxr2130_apps/LINUX/android
./sync.sh
</pre>

== Build the application processor Android HLOS images ==
<pre>
sudo apt-get install libxml*
source build/envsetup.sh
lunch kona-userdebug
./build.sh dist -j8 |& tee make-log.txt
</pre>

== Location of Android HLOS images ==
<pre>
ls out/target/product/kona
abl.elf dtb.img installed-files-vendor.json persist shareduid_violation_modules.json
android-info.txt dtbo.img installed-files-vendor.txt persist.img signed
appcompat dynamic_partition_metadata.txt integrity pgo_profile_file_missing.txt signed_encrypted
appcompat.zip fake_packages ipa prebuilt_dtbo.img soong_to_convert.txt
boot-debug.img filesmap kernel previous_build_config.mk super_empty.img
boot.img gen kona-apps-eng.ganzin.zip product_copy_files_ignored.txt super.img
boot.zip gensecimage_target.timestamp kona-coverage-eng.ganzin.zip product.img symbols
build_fingerprint.txt installed-files-odm.json kona-img-eng.ganzin.zip ramdisk system
build_system_stats.txt installed-files-odm.txt kona-symbols-eng.ganzin.zip ramdisk-debug.img system.img
build_thumbprint.txt installed-files-ramdisk-debug.json metadata ramdisk.img testcases
certificate_violation_modules.txt installed-files-ramdisk-debug.txt metadata.img ramdisk-recovery.img userdata.img
clean_steps.mk installed-files-ramdisk.json module-info.json recovery vbmeta.img
coverage installed-files-ramdisk.txt obj recovery.id vbmeta_system.img
data installed-files-recovery.json obj_arm recovery.img vendor
debug_ramdisk installed-files-recovery.txt odm recovery-two-step.img vendor.img
dexpreopt.config installed-files-root.json odm.img root verified_assembled_vendor_manifest.xml
dlkm installed-files-root.txt otatools.zip secimage.log wall_werror.txt

</pre>

== NON-HLOS images ==
=== bootloader ===
<pre>
sudo apt-get install libtinfo* gcc-8 p7zip-full
cd <target_root>/boot_images/QcomPkg/
python ./buildex.py --variant LAA -r RELEASE -t 8250,QcomToolsPkg
</pre>

=== aDSP ===
<pre>
cd sxr2130_adsp/adsp_proc/build/ms
python build_variant.py 8250.adsp.prod
</pre>

=== cDSP ===
<pre>
cd sxr2130_cdsp/cdsp_proc/build/ms
python build_variant.py 8250.cdsp.prod
</pre>

=== SLIP ===
<pre>
cp nanopb-0.3.6-linux-x86.tar.gz sxr2130_slpi/slpi_proc/ssc_api
cd sxr2130_slpi/slpi_proc
python ssc_api/build/config_nanopb_dependency.py -f nanopb-0.3.6-linux-x86
cd sxr2130_slpi/slpi_proc/build/ms
python ./build_variant.py 8250.slpi.prod SENSOR_VARIANT=xr USES_FLAGS=USES_SXR2130_ENABLE
</pre>

== Program images ==
* boot into fastboot mode in device
<pre>
#get device console first, and run following command
reboot bootloader
</pre>

* Check device availability
<pre>
tommy@tommy-ThinkPad-X1-Carbon-5th:~/projects/ganzin/kona_img$ fastboot devices
45ff8ad1 fastboot
</pre>

* Pre load test
<pre>
tommy@tommy-ThinkPad-X1-Carbon-5th:~/projects/ganzin/kona_img$ fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 2.831s]
booting...
OKAY [ 0.063s]
finished. total time: 2.893s
</pre>

* Start flash image if boot normally.....
<pre>
tommy@tommy-ThinkPad-X1-Carbon-5th:~/projects/ganzin/kona_img$ fastboot flash boot_a boot.img
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.950s]
writing 'boot_a'...
OKAY [ 0.209s]
finished. total time: 3.159s
</pre>

* Check marker in boot log
<pre>
#get console first!

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x51df805e]
[ 0.000000] Linux version 4.19.81+ (ganzin@ganzin-sw) (clang version 8.0.12 for Android NDK) #1 SMP PREEMPT Wed Jun 24 19:31:22 CST 2020
[ 0.000000] Machine model: Qualcomm Technologies, Inc. kona HDK
[ 0.000000] earlycon: msm_geni_serial0 at MMIO 0x0000000000a90000 (options '')
[ 0.000000] bootconsole [msm_geni_serial0] enabled
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] Memory limit set/overridden to 5065MB
[ 0.000000] OF: reserved mem: OVERLAP DETECTED!
</pre>

[[Category:Boards and SoCs]]