This has been fixed in our internal releases... *Latest public release June 22, this was fixed in internal GIT in early Aug.
submit a support ticket and get a patch... (You may have already done so as this was discussed as a support ticket in internal dev meeting today.)
Search found 1080 matches
- Mon Sep 26, 2022 12:25 pm
- Forum: NetBurner Software
- Topic: Need help with crash
- Replies: 7
- Views: 7532
- Tue Sep 13, 2022 3:44 am
- Forum: NetBurner Software
- Topic: Recovering from a corrupted image
- Replies: 8
- Views: 2095
Re: Recovering from a corrupted image
I don't think signed image will work if you force a _APP.s19
- Sun Sep 11, 2022 12:35 pm
- Forum: NetBurner Hardware
- Topic: MODM7AE70 pinout
- Replies: 1
- Views: 1762
Re: MODM7AE70 pinout
Get datasheet from here...
https://www.netburner.com/products/syst ... on-module/
https://www.netburner.com/products/syst ... on-module/
- Wed Sep 07, 2022 2:18 pm
- Forum: NetBurner Software
- Topic: Recovering from a corrupted image
- Replies: 8
- Views: 2095
Re: Recovering from a corrupted image
Just a note one of the very common wget's for windows has a 64K limit and will fail.
Use the exe we provide with our tools..
Use the exe we provide with our tools..
- Wed Sep 07, 2022 2:17 pm
- Forum: NetBurner Software
- Topic: Recovering from a corrupted image
- Replies: 8
- Views: 2095
Re: Recovering from a corrupted image
If you know the ip address, you should be able to easily recover. Assuming this is aonbe of the coldfire based devices. (if its a MODM7AE70 or SBE70LC you may have to set the recovery jumper on the device.) If the setup under the 'alternate' monitor is set for DHCP (IE the ip address in zero) Then i...
- Fri Sep 02, 2022 6:10 pm
- Forum: NetBurner Software
- Topic: Recovering from a corrupted image
- Replies: 8
- Views: 2095
Re: Recovering from a corrupted image
With that monitor version should be able to just update to the device.
Using the current 3.X tools.
The 3.X discovery might not work from the monitor.
Does your network have a DHCP server on it?
You can also use the 2.X autoupdate tools to load the S19 you loaded via FLA.
Using the current 3.X tools.
The 3.X discovery might not work from the monitor.
Does your network have a DHCP server on it?
You can also use the 2.X autoupdate tools to load the S19 you loaded via FLA.
- Sun Aug 14, 2022 10:06 pm
- Forum: NetBurner Software
- Topic: RTC api undefine upgrade to 3.x
- Replies: 6
- Views: 2870
Re: RTC api undefine upgrade to 3.x
To get temporarily unstuck while we figure this out...
Might also try
#include <mcf5441x_rtc.h)
int MCF541X_RTCSetTime(struct tm &bts);
int MCF541X_RTCSetSystemFromRTCTime(void);
int MCF541X_RTCSetRTCfromSystemTime(void);
What you did should have worked...
Might also try
#include <mcf5441x_rtc.h)
int MCF541X_RTCSetTime(struct tm &bts);
int MCF541X_RTCSetSystemFromRTCTime(void);
int MCF541X_RTCSetRTCfromSystemTime(void);
What you did should have worked...
- Sun Aug 07, 2022 3:16 pm
- Forum: NetBurner Software
- Topic: NB_SSL_SUPPORTED and Code Size Problem
- Replies: 6
- Views: 4575
Re: NB_SSL_SUPPORTED and Code Size Problem
We will pull gmtime out of that location so it does not pull in the crypto world.
(I think there is a gmtime in the newlib as well... but its choosing the crypto one so... ):-(
(I think there is a gmtime in the newlib as well... but its choosing the crypto one so... ):-(
- Sat Aug 06, 2022 6:48 pm
- Forum: NetBurner Software
- Topic: NB_SSL_SUPPORTED and Code Size Problem
- Replies: 6
- Views: 4575
Re: NB_SSL_SUPPORTED and Code Size Problem
This is an error, that should not be there.
Try using gmtime_r
You have to pass in your struct tm so its not globally allocated....and thus thread safe.
struct tm *gmtime_r(const time_t *clock, struct tm *result);
Try using gmtime_r
You have to pass in your struct tm so its not globally allocated....and thus thread safe.
struct tm *gmtime_r(const time_t *clock, struct tm *result);
- Fri Aug 05, 2022 8:38 pm
- Forum: NetBurner Software
- Topic: NB_SSL_SUPPORTED and Code Size Problem
- Replies: 6
- Views: 4575
Re: NB_SSL_SUPPORTED and Code Size Problem
Are you using TLS/SSL?
If not I don't understand how that causes the Wolf ssl stuff to link.
Can you send a map file of the one that is 131% and open a support ticket?
If not I don't understand how that causes the Wolf ssl stuff to link.
Can you send a map file of the one that is 131% and open a support ticket?