OpenELEC Testbuilds for RaspberryPi Part 2 - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166) +---- Thread: OpenELEC Testbuilds for RaspberryPi Part 2 (/showthread.php?tid=184866) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-11-27 Updated my previous post with Video settings. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-11-27 (2013-11-27, 01:57)MilhouseVH Wrote: Updated my previous post with Video settings. Okay, guess it's not that. Finding the first firmware that does it would be useful. Some new commits on newclock3 (fix for all subs appearing at start, fix EDL commercial skip start time, and a couple more Ben Avison idle CPU reductions). RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-11-27 When I get around to identifying the specific firmware, do you want me to focus on next or master? And I guess the plan will be to roll through the firmware from the hexxeh repo, testing start.elf/fixup.dat starting from Nov 7th using the last known good image (02:51 on Nov 20)? RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-11-27 (2013-11-27, 02:17)MilhouseVH Wrote: When I get around to identifying the specific firmware, do you want me to focus on next or master? And I guess the plan will be to roll through the firmware from the hexxeh repo, testing start.elf/fixup.dat starting from Nov 7th using the last known good image (02:51 on Nov 20)? Yes. Notionally there was just one source code tree, and any commits to either master or next were just builds of the top of the source tree, so you should be able to bisect on date, ignoring which tree it came from. But I'd focus on master and find the breaking commit, and only look at next if there were commits there between the two master commits. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - bhamail - 2013-11-27 This is great news. Looking forward to this fix making it into new Gotham builds. Thanks! (2013-11-25, 16:55)popcornmix Wrote:(2013-11-21, 19:59)popcornmix Wrote: Looks like just creating a file called <video>.edl with: RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-11-27 Quick update before I start attacking the firmware, I tried the "bad" firmware through my Onkyo 828 amp and got mixed results when playing back the BRFC_100 sample: No passthrough (48KHz PCM shown by receiver), 2.0 Channels - result: "Chirping" No passthrough (48KHz PCM shown by receiver), 5.1 Channels - result: "Clicking" (could just be a multi-channel variation of the "chirping" but now sounds more like a "click") With Passthrough (DD5.1 shown by receiver), 5.1 Channels - result: Perfect audio RE: OpenELEC Testbuilds for RaspberryPi Part 2 - allan87 - 2013-11-27 The above i(MilhouseVH) s consistent with my experience with DD audio. With other audio (AAC, MP3) I do get the chirping with passthrough. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-11-27 Well at least it didn't take long to find the firmware! This was my process: Started with the last known good build from 02:51 on Nov 20: Code: rpi512:~ # vcgencmd version && cd /flash && ls -la fixup.dat start.elf Cloned the raspberrypi/firmware repo on the master branch and started with the first commit on 7 Nov, copying start_x.elf and fixup_x.dat to the Pi as start.elf/fixup.dat respectively. First 7 Nov commit details: Code: bcm2835-driver.git$ git reset --hard 452637c34ceb3f3323e09b56c705f34bbe3a4594 Result: Audio OK Second Nov 7 commit details - same as build (confirming my process is valid): Code: bcm2835-driver.git$ git reset --hard e85b566308a06952103fc3c70f46f3d13aac557b Result: Audio OK (as expected) Nov 10 commit details (only commit that day): Code: bcm2835-driver.git$ git reset --hard 18a163f9341755b00841312af2878afeb64c131c Result: *CHIRPING* ding ding ding we have a winner! I've gone back and forth several times now between e85b566 (last commit on 7 Nov) and 18a163f (10 Nov) and only getting "chirping" with 18a163f. It appears this commit resolves several problems, not sure which one might be the underlying cause of the audio glitches (which seem to be PCM related). Edit: One of the fixes in 18a163f appears to be network related, so I just wanted to add that I've reproduced chirping when streaming from NFS, SMB, and also direct from USB. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-11-27 I tried the 10 Nov firmware with the following options added to config.txt: Code: pause_burst_frames=0 I also added pause_burst_frames=1 to config.txt with the "known good" 7 Nov firmware (e85b566308a06952103fc3c70f46f3d13aac557b), and heard no chirping (there was one, single, solitary "chirp", but it took several attempts at playing BRFC_100 to hear it, and may have been a one-off so possibly not related). RE: OpenELEC Testbuilds for RaspberryPi Part 2 - rterblanche - 2013-11-27 With the last build that was done onthe thread I updated my firmware for the first time and also got the chirping. But I just installed an older xbmc version an left the firmware as is. No more chirping. Will go and do more tests tonight to confirm, but don't understand why I am getting different results. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-11-27 (2013-11-27, 10:03)rterblanche Wrote: With the last build that was done onthe thread I updated my firmware for the first time and also got the chirping. I just tested this theory, and still get chirping. I put the latest 24 Nov build on my system, tested it and confirmed bad chirping. I popped the SYSTEM and kernel.img from the "known good" 20 Nov 02:51 build directly into the root of the SD card (so keeping the 24 Nov firmware), rebooted, and still heard chirping. The chirping *was* less pronounced (less frequent) than with the entirely 24 Nov build - which is strange - but it was still present. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-11-27 (2013-11-27, 07:06)MilhouseVH Wrote: I've gone back and forth several times now between e85b566 (last commit on 7 Nov) and 18a163f (10 Nov) and only getting "chirping" with 18a163f. It appears this commit resolves several problems, not sure which one might be the underlying cause of the audio glitches (which seem to be PCM related). Thanks for searching. There's one change with a config option you can test. Add this to config.txt (with "chirping" firmware) Code: hdmi_dma_waits=7 If not I may have to produce a few test builds to narrow it down further. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-11-27 (2013-11-27, 13:50)popcornmix Wrote: Thanks for searching. There's one change with a config option you can test. Add this to config.txt (with "chirping" firmware) Sorry for the delay. I added the above setting to config.txt, but it made no difference - still chirping. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2013-11-27 (2013-11-27, 22:14)MilhouseVH Wrote: Sorry for the delay. I added the above setting to config.txt, but it made no difference - still chirping. Okay, here are test builds of commits between the good and bad builds: https://dl.dropboxusercontent.com/u/3669512/temp/start_431286.elf https://dl.dropboxusercontent.com/u/3669512/temp/start_431587.elf https://dl.dropboxusercontent.com/u/3669512/temp/start_431592.elf https://dl.dropboxusercontent.com/u/3669512/temp/start_431595.elf https://dl.dropboxusercontent.com/u/3669512/temp/start_431597.elf https://dl.dropboxusercontent.com/u/3669512/temp/start_431600.elf if I understand things correctly, 431286 should be good. 431600 should be bad. Somewhere in between in the bad commit. Note these are test builds with a fixed memory split (256M/256M). You should move current fixup.dat out of the way. RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2013-11-27 The results are in... working top to bottom through your start.elf files: Code: 20 Nov 02:51 Build: No chirping I've repeated the testing twice, and chirping kicked in both times with 431595. |