• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Hardware and U-Boot firmware / Hardware / Re: 110 or 220 VAC US Version? on: February 23, 2010, 10:09:37 PM

The power supply will be fine. We have a number the 110-220V plugs here in Australia running on mains of 230V 50 Hz.

The third pin is for Earth Ground which the plug does not use. (Double insulated)

You can remove the supplied mains pins and use a power cord (instructions some where else on this forum)


2  Hardware and U-Boot firmware / U-Boot stuff / Re: Can't saveenv bootwait. on: April 21, 2009, 01:42:27 AM
We have had the best success with the XBEE modules from digi.com.

For prototyping sparkfun is a great source http://www.sparkfun.com/commerce/categories.php?c=111

For production quantities buy from the digi distributor.
3  Hardware and U-Boot firmware / U-Boot stuff / Re: New U-boot features on: April 21, 2009, 01:36:16 AM
Request that U-BOOT respects bootdelay env variable. To allow the uart to be used with other devices such as ZIGBEE, GPS.

Or U-BOOT supports  CONFIG_AUTOBOOT_STOP_STR  to allow the definition of a string that will not conflict with the attached device.
4  Hardware and U-Boot firmware / Hardware / Re: Broken Serial Console (hardware issue) and fix. on: April 21, 2009, 12:49:11 AM
Pins  J4 1-4 are all +3.3v
Pins  J5 1-4 are all +5v

Pins J4 1-3 are all GND
Pins J5 1-3 are all GND.

So the solder bridge should be OK. I suspect it was the Pins on the board that connects the flex cable to the motherboard.

I had a few problems with that. Heating the pins and pushing them down fixed it.

Did you pry off the flex cable connector board?
5  Hardware and U-Boot firmware / U-Boot stuff / Can't saveenv bootwait. on: April 20, 2009, 11:32:49 PM

I want to use the UART to connect a ZIGBEE module. unfortunately the ZIGBEE module can output data at any time including during the UBOOT boot delay prompt. So I planned to set bootdelay 0 and burn a new uboot image if I ever needed bootdelay > 0

This has raised two problems:

1. setenv bootdelay 2 and saveenv - does not save after reboot. Other environment vars such as serverip do save after reboot.

2. It would appear that the uboot environment is not part of the uboot bin as the variable are preserved after writing a new image via openocd.

Could anyone shed a clue as to why I cant saveenv bootdelay and how I can read and write the u-boot environment via openocd?

Pages: [1]