AVR RAVEN Technical Discussion

Go To Last Post
115 posts / 0 new

Pages

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Without looking at the board(s), and also working from memory, IIRC the '86 is QFN-only and the boards are TQFP?

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It could be as simple as the part they used was in production at the time they designed the device and the cheaper part wasn't. It would take a large price difference to redesign and test the board for such a short run product.

Smiley

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

It could be as simple as the part they used was in production at the time they designed the device and the cheaper part wasn't. It would take a large price difference to redesign and test the board for such a short run product.

Smiley

But the two chips are identical, except one has the host hunk of the USB controller removed. All the other characteristics are the same.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:
Can someone please satisfy my curiosity before I go stir crazy? The Raven dongle uses an AT90USB1287 and not a AT90USB1286. Why would Atmel put the more expensive part on the board when the cheaper part could be substituted instead, with the only difference being the lack of a host mode which can't be used anyway?

A chip manufacturer has completely different criteria than what you perceive from the customer point of view. Sometimes you get weird situations like the less expensive chip is in greater demand, meaning you would have to upset the production schedule to make additional chips for your own product. This is just one possible way that a slightly more expensive retail price chip might actually be cheaper for ATMEL to use in their own product.

There are other mysteries, like how a new retail DDR 512 Kb memory stick can sometimes cost more than a DDR 1 Gb memory stick :wink:.

Besides, if you plug the AT90USB1287 RZUSBSTICK stick into a simple powered HUB, couldn't you then use the OTG features with your own software? In this case it looks like the OTG host mode makes the RZUSBSTICK stick more versatile.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Dean,

When designing the RZUSBSTICK we had several request for host capabilities from companies making industrial sensors. They are usually equipped with a device interface, and it was natural to use a host capable device to accomodate these requests. Even though, from an USB point, it is against the rules regarding connectors etc. :-) . Anyways, for them it was ideal just to plug a RZUSBSTICK into their product as an add-on.

So now you know why...

-Vemund @Atmel Norway

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I tried upgrading my Raven's firmware with the latest version on the Atmel site using the over the air programming method. Now the Raven displays the message "WAIT FOR M1284 BOOT LOADER"

According to the documentation that came with the firmware You can restore the the Raven to default firmware if you jumper USERIO1 to USERIO2 and power cycle. I have tried this and the Raven never tries to write any firmware. It just goes back to "WAIT FOR M1284 BOOT LOADER" I uploaded the backup firmware prior to flashing with the new version so the backup should be there.

Has anyone been able to restore a Raven by jumpering USERIO1 and USERIO2? I have a feeling I will need to buy a programmer now that I've bricked it.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

When designing the RZUSBSTICK we had several request for host capabilities from companies making industrial sensors. They are usually equipped with a device interface, and it was natural to use a host capable device to accomodate these requests. Even though, from an USB point, it is against the rules regarding connectors etc. Smile . Anyways, for them it was ideal just to plug a RZUSBSTICK into their product as an add-on.

So now you know why...

Ah ha! You're right that it would completely invalidate the USB spec for connectors, so I hope that the manufacturers put warnings on their products that the connector in non-standard USB and might cause problems if used with anything else. Curiosity sated.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

HI All i am trying to make simple network

I am leaving the USB RAVEN code as it is, but trying to modify the RAVEN to see what i can do.

What function should i be calling, should it be the 802.. or just the command interface.

I dont understand, how does the AVR 1284 know which function are being called from the AVR 3290, i cant manage to work that out.

There is Zigbee files as well, but does this just implement a tree topology.

Dj

Thanks

Regards

DJ

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

what's going on now among Raven users?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well the contiki ipv6 link with Vista is looking good http://dakx.com:8080/jackdawupti... after some issues with Vista wanting to use it for ipv6 encapsulated file sharing and discovery packets. Had to add robots.txt to each webserver to keep Google, MSN, Yahoo from indexing them once a day. Since they already know about them I might as well post the links again Koko http://dakx.com:8080 Edgar http://dakx.com:8081 Lenore http://dakx.com:8082 and BigBird http://dakx.com:8083

Next step is to get the battery chargers status online using TWI to the 1284p.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm stalled-out on the issue that each time messages come in to the PC from the Raven, the Wireless Server crashes with an illegal memory access. It displays messages saying the info came in, e.g., query temperature, or other message, but then it gets a memory access exception error.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I got that message occasionally on Vista but never on XP. Did you install from AVRWirelessSetup.exe 5/19/2008 and were there any problems installing the USB driver? If you haven't already I'd try reflashing everything with the .a90 files included with the AVR2017.zip download. I don't think it likes the as-shipped firmware much.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Sorting through my pile of connectors I found that an ATA ribbon cable fits on the STK500 JTAG adapter (included with the newer kits), which connects to PC2-PC7 on the EXPAND0 header. I stripped out the wires from the other end and soldered them to a Raven as follows

   Raven        Ribbon     STK500
Gnd     J201-9    1       1   Gnd
PC1     J201-2    2      23   PC7
EXT_PWR J201-10   4      22   VTGT
PC0     J201-1    8      24   PC6
PC2     J201-3    6      25   PC5
PD3     J202-4   10      26   PC4
                 36      27   PC3
                 40      28   PC2

The Raven will happily take whatever target voltage the 500 supplies, I set it to 5.1 volts to power an onboard Tiny85. Jumpering PC4 to TXD sends the Raven debug output to the Spare1 RS232 port. The Red/Black jumper below connects the TWI lines from the Raven (PC6-7) to the Tiny85 (PB0-2) to make the Raven an AVR311 slave. I will be driving it with multiple masters so have another Tiny85 boost charger connected for testing.

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm in the same position as devroot. When I look at the ISP connector for the 1284 processor, I don't find vcc and ground on pins 2 and 6. My AVR Studio recognizes the 3290 on its ISP port. I seem to have a 1 node network.

The largest known prime number: 282589933-1

Without adult supervision.

Pages