View Single Post
Old 08-28-2012, 08:48 AM   #112
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 knc1 View Post
@GM : I PM'd you the access details for the "my k3 is broke" kloud.
Because this "RAM Kernel" code can use all of the opinions and consulting it can get while at the same time respecting Freescale's "don't publish this" license.

This way everyone can be looking at the same code and reference materials.

This source (1.71) handles the i.MX 25, 27, 31, 32, 35, 37, 51 and 53 (no mention of the 503 - but maybe it only needs a loader script).

I plan to start by pulling the existing client code (device_program/*) out of that VC project build system and getting it to build like any other Linux glob of code.

Last edited by knc1; 08-28-2012 at 09:00 AM.
knc1 is offline   Reply With Quote