View Single Post
Old 10-18-2012, 01:09 PM   #4
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by geekmaster View Post

EDIT: Because the upgrade to 256MB uses a power of 2 for the row and column address in the RAM chip(s), you probably do NOT need to add any additional address line in this case. You may also need to modify the u-boot bootloader (and perhaps other code) to initialize and use the extra RAM.
The U-Boot code for the DX-2.5.8 firmware that I recently read has both 128Mbyte and 256Mbyte initialization available in the source code.

But if I recall correctly, it is a build-time configuration option - -
If my memory is correct, it would have to be rebuilt.

On the bright side - it is easy (on this DX firmware) to get u-boot written into the write-protect portion of flash where it normally lives.
Its "erase flash" function un-locks, erases flash, then copies the executing copy of u-boot back into the u-boot partition(s), and then re-locks the flash write-protection.

- - - At least that is how I read it, I did not actual test it on a device to see if my understanding was correct. - - -
knc1 is offline   Reply With Quote