Skip site navigation (1)Skip section navigation (2) 
Date:      Wed, 22 Mar 2017 11:19:35 -0500
From:      Karl Denninger <karl@denninger.net>
To:        "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Pi-series sound output options
Message-ID:  <025036c0-a5a7-33f2-58a7-55f31fbc6e41@denninger.net>
index | next in thread | raw e-mail 

[-- Attachment #1 --]
Ugh.

This morning I had a repeat of a problem I've run into before and it
hosed me good -- a production Pi2 unit failed to restart after a power
failure.  It hung after the "UE0" ident line.

This is related to the fact that I have to run updated bootcode
(bootcode.bin and related files) on that device because the stock
bootcode that FreeBSD-11 uses along with u-boot is severely-unstable for
sound output.  Specifically, after some period of time it will simply
stop talking on the sound port and nothing fixes it other than a reset.

With the updated bootcode and setting pwm_mode=2 sound is stable - IF it
boots.  The problem is that it doesn't /always /boot; the failures are
lockups during some part of the device probe process, and are fatal.  If
you power cycle a few times it will eventually come up and once it does
it's fine.

Attempting to use even /later /versions of the bootcode and related
files (like, for instance, the current stuff now out there) results in
mmc not being seen and thus you can't mount root, so trying to roll
forward isn't an option either as those are completely non-functional. 
There appears to be a clash between the DTB file and the updated
firmware in some fashion.  Pulling over the newer DTB from the Linux
side of the world associated with the newer bootcode results in a
non-booting FreeBSD kernel.

I'd go to the Pi3 (despite no integrated WiFi) in places where I need
this capability except that on the Pi3 we have no sound *at all* at
present in the code because the vchiq driver doesn't exist and won't
compile "as-exists" today.

This application NEEDS sound output capability.  I don't care if it's on
a plug-in via USB but it has to work in a "FreeBSD-like" manner (e.g.
open up a PCM channel, etc.)

Are there any options with this platform available at present or am I
stuck with porting this app to Linux (yuck; among other things the
"NanoBSD" option on FreeBSD is nice for reliability reasons!)

-- 
Karl Denninger
karl@denninger.net <mailto:karl@denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/

[-- Attachment #2 --]
0	*H
010
	`He0	*H
\0X0@=0
	*H
010	UUS10UFlorida10U	Niceville10U
Cuda Systems LLC10UCuda Systems LLC CA1"0 	*H
	Cuda Systems LLC CA0
161218194535Z
211217194535Z0W10	UUS10UFlorida10U
Cuda Systems LLC10Ukarl@denninger.net0"0
	*H
0
͍fd`1ie6";fSz`5¹/?{=Ӵowjħ_fnӴMG\ҢҖ4ib}>@mJo&mM;
Q9U cj]p퐆W.2E=
^¢tzĄ'5i7_`~#dY
`]R]N%R}EXzqV@[oN	T>5AwYˡA"\v&YG]+($p:M,T?=mJkMљg*ym
L!J[./d׷?W^LysD'1
+V'~{-SSX=q-f=%&V<m4BeSet|
l2m 6iO{wv
+aHXˈ5=~é*C!?uJr3tb'3`Oe)üLxt&3N526llU
.|Cp[l?007++0)0'+0http://cudasystems.net:88880	U00	`HB0U0,	`HB
OpenSSL Generated Certificate0U/Zi
0GhG0U#0$q}ݽʒm50U0karl@denninger.net0
	*H
b%X%gwq	
ɁэrK[DMJ35W6
sz8d|qB2Cyw2PbV}
â[!W{HD7oD.TZ'w6~g( -,]R8P{*[f<1=7jGj9铚~3f2AʺN	k~@vz^j(>ͺyh2y{/9}4.45#S|<fW!.,Bss*Q+h=}l@	"q "M&6J5*,G {hɫjbNgǠ.ЃXȶ4$O.5evHlZba!4eE!x|Za1򹿈nZ5TuPvW|#G+	DZpI7S'n0 haGa@vZ	e|]Cu+))vRyY100010	UUS10UFlorida10U	Niceville10U
Cuda Systems LLC10UCuda Systems LLC CA1"0 	*H
	Cuda Systems LLC CA=0
	`HeM0	*H
	1	*H
0	*H
	1
170322161935Z0O	*H
	1B@@FN5Zy|g@¢9j1bN۹YKTS+LViPEP0l	*H
	1_0]0	`He*0	`He0
*H
0*H
0
*H
@0+0
*H
(0	+710010	UUS10UFlorida10U	Niceville10U
Cuda Systems LLC10UCuda Systems LLC CA1"0 	*H
	Cuda Systems LLC CA=0*H
	1010	UUS10UFlorida10U	Niceville10U
Cuda Systems LLC10UCuda Systems LLC CA1"0 	*H
	Cuda Systems LLC CA=0
	*H
۱"Clӟ'tD^	K%~vj/2rDFx>'Rt.Ww;'@--+)ESo1H׸Z[pZzdNya#?1m[?/%wʫFo0~>bfeS̅17tyuSoUV?@44(c(DMYČ(8
;rḒxg-#
^G`Tńu鷔{d}&E1ZЌ`j?ga`2-P入Coݽl'`ܞb<	0fJEճd=p/uXjXm׾1x)O?[XR	}RH^j<;@սmAitQUUSXsW6uS*LAǭǘNςEHDyn~vҼƑ=6zڽJD
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?025036c0-a5a7-33f2-58a7-55f31fbc6e41>