Hi Newracom, I've noticed that the Firmware_Downloader, is outdated...

The commentary does say that the version was updated to a 4.1 28 days from now, but It's not.

I tried clonning the git also downloading the file directly and downloading the sdk .rar.

The .rar has a version 3.0 of the firmware.downloader, and the repository has a version 4.0.

I'm having issues while erasing XIP F/W Sector, and I saw that the last version (4.1) Upgraded the timeout from 5 to 20; so that could help me and solve my issue.

I await your reply, hope you stay great. Kind regards

Dear newracom sir,

I found some problems when testing open AP on CN channel. When I set S1G_CH:7615, the following error is displayed.
[------------LOG------------]
[ctrl_iface_receive_response] cmd: set country CN
wim: 0 country code:CN freq:0
api: 0 CC(CN) from driver is different from CC(US) from cal. data
s1g: 0 index:5 CC: 'CN', # of CH:14
wim: 0 auto txgain is activated
reply_len: 2

reply: OK

[wifi_init] TX Power (18 dBm)
[wifi_task] wifi_init Success !!
[wifi_start_softap] Trying to start Soft AP (SSID:my_demo, S1G_CH:7615 , BW:1)
[ctrl_iface_receive_response] cmd: add_network
reply_len: 1

reply: 0

[0][_nrc_wifi_set_state] state=DISCONNECTED
[STAGetNonS1GFreqWithBw] invalid frequency, s1g_freq:7615
[0][nrc_wifi_softap_set_conf] invalid s1g_freq:7615, bw:1
[wifi_start_softap] Fail to set sotftap config
[wifi_task] ASSERT! Fail to start softap
[------------END------------]

In addition, when I tested S1G 7555, I could turn on the AP normally, but it was turned on to 5210. The corresponding value should be 5180 according to the table.
[------------LOG------------]
[ctrl_iface_receive_response] cmd: set country CN
wim: 0 country code:CN freq:0
api: 0 CC(CN) from driver is different from CC(US) from cal. data
s1g: 0 index:5 CC: 'CN', # of CH:14
wim: 0 auto txgain is activated
reply_len: 2

reply: OK

[wifi_init] TX Power (18 dBm)
[wifi_task] wifi_init Success !!
[wifi_start_softap] Trying to start Soft AP (SSID:my_demo, S1G_CH:7555 , BW:1)
[ctrl_iface_receive_response] cmd: add_network
reply_len: 1

reply: 0

[0][_nrc_wifi_set_state] state=DISCONNECTED
[ctrl_iface_receive_response] cmd: set_network 0 mode 2
reply_len: 2

reply: OK

[ctrl_iface_receive_response] cmd: ndp_preq 1
wim: 0 set ndp probe request: 1
reply_len: 2

reply: OK

[ctrl_iface_receive_response] cmd: set_network 0 frequency 5210
reply_len: 2

reply: OK

[ctrl_iface_receive_response] cmd: set_network 0 scan_freq 5210
reply_len: 2

reply: OK

[ctrl_iface_receive_response] cmd: set_network 0 ssid "my_demo"
reply_len: 2

reply: OK

[ctrl_iface_receive_response] cmd: set_network 0 pairwise CCMP
reply_len: 2

reply: OK

[ctrl_iface_receive_response] cmd: set_network 0 group CCMP
reply_len: 2

reply: OK

[ctrl_iface_receive_response] cmd: set_network 0 key_mgmt WPA-PSK
reply_len: 2

reply: OK

[ctrl_iface_receive_response] cmd: set_network 0 proto RSN
reply_len: 2

reply: OK
[------------END------------]

nrc7292_sdk/package/standalone/sdk/apps/wifi_common/wifi_config_setup.c
nrc_usr_print("network_mode %d [%s]\n",wifi_config->device_mode, ( wifi_config->network_mode == 0) ? "Bridge" : "NAT");

wifi_config->device_mode maybe wifi_config->network_mode

I realized that nrc7292 will stuck in scanning after wake up from ps schedule with "net_init" be "true" if there no AP.
Does there have any method to config that to abort scanning while no AP there, and go to exception progress?
SDK version is v1.5

When I use the JP channel, there is an error that the STA opens to an error channel.
The problem appears to be due to channel duplication.

AP setting:

country JP
channel 9245
bw 4
AP is started correctly
[wifi_start_softap] Trying to start Soft AP (SSID:halow_demo, S1G_CH:9245 , BW:4)
[ctrl_iface_receive_response] cmd: set_network 0 frequency 5235
reply_len: 2

STA setting:

country JP
bw 4
scan_freq_num 1
9245

But STA opened the wrong channel
[ctrl_iface_receive_response] cmd: set_network 0 frequency 5185
reply_len: 2

bw 2, 924.5 -> 5185
bw 4, 924.5 -> 5235
Seems STA does not use bandwidth to distinguish.

Hi,

When the NRC7292 goes into deep sleep, the GPIO pins will be in output low state. Only pins GP00, GP01 and GP07 will go into high-Z state, if i measured correctly. This is not useful for my application so I hoped I could change this with the new nrc_ps_set_gpio_ functions from the SDK v1.4.

I tried calling following functions before calling the nrc_ps_deep_sleep function:

nrc_ps_set_gpio_direction(0x7);
nrc_ps_set_gpio_out(0x7);

This didn't change anything with the pin configuration.

Furthermore, I tried the included sample_ps_schedule sample from the SDK (https://github.com/newracom/nrc7292_sdk/tree/master/package/standalone/sdk/apps/sample_ps_schedule). This example uses the new nrc_ps_set_gpio _functions. This also didn't change the stock pin configuration to the configuration that is defined in the example code.

Is there anything I missed to use these functions?

Thanks in advance!

Dear Sir,

I use AT cmd to connect to the wifi ap, open a udp server remotely, use the at command to send data, the server can receive the data normally. When the server sends data "AA", the raspi-atcmd-cli terminal only print RECV : +RXD:0,2, there is no output data "AA", is there any other need to set?

AT+SOPEN="UDP",1000
SEND: AT+SOPEN="UDP",1000
RECV: +SOPEN:0
RECV: OK

AT+SSEND=0,"192.168.0.99",8800,10
SEND: AT+SSEND=0,"192.168.0.99",8800,10
RECV: OK

0123456789
SEND: DATA 0 10

RECV: +RXD:0,2

Dear newracom sir,

I use the AT CMD to enter the AP mode, but in AP mode it cannot be used to send UDP packets, the AT CMD is as follows.

AT
SEND: AT
RECV: OK

AT+WCOUNTRY="US"
SEND: AT+WCOUNTRY="US"
RECV: OK

AT+WSOFTAP=906,"MyWiFi","wpa2-psk","MyPassword"
SEND: AT+WSOFTAP=906,"MyWiFi","wpa2-psk","MyPassword"
RECV: OK

AT+WIPADDR="192.168.0.215","255.255.0.0","192.168.0.2"
SEND: AT+WIPADDR="192.168.0.215","255.255.0.0","192.168.0.1"
RECV: OK

AT+SOPEN="UDP",1000
SEND: AT+SOPEN="UDP",1000
RECV: +SOPEN:0
RECV: OK

AT+SSEND=0,"192.168.0.215",1000,10
SEND: AT+SSEND=0,"192.168.0.215",1000,10
RECV: OK

1234567890
SEND: DATA 0 10

RECV: +SEVENT:"SEND_IDLE",0,0

=========================================
But in STA mode, it can send UDP packets normally.

AT+WCOUNTRY="US"
SEND: AT+WCOUNTRY="US"
RECV: OK

AT+WSCAN
SEND: AT+WSCAN
RECV: +WSCAN:"2c:3b:70:00:00:12",915.0,-10,"[WPA2-PSK-CCMP][ESS]","MyWiFi"
RECV: OK

AT+WCONN="MyWiFi","wpa2","MyPassword"
SEND: AT+WCONN="MyWiFi","wpa2","MyPassword"
RECV: OK

AT+WIPADDR="192.168.0.215","255.255.0.0","192.168.0.1"
SEND: AT+WIPADDR="192.168.0.215","255.255.0.0","192.168.0.1"
RECV: OK

AT+SOPEN="UDP",1000
SEND: AT+SOPEN="UDP",1000
RECV: +SOPEN:0
RECV: OK

AT+SSEND=0,"192.168.0.215",1000,10
SEND: AT+SSEND=0,"192.168.0.215",1000,10
RECV: OK

0123456789
SEND: DATA 0 10

RECV: +RXD:0,10

Hi,
I'm using standalone-mode with the precompiled binary ATCMD_UART from: https://github.com/newracom/nrc7292_sdk/tree/master/package/standalone/atcmd_binary

It seems that TX-Power switching does not work, at least at STAs.
I'm running the following AT-command sequence at STA:
AT+WTXPOWER=1
AT+WTXPOWER=11
AT+WTXPOWER=21
AT+WTXPOWER=30
Each answered with ok.

After each AT+WTXPOWER, I send an AT+WSTAINFO? at the AP. The response is as follwos:
+WSTAINFO:1,"00:c0:ca:ae:d5:9c",-38,32,6
OK
+WSTAINFO:1,"00:c0:ca:ae:d5:9c",-38,32,6
OK
+WSTAINFO:1,"00:c0:ca:ae:d5:9c",-38,32,6
OK
+WSTAINFO:1,"00:c0:ca:ae:d5:9c",-38,32,6
OK

I would have expected significant changes of the RSSI value from -38 to -9 dBm.

Sending a Ping from AP to STA however, changes the result of WSTAINFO (performad at AP):

+WEVENT:"PING",64,"192.168.200.2",1,255,9
+WEVENT:"PING",64,"192.168.200.2",2,255,5
+WEVENT:"PING",64,"192.168.200.2",3,255,8
+WEVENT:"PING",64,"192.168.200.2",4,255,22
+WEVENT:"PING",64,"192.168.200.2",5,255,5
OK
+WSTAINFO:1,"00:c0:ca:ae:d5:9c",-10,29,4
OK

Now, I doget -10, which is surprisingly close to the estimated -10 dBm.

I think there is an issue with updating the RSSI value in the STA-frimware, or is that normal behaviour?
I would appreciate any information or clarification.

Dear Newracom,

The default of nrc_wifi_softap_set_conf() is to set pairwise to CCMP. CCMP in wpa_cli means that AES128.
[ctrl_iface_receive_response] cmd: set_network 0 pairwise CCMP
[ctrl_iface_receive_response] cmd: set_network 0 group CCMP

I manually set pairwise to CCMP-256. WIFI can connect successfully but shows some RX errors. Does AES-CCMP KEY only support 128BIT?

Code
ctrl_iface_receive_response(0, "set_network 0 pairwise CCMP-256");
ctrl_iface_receive_response(0, "set_network 0 group CCMP-256");

log
[ Modem Detection Statistics ]

Tx Triggered Detection Count: 7
Rx Triggered Detection Count: 7
--Non-zero Length NDP: 0
--IP Length: 0(0)
--MPDU Length Mismatch: 7
--Buffer Mismatch: 0
--MPDU Length Size: 0

modem recovery
wpa: Unsupp cipher (type: 255)lmc: Invalid cipher type: 7
[RX_LEN_MISMATCH_1] t:2 st:8 pt:1 td:0 fd:1 vector->len:98 vector->mpdu_len:86 offeset:4
[RX_LEN_MISMATCH_2] icv_len:0, okay:1, error_key:0, error_mic:0 vif_id: 0
[RX_LEN_MISMATCH_3] is_bcast: 0, icv_len(bcast): 0

Would it be possible to update https://github.com/newracom/nrc7292_sdk/blob/master/package/standalone/tools/external/FirmwareFlashTool.exe

to use a jSerialComm version >= 2.7.0? That's the version in which aarch64 support was added. Or if you can you point me to the source for this tool I can make a PR.

Dear newracom

I use [NRC7292 Standalone SDK v1.4] to build the sample_udp_client APP, and download the firmware(out\nrc7292\standalone_xip\sample_udp_client\nrc7292_standalone_xip_sample_udp_client.bin) to NRC7292 by FirmwareFlashTool.exe through UART. After powering on, it keeps rebooting, below is the UART output, is there any idea about this issue? The output seems that do not run to user_init(void).

I build another APP hello_world, it can boot successfully, and can show "Hello, NEWRACOM IEEE802.11ah~!!".

===start===

Newracom Boot Loader
FW is OK.
Jump to 0x10000
Boot Reason: @@@@@ [WDT] @@@@@

boot_reason:2, check_sig:0, ps_mode:0

retention info size (1007 Byte)
stainfo(20) apinfo(47) s1ginfo(16) keyinfo(137) userinfo(4) chinfo(5) wakeupinfo(3) acinfo(44) tidinfo(76) ipinfo(12) lbtinfo(10) rfinfo(375) ucode_info(66) drv_info(7)
ps_schedule_info(65)
RTC FREERUN Mode initialized
lmac_get_country_code_index Not supported Country()
lmac_get_country_code_index Not supported Country()
No 1. Task Name(LMAC Task) Handle(272867444) Added to Stack Trace
Before Calibration PRF_GPIO_DATA : 0x210004 , PRF_GPIO_DIR : 0x280001 , PRF_GPIO_ALT0 : 0x17fffe
Before Calibration PRF_GPIO_DATA : 0x210004 , PRF_GPIO_DIR : 0x280001 , PRF_GPIO_ALT0 : 0x17fffe
No 2. Task Name(FAST Task) Handle(272849096) Added to Stack Trace
[fast_task_init, 479] task creation succeed!(0x104358c8)
No 3. Task Name(SYSTEM Task) Handle(272859044) Added to Stack Trace
No 4. Task Name(Background Task) Handle(272840624) Added to Stack Trace
[background_task_init, 224] task creation succeed!(0x104337b0)

===end===
Repeated reboot

Hi,

I have trouble using the deep sleep function of the nrc7292. I tried the sample_ps_standalone sample from the SDK v1.4 on a silex sx-newah module. It's just the module and some decoupling capacitors, so no other components connected. When I try the sample code, i get about 790uA in deep sleep.

I tried the same sample_ps_standalone sample code but the older version from SDK v1.3.4. With the older version, i measure about 580uA.

It seems that the nrc_ps_deep_sleep function from the newest SDK is worse than the previous one as it uses about 200uA more.

Apart from that, I think the power usage in deep sleep is still extremely high. 600uA for a microcontroller in deep sleep seems a lot to me and not really useful for a battery powered device. Especially when they specify that Wi-Fi Halow supports coin cell battery devices.

What am I doing wrong or is it something that has to be fixed in the future?

Thanks in advance!

Dear Newracom,

I use the API to set the SPI clock. When the set clock is greater than 16mhz, the frequency is still maintained at 16mhz. Is it possible to set a higher speed?

nrc_spi_init(SPI_MODE0, SPI_BIT8, 16000000);

Hi!

I'm having trouble with getting the firmware over the air to work. I followed the aplication note and the server-side works like it should. However, I tried using my code and FOTA example on the Silex module and Alfa networks raspberry pi shield. Both stop at the function nrc_fota_is_support().

Can you confirm that both boards aren't supported for FOTA and what are the requirements for a module/board to be supported for FOTA? Is there a supported module available on the market right now?

Thanks in advance!

Wouter

Dear newracom,

Is there an API to set the guard interval?
I can only use the UART console command to set the guard interval.
nrc7292_standalone_xip>help set gi
Usage: set gi {short|long|auto|capa} [0|1]

Thanks, best regards.

Thank you for the detailed SDK and documentation.

I wanted to ask if the NRC7292 SoC includes an internal temperature sensor, and whether this sensor is accessible via the SDK or drivers? This is related to tracking the temperature of the chipset itself.

Please let me know, thank you :)

Dear newracom,

I use the app sample_uart to test UART and a PC with CP2102 to send data to nrc7292 UART channel0.
When I add another two tasks in user_init(), the UART uart_intr_handler() can not receive correctly.
PC sends "01234567890123456789"
the uart_intr_handler() has been called two times, and the received data are "012" and "456789012345678"
May I ask if the UART buffer is only 16 bytes? It seems that the data is not taken out immediately, causing the UART FIFO buffer to be full, so some data is lost.

But when I remove another two tasks in user_init(), the UART uart_intr_handler() can receive correctly.
PC sends "01234567890123456789"
The uart_intr_handler() has received "01234567890123456789"

Hi,
I tried to use the latest version of the nrc7292_standalone_xip_ATCMD_UART.bin (ver. 3.1.4 rev.6) with AT-Commands using the AC-CMD Test-Tool v1.3.0 to enter the commands. The command AT+WSOFTAP which configures the module in the AP mode doesn't work. I always get the ERROR 3 as a return message. Other AT-Commands worked successfully.
After I tried an older Version of the nrc7292_standalone_xip_ATCMD_UART.bin (date: 10-23-2021) the command (AT+WSOFTAP) worked without an error.
The version with the build date from 10-23-21 works perfect. But we don't know the revision number.
We got that build file from an earlier download.

I am not able to send the binaries into this Forum. If you need the binary, let me know where to push them.
Can you please check the AT Command with the latest version rev 6 and give me a feedback about the issue.
Thank you very much.
Gerrit

Dear All,

I'm using standalone mode to integrate NRC with a microcontroller and I'm having problems to send AT command via SPI with length lower than 512 bytes. The SPI transaction in a Microcontroller is limited to 255 bytes. I don't undertand why needs to send 512 bytes for a simple AT command? Also I don't understand why CRC calculation only included the header?

I will appreciate your support, thanks in advance. Kinds regards

Dear newracom sir,

AT CMD APP provides AT+SSEND to send Transport Layer packets.
Can I directly transmit the Data Link Layer packets using AT CMD?
Can AT CMD APP also print the Data Link Layer packets received from nrc7292 by SPI?

Dear Newracom,

Currently, we can only find nrc_uart_register_interrupt_handler() to register the RX Callback function. Is there any way to register the interrupt callback function for UART TX done?

Good morning,

I've been running the device in standalone mode with the HSPI ATCMD firmware. I've found a bug that if you send it some data it will go into passthrough mode even if you sent a size on the SSEND command. The data sent in this case ends with a \r\n. Could that be the issue? If you're using strtok or something to find the end of data...

Any future plan to open source the ATCMD firmware?

I (10568) NRC: SEND: AT+SOPEN="tcp",1234

I (10598) NRC: RECV: +SOPEN:0

I (10598) NRC: RECV: OK

...
I (16278) NRC: RECV: +SEVENT:"CONNECT",1

... 
I (16288) NRC: SEND: AT+SSEND=1,24 // size passed, should not go to passthrough

I (16288) NRC: RECV: OK

I (16308) NRC: SEND: DATA 24

I (16308) NRC: SEND: AT ******* THIS IS STILL INTERPRETED AS DATA??

I (16308) NRC: RECV: +SEVENT:"RECV_READY",1,41 // other side sends data

I (17408) NRC: RECV: +SEVENT:"SEND_IDLE",1,0,0,0 **** EVENT TO LEAVE PASSTHROUGH?????