NetBurner Community Forum

Dear All,

As we know, using the utility MTTTY.exe, we can setup mod5213 configuration, such as, Baudrate, Boot Delay, etc., and download application code.
I wonder if I can develop a Windows program to set the prefered settings automatically. Tt will be more efficeint this way, especially when u have thousands of mod5213 to setup.

I have gone thru some postings in this Yahoo newsgroup and some NNDK docs. However, I still have some questions unclear. Could anybody give me some comments, thanks in advance.


1) "Sending 0xFCFC to an application that has called EnableSerialUpdate() will put the MOD5213 into a state equivalent to having entered FLA from the NB prompt." (please see Yahoo posting #2927) What special character sequence can make the MOD5213 goto a state equivalent to display "NB>" on the MTTTY screen?

2) What are the command formats for setting Baudrate, Boot Delay, and Save these setting thru MOD monitor??

3) By the way, when downloading code to the MOD5213, "After the MOD5213 confirms that it is out of the application and in monitor the PC sends the string 0xBBBBBBBB followed by the base address of the binary FLASH file. This will tell the MOD5213 you are about to send a binary instead of a standard _app.s19. ~~~~~" (please see Yahoo posting #2743). What does "base address of the binary FLASH file" refer to? is it an physical address in the MOD5213 flash? or an physical address in PC memory?


Regards,

Haomin

Hi,

How about a pc program that interacts with the monitor. For example, it looks for the sign-on message, sends the command to enter the monitor, then sends the correct serial commands to set up the parameters. The only tricky part is to make sure the pc program is listening on power-up or reboot of the device.

Hello all,

Based on other posts and the source code in the folder
C:\Nburn\pctools\magicload, I developed a firmware loader using Labwindows/CVI.
In my code, I have to repace the communication call "cc.write(unsigned char* buf, int count)" with "ComWrt(int port, char* buf, int count)". All other file conversions and transfers were kept intact. The firmware file is downloaded 4 bytes @ each transfer just like Magicload.exe.

My program works well except one thing. I have to introduce at least 5 mS DELAY after each transfer (0f 4 bytes) to make the loading successful, otherwise the mod5213 will have checksum errors. While the Magicload.exe has no problem with that ( on the same PC machine). Does anybody know why this happens?

Thanks in advance.


Haomin

Solved.