Just wanted to update for completeness.
Got my plug working again using the Installer v1.0, while running from
Ubuntu. Several people did mention that while running from windows they ran
into issues as well. Apparently the FTDI drivers (at least on Windows 7)
isn't exactly reliable from what I can
Newer kernels don't use /dev/ttyUSB0 for JTAG. It is used for serial
access and no /dev/ttyUSB1 will appear.
Check out
http://www.openplug.org/plugwiki/index.php/Setting_Up_OpenOCD_Under_Linux
On Thu, Mar 11, 2010 at 11:29, Lluís Batlle wrote:
> 2010/3/11 Shiva Bhattacharjee :
>> Is it necessar
On 3/11/10, Martin Guy wrote:
> You can test for that by going
> # echo 5 > /proc/cpu/alignment
> and running your test again. On unaligned access the program will then
> die with SIGBUS instead of merrily going on its way with corrupted
> values.
Note that QEMU does not emulate either the
On 3/10/10, Luke Kenneth Casson Leighton wrote:
> ... where is all this documented?
>
> has anyone actually done this - documented and automated e.g. how the
> debian-armel port was created, when previously there was only the
> debian-arm one?
There is a huge difference between recompiling
(Add debian-embedded@ as Neil was suggesting)
Hello,
2010/3/10 Jonathan Wilson :
> What I'd like to know is how do I build a distribution entirely from
> scratch/source like the pro's do.
linux from scratch is a great reference.
> ie. Get all the debian source for the latest arm port (just the
On 3/7/10, Iustin Pop wrote:
> >So it looks like what we're actually seeing here is one bit of corruption.
> >
> >I still strongly suspect a compiler bug. Probably the compiler's emulation
> >of 64-bit arithmetic is broken in some way.
>
> First, are you aware of 64-bit arithmetic issues on
Hi,
after the (usual) long delay I've managed to fight my jet-lag with a good
coffee and I've tested the image Arnaud provided me with :)
The steps I've followed are:
1. halt the startup sequence at Redboot> prompt with CTRL+C
2. *RedBoot> fis load ramdisk.gz*
3. *RedBoot> load -r -v -h 192.168.1.
2010/3/11 Shiva Bhattacharjee :
> Is it necessary for me to use the same mini-usb cable that came with the
> sheevaplug? It seems my host machines ( windows, linux, mac) all recognize
> the sheevaplug but when I try connecting to the serial port I get
> nothing...
>
> I think I am running into
I threw my cable away months ago after big problems with it
disconnecting serial access. Now I just use any mini-USB cable lying
around.
On Thu, Mar 11, 2010 at 09:18, Shiva Bhattacharjee wrote:
> Is it necessary for me to use the same mini-usb cable that came with the
> sheevaplug? It seems my h
Is it necessary for me to use the same mini-usb cable that came with the
sheevaplug? It seems my host machines ( windows, linux, mac) all recognize
the sheevaplug but when I try connecting to the serial port I get
nothing...
I think I am running into the same problem with the installer as wel
10 matches
Mail list logo
