NetBurner Community Forum

Should using a modified makefile from one of the examples work with v2.9.5 of the tools? Because it doesn't work for me.

Not only that, but after running the makefile I went back to Eclipse to build my app and now I get error:

Build Error
Generated resource conflict
two resources of the same name ...

Is it possible to do a salted sha-256 hash for image signing? I understand salting, I just don't understand how it would work in an embedded system.

We are not using certificates. All we are doing is signing the firmware image using the private key created by OpenSSL.

The only reason this is coming up is because a customer is concerned that we used a version of OpenSSL that is out-of-date and no longer supported. At the time we started signing ...

For signing firmware images, we are using OpenSSL v1.1.1f, which I think was provided by Netburner. It's been about 4-years since we started signing images. In any case, is it possible to use the current version of OpenSSL, which I think is v3.5.0, to create the private/public key pair?

Am I ...

It turns out I was calling StartTcpUpdate at two different locations in my code. I'm running out of feet to shoot.

It turns out the return code for OSTaskCreatewName is defined in OSTaskCreate. And error code of 40 mean the task priority is already used.
These are my priorities:

#define USERMAIN_PRIO (55)
#define NTP_TASK_PRIO (54)
#define UDP_TASK_PRIO (53)
#define SNMP_PRIO (52)
#define FTP_TASK_PRIO (51 ...

StartTcpUpdate just calls OSTaskCreatewName, and returns the value returned by OSTaskCreatewName. But the uCosLibrary document doesn't define any return values.

Well, this is embarrassing. It is in my code. It's generated when function StartTcpUpdate returns a non-zero value, which in this case is 40.

At the completion of programming a Nano module using Autoupdate, v2.5, the following message is output on the serial port:

TcpUpdate Error: 40

The module is programmed correctly and runs as expected. I have detected nothing wrong. What does that message mean?

The applications are built with v2.9 ...

Any guidance on how we should proceed?