NetBurner Community Forum

Hi John, Please, try the following function to see if it resolves your issue. You'll need to place the following source in \nburn\platform\MODM7AE70\source\pin_irq.cpp void ClearISR(PinIO pin) { int idx = &(pin.pio) - PIOA; // PIO controller index volatile uint32_t isr = pin.pio.PIO_ISR; // Inte...

Thanks for bringing this to our attention. This has now been patched for the next release of the NNDK. To answer your question, that behavior was not intentional. For anyone using the NBWIFIIN modules, this did not affect it's driver since it does not return values outside the range of a uint8_t. Th...

The DSPI driver for the MODM7AE70 currently only supports one SPI module. The SAME70 has multiple peripherals that can be configured for SPI, but we have only written a driver for one of the dedicated SPI peripherals on the SAME70 so far. There are other peripherals, such as the USARTs, that can be ...

Mike, After taking a look at things, we've realized that the PIT interrupt/semaphore/flag functions defined in nburn\MOD5270\include\pitr_sem.h and nburn\MOD5270\system\pitr_sem.cpp should have been ported over to the PK70. SetUpPITRFunc() defined in pitr_sem.cpp shows how to configure a PIT interru...

Hi Mike, You're looking for the "Pins" array instead of the "J1" and "J2" arrays. This is defined in \nburn\include\pins.h. There is some example usage in the comments above the class definition, too. Note the platform #ifdef for the PinIO class definition in pins.h. Yo...

Which send email function are you using? Are you sending the email to a common server like Google, Outlook, Yahoo, etc? Are you calling the send email function from the web server task? Are other tasks able to run other than the firmware update task? What does your send email fail condition logic lo...

Alternatively, if you're just trying to avoid having to get a certificate from a Certificate Authority, you can create a self-signed certificate as described in the following article: https://www.netburner.com/learn/creating-a-self-signed-certificate-for-secure-iot-applications#diy-section . You wil...

Are you capturing the WebSocket handshake in your Wireshark capture? If not, Wireshark won't recognize the packets as WebSocket packets but TCP packets instead.

Is the whole message (WebSocket payload) and length correct in the packets that Wireshark captures?