I just bought a Fez Panda II from an online retailer, which came in a bag with usb cord. I initially plugged the device and the LED blinks constantly. I tried connecting to the device using MFDeploy but the firmware is not recognized(USBizi). After reading some more and watching the tutorial, I figured I would need to install the firmware. I downloaded the Tera Term software as well as the 32bit driver executable. I tried setting up the boot loader mode, and was able to one time get windows to ask for a driver. It automatically loaded the NETMF driver but not the boot loader. Now everytime I try to use Tera Term I dont get the com port I need. If I use what available com 3 it just echoes my input. How can I fix this, or start over
Welcome to the forum! A good place to start is the Beginner’s Guide, Getting Started section. The Panda II comes with a default LED blink app on it, so that is normal. The important part is to make sure the firmware you install on the Panda matches what you installed on your PC. THe best bet is to download the latest firmware (which may or may not be on your board already). Also, when you power up the Panda, you need to have the bootloader button depressed for a few seconds to get it ready to upload firmware. The USB drivers need to be installed prior to doing this.
There is a lot of information on this site under Downloads & Tutorials to get you going. Good luck and have fun.
Thank you for your quick response, I am still having issues with the unit. I tried connecting an external power supply to the unit as well as the usb cable, going through the boot loader sequence I was able to load the boot loader interface. It still does not recognize the port when connected. Once the boot loader driver was installed, I disconnected the board and reconnected and then I received a prompt to instlall the GHI debugger interface. I pointed towrds the GHI NETMF folder and ran through that installation. At the end it says the driver was installed but may not function (code 10). I am still unable to connect use tera, fezpanel or mfdeploy. Where do I go next, this has taken a bit of time.
There is no ‘boot loader’ to install. This makes me think you are just missing having the correct drivers installed. Go to the downloads section and grab the drivers … heck here are the links:
Install the correct drivers for your computer and try again. When the FEZ is plugged in without the MODE button held down it will show up as a debugable NETMF device in device manager. When you plug it in with the MODE button held down it will show up as a COM port.
Like I suggested before, follow the exact steps and when you are stuck tell us at what point you are stuck. At this point we have no idea where you are or what is going on so it is impossible to help you.
Thank you again for your assitance. At this stage I am just trying to communicate on any level and am unsuccessful. I have followed all the steps, installed the 32 bit driver installer and it is still not recognizing USBizi in MFDeploy. So from that I go to lower level Tera, I have installed the driver and put into boot mode. I dont get the com port to communicate, so at this point I have no communication.
Sorry this i not working for you but I still think you are not following the steps.
Let me step you through it:
open your PC’s “device manager”
connect your FEZ to your PC using the included USB cable. Connect it directly to the PC. Do not use any HUBs.
What do you see added to “device manager”? It is going to be “NETMF Debug interface” or it will be a new COM port or the device manager will simply show an error in the device.
I have tried this on two computers running XP. I open up device manager and observe any hardware changes while connecting device. It does not show any change on either computer when connected directly through USB. I am specifically looking at com port but I also don’t see any changes anywhere else.
The blinking LED is a test program loaded at manufacturing process so this means the board is functional and it is loaded with firmware and application. I would try a different cable before doing anything else, since you already tried a different PC.