
Hi Austin,
On 20 July 2016 at 14:21, Gardner, Austin (GE Transportation) austin.gardner@ge.com wrote:
Simon,
Thanks for the response!
I do not have any debug facilities unfortunately, and I don't think it is a board fault either. The text base you're referring to is "CONFIG_SYS_TEXT_BASE" correct? Originally the value for this for the MPC8349EMDS board is: 0xFE000000, but the docs for our MPC8347 board says that the boot loader needs to be at location: 0xFF800000, possibly at 0xFF800100 for issues with an offset.
Further research has lead me to believe that I need to use UBoot 1.1.3 due to the BSP documentation stating that it uses is 1.1.3, and I think because it was configured for it, we have to use it. I have run into many problems trying to make a binary for the 1.1.3. When I use the most recent version of the ELDK I get a binary of around 4.5GBs, and when I try and use an earlier version of the ELDK (3.1.1) I get a segmentation fault immediately when I try and configure it.
Any ideas?
I'm really not sure about this. The large binary suggests that you have code/data at 0 and at 0xfe000000, which seems wrong. So the image is trying to bridge the gap and ends up being huge.
If you have a working image from an old U-Boot and can build it from source, that helps a lot, since you can compare settings, etc. Sorry I can't help more...
Regards, Simon
Thanks, Austin
-----Original Message----- From: sjg@google.com [mailto:sjg@google.com] On Behalf Of Simon Glass Sent: Sunday, July 17, 2016 10:15 AM To: Gardner, Austin (GE Transportation) austin.gardner@ge.com Cc: u-boot@lists.denx.de Subject: EXT: Re: [U-Boot] MPC8347 Initial Boot problems
Hi,
On 30 June 2016 at 12:40, Gardner, Austin (GE Transportation) austin.gardner@ge.com wrote:
Still hoping for a response. I have not had any luck trying to get this up and running. Any advice would be very helpful.
Do you have any debug facilities? Maybe a BDI2000? It could be a board fault or something wrong with text base, etc.
Thanks, Austin
From: Gardner, Austin (GE Transportation) Sent: Friday, June 17, 2016 8:57 AM To: 'u-boot@lists.denx.de' u-boot@lists.denx.de Subject: MPC8347 Initial Boot problems
Hello,
I am currently trying to get my MPC8347EA board up and running by porting the MPC8349EMDS configuration that is currently available. This is my first time working with uboot, so naturally I am having some issues. My issue is that I can't get any response from the board after we flash it with the binary image. I don't know if I am flashing it in the wrong location, or if it is because the configurations in the header files that I changed are wrong. I have tried flashing it in various locations such as start of memory, CONFIG_SYS_TEXT_BASE location (changed to our needs of 0xFF8000000), etc. I also have changed a lot of the memory configurations from the MPC8349EMDS such as the timing configs, ddrlawbar and ddrlawar, sdram configs and modes, etc.
After getting the uboot to actually launch to a command line, the next step will be to have it launch to our QNX os.
Any help with this would be greatly appreciated. I apologize if I use the wrong terminology at any point, I am still very new to this.
Thanks, Austin
Regards, Simon

Dear Simon
In message CAPnjgZ3w6xn7omKK0V077iGWNVr8L71ZE26rnY_6A5C0pZ1w7A@mail.gmail.com you wrote:
I'm really not sure about this. The large binary suggests that you have code/data at 0 and at 0xfe000000, which seems wrong. So the image is trying to bridge the gap and ends up being huge.
Probaly the code / data overflows at 0xFFFFFFFF and wraps arount to continue at 0x0 which cuses the huge image size. We have seen this before with somme tool chain versions and some (usually sub-optimal) optimizer settings.
Best regards,
Wolfgang Denk
participants (2)
-
Simon Glass
-
Wolfgang Denk