It has been a while since I have dealt with that board. That was a while ago.
Gerald On Sun, Nov 23, 2014 at 11:57 AM, n2vdy <[email protected]> wrote: > Beagleboard rev c2 has 256MB of NAND flash. Normal sequence is to load MLO > and u-boot from flash. If you hold the user button when powering up it then > loads MLO and u-boot from SD. > > > T-Mobile. America's First Nationwide 4G Network. > > > ------ Original message ------ > *From: *Gerald Coley > *Date: *11/23/2014 12:21 PM > *To: *[email protected]; > *Subject:*Re: [beagleboard] Is my Beagleboard dram dead? > > On the the BeagleBoard we booted form SD. Not NAND. So I am not sure > where the support for booting from Flash comes from. We only implemented > Flash (eMMC) on the BeagleBone Black. > > Gerald > > On Sun, Nov 23, 2014 at 9:55 AM, 'David Batzle' via BeagleBoard < > [email protected]> wrote: > >> Which is why I was thinking maybe a bad flash to NAND had caused a >> problem. The DRAM is definitely not working now. >> >> When x-loader goes to load u-boot.bin off of MMC, it passes a file name >> to a function in fat.c. The function copies the filename into DRAM and then >> parses the copy of the name. It never finds a name because the contents of >> DRAM are zeros. If I modify the function so that the copy of the filename >> and the contents read from the MMC card are both in SRAM, then I get a >> message of loading u-boot.bin from MMC but then it locks up. >> >> My next step I am planning to modify x-loader so it can properly wipe the >> NAND clean. I just didn't want to waste my time if a bad flash would not be >> a possible cause. >> >> Thanks. >> -------------------------------------------- >> On Sun, 11/23/14, Gerald Coley <[email protected]> wrote: >> >> Subject: Re: [beagleboard] Is my Beagleboard dram dead? >> To: "[email protected]" <[email protected]> >> Date: Sunday, November 23, 2014, 10:31 AM >> >> If it booted the >> Always image, then the DRAM is working. Code executes out of >> DRAM. >> Gerald >> On Sun, Nov 23, 2014 >> at 9:04 AM, 'davidcb' via BeagleBoard <[email protected]> >> wrote: >> I have a Beagleboard Rev. C2. I fired it up after >> not using it for a couple of years. It booted the Always >> Innovating image I had installed. I decided to try to put >> Debian on it. I used the flasher script to try to update >> u-boot (thank you RobertCNelson). U-boot would lock up just >> after printing out DRAM on the serial console. >> I tried a bunch of different things and managed >> to get the flasher MLO flashed to the NAND but nothing else >> got flashed. >> I had been have better luck with x-loader so I >> downloaded x-loader source version 1.5.1. It correctly >> identifies the revision of the board but will not load >> u-boot. Hacking up x-loader source I have been able to >> figure out that anything that gets loaded to the DRAM gets >> read back as all zeros. >> My question is, is there anything that could >> happen in a bad write to NAND that would interfere with >> DRAM? I had already hard coded the memory configuration in >> x-loader so it was not relying on the configuration values >> in NAND. I am thinking the DRAM is probably >> bad. >> >> >> >> -- >> >> For more options, visit http://beagleboard.org/discuss >> >> --- >> >> You received this message because you are subscribed to the >> Google Groups "BeagleBoard" group. >> >> To unsubscribe from this group and stop receiving emails >> from it, send an email to [email protected]. >> >> For more options, visit https://groups.google.com/d/optout. >> >> >> >> >> -- >> Gerald >> >> [email protected] >> http://beagleboard.org/ >> >> http://circuitco.com/support/ >> >> >> >> >> -- >> >> For more options, visit http://beagleboard.org/discuss >> >> --- >> >> You received this message because you are subscribed to the >> Google Groups "BeagleBoard" group. >> >> To unsubscribe from this group and stop receiving emails >> from it, send an email to [email protected]. >> >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Gerald > > [email protected] > http://beagleboard.org/ > http://circuitco.com/support/ > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Gerald [email protected] http://beagleboard.org/ http://circuitco.com/support/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
