ahhhh, so I have to have a console attached WHILE I RUN THE OCD MACRO?
That seems next to impossible with the test points, without actually
soldering. My gumstix-jtag board is worthless then
On 3/1/06, Craig Hughes <craig@...> wrote:
> The OCD macro doesn't actually flash the new u-boot, it merely loads
> it to RAM then executes it. To install it, you then have to use the
> in-RAM u-boot to load a new u-boot image to somewhere else in RAM,
> then use u-boot to copy that image to flash (after the protect off/
> erase 1:0-1).
> If you can run the OCD script successfully (ie it's not popping up
> some error message, and it gets all the way through the SREC load),
> then everything is probably good on the 'stix -- when the in-RAM u-
> boot runs, you should see its output on the serial console. If you
> see the u-boot splash there with the info about detected RAM and
> flash, then you should be good to start the process of copying u-boot
> to flash.
> On Mar 1, 2006, at 4:23 PM, Nik Martin wrote:
> > can anyone give me some tips on getting a new u-boot flashed via JTAG?
> > I'm not having much luck with the wiki docs - i just fetched the
> > latest buildroot, built a 1.1.4 u-boot, flashed it using JTAG + OCD
> > Commander macro, and still get nada on the console upon reboot. Are
> > there some undocumented steps required? some tin-foil applied in a
> > strategic location? amything? Is there a OCD command that will help
> > me determine if my gumstix is working properly? I can list the
> > configuration regs, and they actually spit something out, so I assume
> > my CPU is running, but that's all I know.
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
> that extends applications into web and mobile media. Attend the live webc=
> and join the prime developer group breaking into this new coding territor=
> gumstix-users mailing list