Developer FAQ

From The Neuros Technology Wiki

Jump to: navigation, search

Neuros Technology | Products: LINK, OSD, Tablet | Developers

Contents

Getting Started

What equipment do I need to hack the Neuros Products?

  1. A PC with Linux. There are many ways this can coexist with a windows installation on a PC, dual boot, QEMU, colinux, or easiest of all the Virtual Machine but you'll need some form of Linux in order to "Hack the Duck."
    • Any distribution should do. The China team uses Fedora Core 4, but the Neuros community uses Ubuntu, Debian, Gentoo and others.
  2. A Neuros Linux Product, the first of which is the Neuros_OSD
  3. A Null Modem adapter
  4. A USB serial adapter if you don't have a serial port.

What skills do I need in order to participate?

If you've gotten this far, you are already skilled enough.

Participation takes place in a variety of forms. To code for the Neuros hardware, knowledge of C/Assembly and Linux should be enough to get you started. When you buy a developer sample it is basically a complete working product and you will have access to updates that will bring it up to production quality right along with us. You'll have the ability to poke around at basically whatever level you want, from a simple UI tweak to a complete re-write. Of course, The earlier you get on board, the more influence you'll have on the product's development.

How can I participate?

You can join various discussions at the Developer Google Group or the User Forums. We're actually inviting you to join the entire gamma development process: both feedback and design. Tell us how to layout the buttons on the remote. Change our screen designs. Tell us what works, what doesn't work and what we need to add.

You can join Freenode IRC channel #neuros for 24/7 discussion of Neuros issues, with more focused activity during scheduled meetings. Logs can be viewed at older #neuros IRC Logs and newer #neuros IRC logs.

You can report bugs through Bugzilla. Please choose proper product version when reporting bugs.

You can directly work on the code or documentation for each project.

For a complete list of community resources, please see Getting Involved.

How can I get started?

First, pick a project, there are a number of projects to pick from.

You'll need a device too, so pick one that suits your needs and you'll have all the hardware you need to at least get started.

How can I buy the developer kit?

Being open source, the product is the developer kit. Just buy the OSD1 or OSD2 and download the source. The new Virtual Machine Environment is one of the easiest ways to start your neuros hacking adventure.

How do I access the source code?

Project source repository can be viewed at websvn. To check out code from the repository:

Are the developer boards suitable for commercial development?

Yes and No. The boards themselves are just fine and we've had lots of inquiries from interested parties, but Neuros does not support the developer boards for commercial development. At $179, we hope you can understand that we simply can't afford to. If you think your engineers can figure it out and work through the community for troubleshooting, etc, then be our guests. For most commercial applications, we recommend you talk to one of the Commerical IP providers that work with TI silicon.

If on the other hand you've got a cool hack working on the Neuros that would make a neat consumer product, well let's talk. Maybe we can help you bring it to market.

Documentation

Where can I find project documentation?

Project documentation can be found from Wiki page of each project, while README is always a good place to start if you have access to the source code.

General

What's the Big Deal? There are lots of hardware projects out there.

Neuros isn't just a community, it's a community that's integrated into the actual device manufacturer, one team, one codebase, and today that's fairly unique and something that brings a lot of advantages to hackers. For information on why this is a big deal, see Neuros and Open Source

What can I make this baby do?

Well, that's up to you, isn't it? Use your imagination. Create an embedded system to record helmet-cam video for paragliding enthusiasts. Build the Myth-killer PVR. Develop the next generation of security recorders. Build a flash-card-based video device for your medical imaging equipment. If you can dream it, the hardware's there for you to build it.

Short on your own ideas? See Developer Board Ideas.

What's currently going on?

The best answer to that is always to be found at OdNT

How does the version system work?

Neuros releases 3 type of firmware for OSD,

  • Daily Developer Release

This release includes all latest development, release may have serious bugs and this type of release is not recommended for general user, instead this is more of a testing-bed for upcoming Beta and Production releases.

  • Beta Release

This release includes some of the latest development and has been extensively tested and verified by internal test team. It is a release candidate for upcoming Production release. Release may still contain bugs but in general is ready for daily use for early adapters.

  • Production Release

This release has been fully tested and verified with extensive tests from both internal team and field users. Release is ready for production and is ready for daily use for all level users.

Beta & Production Release Version

Both Beta and Production release version comes in the form of 'A.BC-D.EF-GH.IJK', where,

  • 'A.BC': the hardware version,
  • 'D.EF': the firmware version,
    • D: major firmware version
      • 1: for TORFU series releases (Nano-X based)
      • 2: for AZ series release (Qt based)
    • EF: minor firmware version
  • 'GH': field release sequence number
  • 'IJK': release timestamp
    • 'I' indicates year,
    • 'J' indicates month,
    • 'K' indicates date.
  • Example:
    • 3.33-1.74-01-832: TORFU release 3.33-1.74 on March, 2nd, 2008.
    • 3.33-2.05-02-843: AZ release 3.33-2.05 on April 3rd, 2008.

Daily Developer Release Version

Daily developer release version comes in the form of 'A.BC-D.EF', where,

  • 'A.BC': the hardware version,
  • 'D': developer release signature code
    • x: TORFU developer releases
    • y: AZ developer releases
  • 'EF' developer release time stamp
    • E: month
    • F: date
  • Example:
    • 3.33-x.53: TORFU daily developer release released on May 3rd.
    • 3.33-y.93: AZ daily developer release released on September 3rd.

For historical reason, Neuros I & II have separate firmware and hardware versions.


This wiki is user updated and the information here cannot be considered official Neuros communication

Personal tools