We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
The manual says that if p0.14 is low while reset is low, forces on-chip boot-loader to take over control of the part after reset. However, when I connect this pin to ground, while the user code is executing (Blinky), the program stops! When I connect it to the 3.3V pin on the motherboard, Blinky starts running again! And all this time reset is never low. Is this supposed to happen? It doesn't seem so according to the flowchart in the manual.
Hi Per,
Many thanks for your help.
At that moment, I just wanted to complain, so I did not provide enough information.
The TI/Luminary Serial-to-Ethernet Reference Design Kit consists of a S2E Module, a S2E connector board (MS2E-CKIT), and some cables.
The MS2E-CKIT board which I got, is mounted with a DB9 male connector. The DB9 serial cable which I got, is one end male and one end female. And on the PC side, the COM Port adapter is male.
S2E-RDK:male <-> male-cable-female <-> X86-PC:male
So, I used a female to female converter to connect all this stuff.
S2E-RDK:male <-> female-converter-female <-> male-cable-female <-> X86-PC:male
I did not perform any real testing, I just simply run the example project from Luminary, and it "seemed" work. (My mistake)
After suspending this project for quite a long time, recently, I wanted to do some Hello-World thing on this S2E RDK. But I didn't have enough time to read all the Luminary documentations. I did some Try and Error thing, modified the example project from Luminary, and of course, it did not work.
I can send data from PC to MCU, but can not send data from MCU to PC.
Because I did not read the Luminary documentations, so originally, I thought that, there was something wrong with my modification.
After one week debugging (also doing something else), I started to suspect that what I were facing was a hardware problem. So I tried to obtain the MS2E-CKIT schematics, and found NOTHING in the CD of the S2E RDK. But fortunately, Google brought me to the below URL.
e2e.ti.com/.../226147.aspx
The MS2E-CKIT schematics: e2e.ti.com/.../S2E_5F00_CKIT_5F00_RB.pdf
With the MS2E-CKIT schematics, and some other photos, I noticed the DB9 connector on my MS2E-CKIT board should be a female one. So I made my own female to female converter with my terrible soldering skill. After changing the wiring again and again, it worked, I can send data from MCU to PC successfully.
With the solid evidences, (It is a ready-to-run kit from TI/Luminary, we expect the quality should be good at least.) I reported to my supervisor, he is good at 8051 hardware designing and 8051 assembly programming. My supervisor did more tests and replaced the DB9 male connector with a female one.
So, we believe the DB9 connector on the MS2E-CKIT board is incorrect. It should be a female DB9 connector by design.
I am re-reading your post. So, you mean the DB9 male connector could be for another device which is not a PC?
the DB9 male connector could be for another device which is not a PC
If this is the case, then it is a mismatch with the example project and the schematics.
But yes, The most common application for the S2E module is for augmenting legacy products that contain a serial port for a configuration or control interface. Simply installing a S2E module into the legacy serial device provides instant networking capability with no major board redesign or software changes, a tiny form-factor for unobtrusive implementation, and cable lengths much longer than what is available for simple serial connections.