NetBurner Community Forum

I have the NETBurner development kit. I wish to communicate between both NetBurner MOD5234_1588 twin boards, shipped with the development board. The steps i thought of as follow:

A) Download an bin image on both the boards.

B) Duplicate the interfacing for both the boards i.e. one board (board1) would be connected to the development board and another (board2) will have the exact same connections, probably by shorting with board1.

C) Can i assign IP address to both boards (1&2) in some manner?

D) Can i FTP/SSH from board1 to board2 somehow?

I think I am missing few key steps on this. Could you provide me some insight.

Rahul

Rahul,

Your list contains so many issues I'm not sure where to even begin. Yes, you can download images, that is how you get your app in the device. Likewise, you can assign ip addresses.

Maybe the best way to start is to break the functionality down into the smallest, simplest steps. One way might be to first get one device working and talking to a simple network connection on a PC using telnet. Then add each level of functionality to it in the smallest possible steps. Once you have one board working, then do the same thing with the other netburner device, one function at a time.

I was curious if it was possible to ping from one core module to another after both core modules have running images on them.

yes, it would be possible. You would have to have one board know the ip address of the other and the same with the other board.

A) One core module is connected to the Development board using J2_C and I have connected it to host PC using RJ-45. Core Module has got IP Address of the Ethernet Cable. How can i connect another core module to Network. Shall i connect it to same J2_C as the first one, then maybe use blue RJ-45 patch cord to connect it to an existing network.

B) I'm still not clear on how to ping from one core module to another one? NB modules support UDP/IP protocol. How can i ping from one NB module to another one having known corresponding IP Addresses. Could you please enumerate possible steps i should be following.

Rahul

Hi

I am glad you replied to my post. I was able to program both core modules and assign them separate IP addresses. I was also able to write a small TCP Server, i used telnet port for sending packets.

I am still clueless on how to send packets from one NetBurner module to another module. Please note that one NB module is connected to J1 and J2 connectors, another one is just powered on (i just connected its VCC and ground) and has Ethernet connection. Do i need to connect all its J1 and J2 pins as i did for first NB module.

Also could you suggest me a piece of software code i need to send packets from one module to another.

regards,
Rahul

What you are trying to do with making one network device talk to another is the same method whether it be a PC, MAC or embedded computer like the netburner. If using tcp, one device needs to listen on a specific port number, then the other device needs to know the ip address and port number of the first device, then use a connect() call to get to it. If this is new to you (network programming) then you are going to have a bit of reading and research to do to cover all the aspects/concepts. I would recommend TCP/IP Illustrated by Richard Stevens. I think there are also tcp client and tcp server examples in the netburner programmers guide. But you need to get familiar with the general concepts first.

I think i understood the networking concepts, the examples in Netburner guide. I have the following problem:

I have one development board and two NB core modules, I believe i can connect only one core module to board. How should i be connecting another NB core module. Networking is the next step once i get the two core modules running (I have programmed them separately). Is it possible at all to have two NB modules running on same development board.

Rahul

I would buy another dev board. They are cheap, and you won't damage your module by trying to hack wires together.

Do i run into risk of damaging the core modules by shorting their J1 and J2 connector pins to dev board. Is it is a normal practice to have two separate development boards in case i would like to interact between these two embedded computers.