|
Hey guys. I've been following this list with some interest for a while now. I work for a university small satellite program and we use a TS-7250 as one of our command & data
handling computers. Anyways, I've managed to bork the bootloader. I've done this before, and I thought it was because of my custom 2.6 kernel not having the correct flash partition mapping- i.e.,
something was getting overwritten. I thought I had fixed the problem, but apparently not. I've used serial blaster before to restore the redboot image (that's what always seems to get corrupted). I modified the serial blaster code to drop me into minicom immediately after the
redboot image was sent, so that I can interrupt the boot process and upload all the important stuff all over again. Unfortunately, minicom doesn't seem to wish to work any more. I just updated my linux machine that I use for this (Ubuntu 10.04) and minicom no longer catches commands via Ctrl-A, even though it is configured to do so. Has anybody had similar issues to this, and do you know how to resolve it?
Additionally, does anybody know what the *correct* flash mapping for the TS-7250 is? I have 128 megs of NAND flash. The page size is 2k, I believe. My ultimate goal with this is to be able to get my 2.6 kernel to boot from the flash and not NFS, and maybe even to get a 2.6 vmlinux image in flash so I don't have to use bootload. Any comments would be appreciated; I've been going through the mailing list archives, and so I feel pretty confident that I can get 2.6 running off flash, I just need to get my bootloader restored first.
Thanks, -Pat
__._,_.___
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe __,_._,___ |