[Tim Scott]

Just wanted to post a quick update. I’m able to successfully run v2012.10 using the patch changes Jesse linked above. I can attach a USB thumb drive and download a file to that using USB / fatload commands. I was able to re-flash my MT100 using this and things are working well so far.

I seem to have taken a step back trying to run the latest version of U-boot, however. I applied the same patch changes to v2015.01-rc1 and the boot process appears to get hung up before it hits the prompt:

## Starting application at 0x21400000 …

U-Boot 2015.01-rc1-dirty (Nov 17 2014 – 10:30:52)

CPU: AT91SAM9G20
Crystal frequency: 18.432 MHz
CPU clock : 396.288 MHz
Master clock : 132.096 MHz
DRAM: 64 MiB
WARNING: Caches not enabled

At this point things hang indefinitely. Since I’ve got v2012.10 working, I can proceed with what I was originally working on. Still, it would be nice to know what the hang-up is for the latest version of U-boot. If I get anything figured out, I’ll be sure to post it here. If anyone has ideas for troubleshooting, I’d be interested to hear them.

Thanks!
–tim

[Tim Scott]

Does anyone know if it is possible to recover an incorrectly programmed flash using the MT100EOCG-DK? I found the link below, but it applies to a different board altogether:

Home

My board is working fine at the moment. I’d just like to know how to resolve a bricked unit in case something goes bad with my u-boot update.

Found the answer in S000516C. Looks like I just need to short out R108 on the MT100 board and run the ATMEL software. Sweet!

Thanks,
–tim

• This reply was modified 10 years ago by Tim Scott.
• This reply was modified 10 years ago by Tim Scott.

[Tim Scott]

Yep, that makes sense. For test purposes, I think loading in the .bin to RAM and running things that way will help prevent from bricking accidentally bricking the unit.

FWIW, I have the first pass of U-Boot v2014.10 working on the board. Ethernet doesn’t appear to function yet so I’ll be digging into that today.

–tim

[Tim Scott]

Sweet. I recompiled U-boot v2012.10 with the patch, but changed then CONFIG_SYS_TEXT_BASE to 0x21400000 and was able to load / execute the .bin file just fine. I plan on investigating whether or not I can get the latest version of U-Boot running in a similar manner.

–tim

[Tim Scott]

Hi Jesse,

I think I may be deploying my u-boot.bin file to the target incorrectly. I can’t load it at 0x23F00000 because that is where the existing u-boot resides, so it freezes if I try to do that. If I load things at 0x21400000 and follow that with a “go 0x2140000” I encounter the freeze as mentioned in my original post. I’m guessing this may be due to the CONFIG_SYS_TEXT_BASE setting.

How did you test your u-boot build?

Thanks,
–tim

[Tim Scott]

I haven’t messed with the GPIOs so I haven’t verified them. GPS works fine — either through Minicom or the recompilation of Venus GPS.

–tim

[Tim Scott]

I similarly tried to get things to run using VirtualBox running an image of 11.04. For me, I couldn’t even get past the pre-requisites step… apt-get failed miserably due to certain packages no longer being available on the Ubuntu servers. I rolled things back to an image of 10.04 LTS and was able to finally get the necessary pre-reqs installed and bitbake to work.

That said, I’m now using buildroot instead of bitbake to create my kernel and file system images. If you’re interested, I created another thread in the “MultiConnect OCG” forum about that.

Cheers,
–tim

[Author]

Posts