[U-Boot-Users] help starting

[U-Boot-Users] help starting

[Sam Song]

Wolfgang Denk <wd@denx.de> wrote:
> 
> Is your BDI is configured to use hardware
breakpoints?

Well, I'd like to cut in here. A little out of
topic:-)

Does BDI2000 support Interrupt Service Routine debug?
How about exception?

Thanks in advance,

=====
Best regards,

Sam

_________________________________________________________
Do You Yahoo!?
150??MP3????????????
http://music.yisou.com/
???????????????????
http://image.yisou.com
1G??1000???????????
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/

[U-Boot-Users] help starting

[Wolfgang Denk]

In message <20041202084804.96333.qmail@web15602.mail.cnb.yahoo.com> you wrote:
>
> Does BDI2000 support Interrupt Service Routine debug?

Yes.

> How about exception?

Yes with some limitations.

Is it just my paranoid suspicion or did you really forget to read the
FAQ before postting? See http://www.denx.de/twiki/bin/view/DULG/FaqBDI2000

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"I think they're going to take all this money that we  spend  now  on
war and death --"                   "And make them spend it on life."
	-- Edith Keeler and Kirk, "The City on the Edge of Forever",
	   stardate unknown.

[U-Boot-Users] byte-order in the u-boot .c files

[Peter Asemann]

Ehm... okay, I was going to write an sdram- 
initialization-/refresh-/access- code following the wise and detailed 
instructions in chapter 15.9 of my fine MPC886 family reference manual.

I also took a look to uboot/board/NAME/NAME.c files to see how others 
initialize their SDRAM and program it.

Now the problem is that I'm not sure if the bit order of the 
documentation and the bit-order of the hex-values in the C-Code are 
corresponding. So I'm neither capable of looking what the others did in 
their code nor of generating hexadecimal representations of my bitstrings.

It seems like not to know this is incredibly stupid as I couldn't find 
anything about byte order in the README or the u-boot manual.

Anyway, if anyone could please tell me something about the byte-order of 
the u-boot code and how it relates to MPC-manual-byte-order, I'd be very 
happy.

Peter Asemann

[U-Boot-Users] help starting

[Sam Song]

Wolfgang Denk <wd@denx.de> ????
> > Does BDI2000 support Interrupt Service Routine
> debug?
> 
> Yes.
> 
> > How about exception?
> 
> Yes with some limitations.
> 
> Is it just my paranoid suspicion or did you really
> forget to read the FAQ before postting? See
> http://www.denx.de/twiki/bin/view/DULG/FaqBDI2000

Oops, I forgot the post etiquette. Apologize, no more
next time.

Thank you very much,

=====
Best regards,

Sam

_________________________________________________________
Do You Yahoo!?
150??MP3????????????
http://music.yisou.com/
???????????????????
http://image.yisou.com
1G??1000???????????
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/

[U-Boot-Users] byte-order in the u-boot .c files

[Wolfgang Denk]

In message <41AF11BC.6050403@web.de> you wrote:
>
> Now the problem is that I'm not sure if the bit order of the 
> documentation and the bit-order of the hex-values in the C-Code are 

The PowerPC documentation lists bit 0 as MSB. For a 32 bit value, bit
31 is the LSB.

> It seems like not to know this is incredibly stupid as I couldn't find 
> anything about byte order in the README or the u-boot manual.
> 
> Anyway, if anyone could please tell me something about the byte-order of 
> the u-boot code and how it relates to MPC-manual-byte-order, I'd be very 
> happy.

Now _BYTE_order is something completely different. For your  question
it  does  not  matter  at  all [FYI: U-Boot is (except for eventually
remaining bugs) byteorder-independent].


The bit order doesn't matter, either. Just write down  the  constants
as listed in the manual - MSB as MSB down to LSB as LSB ;-)

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Brain fried - Core dumped