Hey! I’m finally back, and I’m sorry for the delay… it took longer than I expected
Just saw the wiki page—amazing work, thanks a lot for setting that up! I’ll go through it now and contribute anything I can from my side. Let’s keep pushing this forward!
Also I saw that you are trying to add Bluetooth support
Am I right?
I’ll continue where we left off later today/tomorrow
depending on your time zone
Bluetooth is already supported you just need to install the BlueZ Bluetooth stack and set it up as you wish.
I was hoping to setup Bluetooth coexistence as Wi-Fi interferes with Bluetooth.
what is does is disable Wi-Fi channels to allow Bluetooth it also cuts width of the WI-FI channel to 20mhz and can prioritize traffic when required.
It seems this is not really a possibility on ath11k chipsets as the driver in Linux lacks support for three wire coexistence and instead uses the WMI interface.
But it would be cool to use Bluetooth presence to configure the coexistence automatically on the fly.
In the dumped OS image it calls the lcd display the LCM it references it all over the place it seems to be what they call in in manuals and online etc... as I believe it's full name is the local control module.
If you could change one of the uboot environment with setenv/saveenv and then dump the images again and verify differences with the CRC or md5 sum so we can work out the correct location for the environment variables.
I need this to control boot options from OpenWrt.
It seems they are stored in the uboot partition mtd16 I think, a wrong move and we could overwrite boot code and brick the router.
I'm also interested to find what device has the mac address: 24:5a:4c:82:48:2e I'm guessing it is WI-FI that has pulled it from the art partition.
It will let me know if nvmem worked or not as in theory the mac's should all be working now if I have not stuffed up something.
I'm unsure if the lm63 controls the fan directly or what as it has the ability to do that.
I'm guessing the lm63 need setting up with thermal limits eg:
The chipset already has passive tripping points in the DTS to throttle the device.
there is an intresting patch to init the lm63 from the device tree here:
Hey, quick update:
I changed the IP using setenv/saveenv and dumped mtd16: here’s the updated dump.
Also confirmed: 24:5a:4c:82:48:2e shows up in ip link, so looks like nvmem is working and pulling MAC correctly for Wi-Fi! i hope so at least.
Let me know if the dump confirms the env location.
U-Boot Env Test: then dumped and checksummed mtd16. The checksum did change, so envargs do seem to be stored inside mtd16 as you suspected.
New MD5: 4a9b6fe9c1d742abe7874c7c8771c8ec
Fan PWM Control: I tested writing values to the PWM sysfs, and the fan does spin and respond, but makes a buzzing noise at low duty cycles... likely due to a too-low PWM frequency. Might need to tweak period if supported.
Let me know what you'd like me to try next
and sorry for taking long.
I compared the dump you sent with the previous dump and the crc is identical, are you sure you sent me the new file?
As for the pwm frequency this should be setup by the bootloader but it seems it is setup by the firmware, you will have to set the pwm freq etc via i2c or use the experimental patch as above.
That patch would benefit from parsing parameters under the lm63 node and updating registers instead of putting values in registers to make it clear.
The device captures the mac from the art partition for WI-FI nvmem should capture that same mac it is referenced as the label mac in the board.json
the mac should increment giving each lan port an incrementing number but that bit is not working.
Can you see if the label mac is present in \etc\board.json ?
You won’t believe what happened! Ubiquity finally wrote me an email back with the GPL Sources for the AMPLIFI Alien, should I sent it to you here or privately? Maybe Google drive (.tar file) I didn’t think they would actually do this
.
Also I’ll check the things you last wrote when I’m back home later today and have time then
see you. i hope i have time*
Post a link to google drive.
Others on here might want to download it.
Keeping an eye on this thread, looks like a cool device. Keep up the good work.
Would love to see the screen supported but that’s a long term dream.
here:
i hope this has most things we need... im not sure but we will see
![]()
i can already imagine that its gonna be very hard to get it working correctly.
Sorry to get your hopes up but this is not the source for the amplify alien router, I think it is for the amplifyHD or just some random source code, but I did not see any dts for it in there unless it has some other name they reference it as internally.
This source indicates it is for the AR71xx chipset not the IPQ8074, they have defiantly sent you the wrong thing, it is also nowhere near complete.
Man I already had that feeling actually
I knew it…
Well that sucks, I’ll make a new email
this time I’ll also add that I want the full version for the Alien….
I also asked ChatGBT to analyze the full file and it told me the same
so yea
I’ve sent them an new email
taking weeks to respond and then to also send the wrong one is just a bit strange but whatever.
Í think the plan is to make it as hard a possible so people give up they don't really want to give you the source, legally it needs to be complete and full.
There seems to be no u-boot source also.
We just need to stress them and then eventually they will… I will not stop. They are gonna get annoyed at some point trust me.
