Hi,
I had a look at buildroot, seems neat. Thanks for the tip!

As for miraclecast, I don't know... I had some prior experience with it.
Almost forgot about it. But I've just tried the latest version today and,
again, out of 4 android devices I own only one can connect to my
miraclecast sink running on my linux mint 20 on a very new thinkpad p1 with
intel chipset. Some blame it on the intel chipset actually and say it works
better on other wifi chipsets :).  Maybe that's true. I'll try to run it on
the a10 dongle, but I doubt I'll have enough time for this project this
week.
My other 3 android devices fail to connect for mysterious unspecific
reasons. Usually timeout, but the actual cause is not clear. I activated
trace logging on the miracle sink and also on the miracle-wifid but could
not figure out. So from my point of view miraclecast is a pretty
experimental project ATM that offers similar reliability as the original
firmware on these cheap hdmi miracast dongles. At least my success rate was
identical :) So I'd rather look for an alternative :)

On Wed, Sep 16, 2020 at 12:27 AM Clément Péron <[email protected]> wrote:

> Hi Adrian,
>
> Le mar. 15 sept. 2020 à 13:06, Adrian N <[email protected]> a écrit :
> >
> > Gediz, all credit should go to you! I couldn't have done anything
> without your tips.
> >
> > I think I would be able to re-create a small image from scratch, with
> the bare necessities, an ip stack, wifi, busybox, telnet or ssh.
> >
> > But not sure the final goal of making this little board work with hdmi
> output + miracast and / or dlna is actually attainable.
>
> Just my advice here but don't rewrite a build system from scratch use
> buildroot or yocto.
> Buildroot is very easy to understand / Yocto more powerful
> https://git.buildroot.net/buildroot/tree/package/miraclecast?h=master
>
> https://github.com/OSSystems/meta-miracast/blob/master/recipes-miracast/miraclecast/miraclecast_git.bb
> Both have a package/recipe for miraclecast.
>
> In your case, I would choose buildroot.
>
> Add the board config, make the uart / wifi / hdmi works. (Mainline it
> to buildroot :P)
> Then I think the last thing is to write the gstreamer pipeline to
> connect the miraclecast sink to cedrus and you're good.
>
> Good luck,
> Clement
>
> >
> > Could not find any opensource projects for that, especially one that
> could fit in this very constrained environment.
> >
> > Adrian
> >
> > On Mon, Sep 14, 2020 at 1:54 PM Nazım Gediz AYDINDOĞMUŞ <
> [email protected]> wrote:
> >>
> >> On 11.09.2020 18:40, Adrian N wrote:
> >> > That was an awesome tip Gediz!
> >> > I added the line:
> >> >     case 0x1623: /* Allwinner A10 */
> >> > right before this line:
> >> >
> https://github.com/linux-sunxi/sunxi-tools/blob/7fe6024211ffed3024b0491ee9f2a19c17848c12/fel-spiflash.c#L163
> >> > because it seems A10 is actually more similar to A20 in terms of
> booting
> >> > from spi flash than A13 (line 154 that you suggested).
> >> > I tried both variants, but it worked only after adding before line
> 163.
> >> > So now spiflash-info command succeeds and tells me it's a Macronix 16
> MB
> >> > flash.
> >> > I was able to dump it, and then running strings command on it yielded
> >> > some very interesting strings:
> >> > eGON.BT0
> >> > sunxi-cubieboarda10
> >> > sunxi SPI
> >> > U-Boot SPL 2019.10 (Oct 15 2019 - 20:11:30 +0800)
> >> > U-Boot 2017.01-rc2-00098-gc88edf
> >> > bootcmd=sf probe 0; sf read 0x41000000 0x80000 0x400000; bootz
> 0x41000000
> >> > bootdelay=0
> >> > baudrate=115200
> >> > arch=arm
> >> > cpu=armv7
> >> > board=sunxi
> >> > board_name=sunxi
> >> > soc=sunxi
> >> > stdin=serial
> >> > stdout=serial
> >> > stderr=serial
> >> > bootm_size=0xa000000
> >> > kernel_addr_r=0x42000000
> >> > fdt_addr_r=0x43000000
> >> > scriptaddr=0x43100000
> >> > pxefile_addr_r=0x43200000
> >> > ramdisk_addr_r=0x43300000
> >> > dfu_alt_info_ram=kernel ram 0x42000000 0x1000000;fdt ram 0x43000000
> >> > 0x100000;ramdisk ram 0x43300000 0x4000000
> >> > fdtfile=sun4i-a10-cubieboard.dtb
> >> > console=ttyS0,115200
> >> > boot_prefixes=/ /boot/
> >> > boot_scripts=boot.scr.uimg boot.scr
> >> > boot_script_dhcp=boot.scr.uimg
> >> > boot_targets=fel
> >> >
> >> > This list is only partial. I'm not going to put here the full list
> >> > because it is very long. I also cannot post publicly the contents of
> the
> >> > SPI flash for obvious reasons.
> >> >
> >> > My goal is now to extract some useful config info from this dump to be
> >> > able to re-create from scratch a fully open-source and very small
> >> > firmware based on linux by following the steps from
> >> > https://linux-sunxi.org/New_Device_howto
> >> >
> >> > The biggest problems are the flash and SDRAM of this device are very
> >> > limited: 16MB flash, 128 MBytes DDR2 RAM (based on the ELIXIR
> >> > N2TU1G16GG-AC label on the chip). Is that too little ?
> >> >
> >> > Btw, it would be good to add that one-line patch to git master. I'll
> >> > make a PR next week.
> >> >
> >> > I also found 3 unmarked round pads that might be the serial console,
> but
> >> > I cannot confirm that yet.
> >> >
> >> > Thanks a lot!
> >>
> >> You're welcome. I'm glad it worked out. It would be even better to be
> >> able to debug the board with a console. I think 128 MBs of DRAM and 16
> >> MBs of SPI flash can easily handle a modest application. You can do it.
> >>
> >>
> >> On 14.09.2020 10:27, Adrian N wrote:
> >> > Hi,
> >> >
> >> > I've created a trivial PR for adding SPI flash support for A10 :
> >> > https://github.com/linux-sunxi/sunxi-tools/pull/138
> >> > It seems that nothing more was needed, just adding the ID to the
> >> > supported list.
> >> >
> >> > Thanks!
> >>
> >> That's cool. Our next fellow hacker won't have to tinker around. And I
> >> admire you, by the way. I'm using sunxi-fel for around two years and did
> >> not have an opportunity to contribute to the tool :)
> >>
> >> So, thank you too!
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "linux-sunxi" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> > To view this discussion on the web, visit
> https://groups.google.com/d/msgid/linux-sunxi/CAAuDtmd9V%3DWj4gK7u%3Dw%2Bqgwnq7f6zLdV906qsxWFdWbh148RNg%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/linux-sunxi/CAAuDtmddmnrgbFuMOTaM7O4vK0Hq_W%2B%2B4GLnCmHJ6yJLhg-Kow%40mail.gmail.com.

Reply via email to