Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: Problems with i2ceth

Problems with i2ceth 5 years 2 weeks ago #317

  • psycho
  • psycho's Avatar
  • Offline
  • New Member
  • Posts: 5
  • Karma: 0
Hi.

I have problems with the i2ceth on my DX1 board. I can upload a firmware via tftp to address 192.168.97.60 with success
tftp> connect 192.168.97.60
tftp> put BTnicEmb.hex
Sent 324963 bytes in 13.8 seconds
But I'm not able to ping the device nor to connect to the web interface by pointing my browser to http://192.168.97.60. I tried the firmware versions 2.0.1, 2.0.2 and 2.5.1 with no success.
The left LED oft the ethernet port is always on (it flickers 3 times on start up). The left LED stays dead. The Ethernet status is blinking all the time.
Im connecting with an iMac (Mac OS X Mavericks).

Do I miss something? Any help is appreciated.

Regards,
--Bernd
The administrator has disabled public write access.

Problems with i2ceth 5 years 1 week ago #318

  • psycho
  • psycho's Avatar
  • Offline
  • New Member
  • Posts: 5
  • Karma: 0
One addition: My latest testing showed, that DHCP works as well, but ping or http to the assigned address fails.
The administrator has disabled public write access.

Problems with i2ceth 5 years 1 week ago #319

  • adam
  • adam's Avatar
  • Offline
  • Administrator
  • Posts: 210
  • Thank you received: 19
  • Karma: 5
That address 192.168.97.60 is only used during boot as a static IP for the purpose of fimware upload. Once the i2ceth nic is fully booted, it grabs a DHCP address from your network. You can use the discover tool avaliable for windows if you are running a windows machine. Otherwise, you will need to use a tool like nmap to scan your network.

The windows discover tool is here:
www.brewtroller.com/customIDE/Microchip%...net%20Discoverer.exe
____________________________________
Adam Shake
Owner - BrewTroller
The administrator has disabled public write access.

Problems with i2ceth 5 years 1 week ago #320

  • psycho
  • psycho's Avatar
  • Offline
  • New Member
  • Posts: 5
  • Karma: 0
Hi adam.

Thanks for your help. DHCP seems to work (according to my router), but the assigned IP address does not respond to ping or http queries. I checked the arp table of my macbook. It shows something like this:
arp -n -a
? (192.168.178.23) at (incomplete) on en0 ifscope [ethernet]
? (192.168.178.1) at 24:65:11:63:ea:b9 on en0 ifscope [ethernet]
...

The address 168.192.178.23 is assigned to the BrewTroller by my router via DHCP. I assigned a fixed DHCP-address by binding the IP-adress to the MAC address of the BrewTroller.

I will try to reset this assignment when I'm next time at home (by tomorrow).

Unfortunately I have no windows machine in my network. Trying to run Discover.exe in my VM did nor discover an i2ceth device (bridged mode). I will see what nmap can do for me. I already tried a network ping in the DHCP subnet w/o answer of the BrewTroller:
ping 192.168.178.255

What wonders me, is that no LED is flickering during the successful upload of the i2ceth firmware. How can I debug the i2ceth interface by observing BrewTroller's LED behavior or logging? Can you give me some hints?

Regards,
--Bernd
The administrator has disabled public write access.

Problems with i2ceth 4 years 11 months ago #324

  • adam
  • adam's Avatar
  • Offline
  • Administrator
  • Posts: 210
  • Thank you received: 19
  • Karma: 5
You should see some lights going when the firmware updates. Are you setting a static IP on your computer to match the boot IP of the NIC?
____________________________________
Adam Shake
Owner - BrewTroller
The administrator has disabled public write access.

Problems with i2ceth 3 years 9 months ago #522

  • bfoot307
  • bfoot307's Avatar
  • Offline
  • New Member
  • Posts: 4
  • Karma: 0
I have a similar problem to pyscho's. I had problems with the i2ceth v1.1 firmware, and have successfully (I think) flashed to the newest version of the BTnicEmb.hex file from GitHub. However, when running the discovery tool included with the GitHub files, the i2ceth is not pulling from my internal DHCP. I am currently using a 192.192.xxx.xxx scheme, and BTNICEMB is pulling an IP of 192.168.0.199. Through all my playing (reflashing, resetting, rebooting) I have got it to pull from my IP scheme ONCE, but have never been able to pull up a page to verify what firmware version I am even running....if any.
Just learning the ropes with all this with my recent purchase of a brew system with brewtroller dx1 board. ANY help is greatly appreciated. Would love to be able to get the brewtroller.com/live working so I can upload recipes and get rolling!

--Chris C.
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Time to create page: 0.093 seconds
Follow via Facebook Follow via Twitter

Login