public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: nohabviktor <nohabviktor@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] After relocate the printf not working
Date: Fri, 19 Sep 2014 07:01:22 -0700 (MST)	[thread overview]
Message-ID: <1411135282961-189814.post@n7.nabble.com> (raw)

Hi! 
I have a LPC1788 board with 32Mbyte RAM and NAND flash and I followed the
nxp instructions: 
http://www.lpcware.com/content/project/lpc177x8x-u-boot-port/u-boot-build-procedure

The result is: 
U-Boot 2011.06 (Aug 16 2011 - 16:47:50) 

NXP LPC1788 Cortex-M3 
DRAM: 32 MiB 
Flash: e1z? K!A 
NAND: y2x#Mi 
#foeid !f pide 65472+ vedsigz 0@&1 
#fojd !f pide 65408+ vedsigz 0@&1 
pro!whoe "sadiyg fd "hocK!ta\x7fe 
naf_rued_Zbt:8 at adnaf_rued_Zbt:8 at ad``lokk ad40x000000120000zta\x7fe 
naf_rued_Zbt:8 at ad``lokk ad40x000000140x00zta\x7fe 
naf_rued_Zbt:8 at adnaf_rued_Zbt:8 at ad``lokk ad40x000000180000 
ta\x7fe 
naf_rued_Zbt:8 at ad``lokk ad40x0000001a0000zta\x7fe 
naf_rued_Zbt:8 at adnaf_rued_Zbt:8 at ad``lokk ad40x0000001e0000zta\x7fe 
sd rom(kffpt 40000 fa9xed***0Wa 
{viznm-|tdenv() failedL!usYxg `fa}{t 

In: serial 
Out: serial 
Err: serial 
uboot> 

I send a 'help' command: 

uboot> he 
Uncmow0coMkan0'he'x9 trl 'uboot> 
uboot> 

I switch on the debug mode and I realized the printf and vsprintf not
working correctly after the relocated on the ram.  The puts function is
works fine all the time. I tried the u-boot.hex from the nxp and the result
is same. I have no idea whats the problem. Please help me!



--
View this message in context: http://u-boot.10912.n7.nabble.com/After-relocate-the-printf-not-working-tp189814.html
Sent from the U-Boot mailing list archive at Nabble.com.

             reply	other threads:[~2014-09-19 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 14:01 nohabviktor [this message]
2014-09-19 17:48 ` [U-Boot] After relocate the printf not working Jeroen Hofstee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1411135282961-189814.post@n7.nabble.com \
    --to=nohabviktor@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox