Shop OBEX P1 Docs P2 Docs Learn Events
Prop + ethernet functionality — Parallax Forums

Prop + ethernet functionality

Erik FriesenErik Friesen Posts: 1,071
edited 2009-02-25 02:59 in Propeller 1
I am in the process of trying to grasp embedded ethernet. Can someone that has done this on the prop tell me if the prop + enc28j60 can do something like the link below?

demo.netburner.com:81/INDEX.HTM

Comments

  • Mike GreenMike Green Posts: 23,101
    edited 2009-02-24 20:56
    Look at the description and open source code for YBOX2: www.deepdarc.com/ybox2/
  • Mike HuseltonMike Huselton Posts: 746
    edited 2009-02-25 02:13
    I purchased a Ybox2. Ships with all parts, works well. Good suggestion, Mike.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    JMH
  • Erik FriesenErik Friesen Posts: 1,071
    edited 2009-02-25 02:45
    I am still in the pre understanding stage. Is this setup capable of the above mentioned demo?
  • Mike GreenMike Green Posts: 23,101
    edited 2009-02-25 02:54
    No.

    There's not a huge amount of space for webpage data. You could probably do everything but the video. I think the EEPROM can be replaced and could be upgraded to a 128K byte EEPROM. That might let you serve more information from EEPROM.
  • Erik FriesenErik Friesen Posts: 1,071
    edited 2009-02-25 02:58
    Thanks Mike. That is the answer I was looking for. Sometimes a person has to ask dumb sounding questions to get a grasp of things. I wouldn't need the video anyway.

    Does the prop interface run into a spi bottleneck problem?
  • jazzedjazzed Posts: 11,803
    edited 2009-02-25 02:59
    I've used a variation of the ybox httpd code to serve javascript. My main problem was the number of times the server stopped because of too many server hits resulting in a "DOS" or Denial of Service. Harrison has updated his network drivers since my experiments, so there may be a fix for DOS. The gif and other data could be loaded onto SDCARD from the "http client" code although I'm not sure if the client and server will both fit in propeller memory simultaneously. One could easily arrange to reboot periodically to do updates. The ybox example uses a 64KB eeprom for storing parameters. Added: the server is quite slow using existing SDCARD SPI code.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    --Steve
Sign In or Register to comment.