![]() ![]() Of course Processor Expert could be wrong with it too, but so far it always worked when I made the pin muxing with Processor Expert before doing the PCB layout. To verify muxing, pull-up/pull-down/interrupt settings. :00:01.17 bitrate 2.6kbits/s speed2.24x video:0kB audio:67kB subtitle:0kB other streams:0kB global headers:2kB muxing overhead. So I’m using Processor Expert as the muxing verification (at least with dummy components and software) to ensure that my pin assignment and routing will work. Hi, Im trying out the new version, it seems to work almost flawlessly, but on some files it gives me an error: ffmpeg exited with code 1: avinterleavedwriteframe(). My only help in this is Processor Expert: I do not build that PCB until I have at least all pins I need allocated and configured in Processor Expert to make sure I can make the assignment and muxing the way I need it. So I have burnt my fingers too many times on this, especially migrating from one device to a different package or different controller in the same family. If AVFMTCTXNOHEADER is set in ctxflags, then new streams may also appear in avreadframe (). demuxing: streams are created by libavformat in avformatopeninput (). The semiconductor provided documenation does not make it simpler, and with the plethora of devices things get even more complicated. New streams are created with avformatnewstream (). Am running it on ubuntu with command gcc muxing. The functions getaudioframe(), openaudio() generates dummy audio frames and fillyuvimage() generates dummy video frames. I have trashed a few PCB’s because I *thought* that I can mux things in a certain way, until to find out that it is not possible that way I thought it is possible. thekamilz I have provided the link to muxing.c in the question. Especially if the pin muxing is not clearly documented. When attempting to publish a imovie project to a dvd using idvd I get the message 'the project could not be - Answered by a verified Mac Support Specialist We use cookies to give you the best possible experience on our website. Yes, I appreciate and hate that feature the same time. I recommend to disable/mux the reset pin only a few second after power up to give the debugger a chance to get access to the CPU. Your microcontroller still runs, but you need to be lucky (or fast enough) to get control over the CPU. That might mean that the debug probe is not able to get control over the CPU, especially if low power mode is involved, or if this happens that fast. If I mux the pin early in the startup process, then this means the microcontroller boots and after a micro-seconds later the reset line is disabled. But here be careful: muxing the reset pin means that there is no way to reset the microcontroller with the reset pin. □ The same thing can be done for the reset pin. With this I have the NMI pin ‘muxed’ as normal GPIO pin. I had not a clear reproducible case, but it helped if I re-enabled the other setting to ‘unblock’ it. In the earlier version of Processor Expert I had sometimes the issue that one setting was ‘grayed’ out. □ The settings of interrupts and pin enable are connected and interlocked. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |