Hi.
I have a BLDC kit with LM3S8971. While measuring the signals around the board I burn out the uC and I replaced with another one.
To program I used a JTAG parallel cable with the H-JTAG software. This works fine. I program the 'boot_eth' to the flash base adrress and the 'qs_bldc' to the 0x1000 address of the flash.
The 'run Led' it's blinkg and pressing the DEMO switch the motor starts to rotate, so the program is runing.
The problem is when I try to connect over ethernet to the BLDC-GUI application to communicate with the board. I don't know why this is not working. The yellow LED of the ethernet connector it's ON (with the cable connected) and the green LED turn ON sometimes too.
Can anyone help me solving this problem?
As the uC is a new one the I don't have the flash parameters programmed, as it says at the memory Layout in the User Guide... Could this be the problem? If yes where can I get those parametres?
Let's start out with the obvious red flag... you said you burned out the original MCU. That cannot be ignored! Are you sure that other components on the board are not damaged? Which pins were you probing when you damaged the device? If there was a short, perhaps something else was damaged on the board.
Assuming everything else is OK, the first thing you need to do is program a MAC address into the device. If you use a debugger, changes are that it is skipping the Ethernet steps since the default MAC address is FFs. Even if you don't have flash parameters programmed, you should still be able to communicate with the board.
Thank you for your quick reply.
I think that is the problem. If the MAC address it isn't correct ythis won't ever be configurated obver the LAN.
I thought that one of the paramters would be the MAC address, so if I don't have it defined the uC would never communicate.
How can I define the MAC adress? How would the application 'bldc_eth' & 'qs_bldc' (together) work with this kind of problem?
Basic networking.. everything needs a unique address. If the board doesn't have a MAC assigned, the application won't initialize the interface. The correct way to get a MAC address is to request a block from the IEEE, but for testing purposes, you can probably just make up a number that is not all FFs.
Sorry but, I was out off office in the last days..
I also think that the problem is the MAC address as I told you.
In that way I would like to have all the parameters to define the MAC address. Can you tellme that information?
The informaation of my BLDC Kit is:
Opt Item: LBL 242A (L) TO:1120
(31T) LOT: 000624CTU
(4W) TKY (1T): 0029682ZAF
After that can you tell me how can I send those parameters to the MCU.
Best Regards.
Carlos Costa
I don't know what all of those numbers you listed there are...
You obviously wiped away the factory programmed MAC addresss, and there is no way of getting that number back. Like I said, for testing purposes, you can make up any number that is not all ff's. If you want more information about what a MAC address is, try doing a search on Google. I cannot give you a new MAC address because those are distributed by IEEE.
Ok.
In that way, how can I change the MAC address to be able to comunicate with BLDC-Kit?
What I need is to comunicate with the BLDC kit and change the motor speed.
Can I have a Serial communication with a PC? If yes, can you teel me the comands protocol?
Beste regards,
In the last time I got the MAC and an IP addr, using the BLDC-GUI.
To do that I must press the DEMO bottom on the board and the software qs-bldc load the DEFAULT_IPADDR (not DHCP).
When I start the BLDC-GUI it founds the BLDC board with IP-169.254.89.71 and with the MAC-20:C1:00:00:20:C1.
What should I do to have the board working with DHCP?
thanks.
You can try to implement a serial interface by starting with the ui_serial.c/h files from one of the other RDKs (like the stepper). The command sequence is in the documentation, under the Ethernet Interface section. The same command protocol is used for all interface types.
If you hold the DEMO button for a couple seconds while starting up the board, you will force it into DHCP mode.