Hi,
I am trying to test FGH100MAAMD M.2 boards connected to ESP 32 P4 Devkit, there are 2 such boards, i have flashed one of the ESP with “SoftAP” example from morsemicro/halow component which seems to work fine as mentioned in the image below [s1g channel 7, s1g class 6 is set in menuconfig]
However when i flash second ESP with “Scan” example expecting it to show this particular Halow AP in the results, but for 1st run it comes out blank as mentioned in the image below.
I wouldn’t expect this to be caused by not connecting the wake and busy lines to the host, but please try connecting them to see if it changes behaviour.
Do you have a Linux based HaLow device available which can be configured for the same region? I’d like to verify the AP is beaconing.
For extra debugging, you can turn up the logging of morselib by setting MMLOG_LEVEL_DEFAULT=MMLOG_LEVEL_DBG in halow/components/morselib/CMakeLists.txt. Note that this will likely fail to compile as it will look for some functions (mm_hexdump) that haven’t been implemented yet in esp-halow. See SDK Internal Logging with Zephyr - #2 by ajudge for an implementation that you can pull in.
I tried connecting WAKE and BUSY pins to ESP GPIO (soldered from M.2 board) but when i run porting assistant it fails at the following stage, i tried many GPIOs for BUSY pin.
[UPDATE 2]
Scan is still empty, i will use the logging method suggested by @ajudge and update here
[UPDATE 3]
Scan example is still empty, even with WAKE and BUSY pins and all porting assistant tests ok, feels like a issue with Scan/Soft AP example, scan is finished in an instant shouldn’t it show atleast “no AP found”
My softap example is set at s1g op class 6 and channel 7, with country code IN. Is there any debug/fix available for the same?
According to this software release note, it says it might have issues in EU regions, could anyone confirm this information with respect to 2 ESPs, using mm6108 (FGH100MAAMD2) one as SoftAP example and other running a Scan example may not be able to see the AP on Scan?
I would strongly suggest to get the logging going. And also use one of our evaluation kits as a reference to isolate which device (the AP or the Client), isn’t behaving correctly.
well with P4 i am using the correct BCF, ESP S3 was a desperate last moment attempt to get it running , hence the mistake with BCF.
However i have some wonderful updates for you @ajudge.
Today my HL2 was delivered, and i set it up as an AP, and ran the scan example on my ESP P4 and it worked. I was able to see HL2 AP on my scan example, i was also able to connect with STA_Connect to the AP, and then tried uplink using my 2.4ghz wifi. It also worked
Now coming to ESP P4 AP. Since last week i had a doubt maybe my AP was not working, now i tested it with HL2, scanned for available AP and there it was. ESP 32 halow AP.
Now the conclusion and the problem is
ESP 32 P4 can create Halow AP
ESP 32 P4 can see HL2 AP
BUT… ESP 32 P4 scan cannot see ESP 32 P4 Halow AP, while HL2 can see the ESP32 Halow AP
Hence i cannot connect 1 ESP STA to other ESP AP. However connections with HL2 is smooth
i read in software release notes that STA may not be able to associate with AP for EU and GB regions.
Anyways i absolutely love HL2 now and appreciate MM team for making one, i am just waiting for an update where i can set s1g op class and channel number.
