Board Bring Up Query

N

Nutty 19 years ago

Hello to all,

I m working on the wireless product, in which there are many hardware components like DSP, WLAN Chipset, Memory, LCD, Key, ADC, etc. For this product i would like to write the Board Bring Up software and Power On Self Diagnostic Test Software. Actually this is the first time i m working on the Board Bring Up Software. I don't even know what is it? Could any one please help in regards and tell me what is the Board Bring Up and how to start the coding for that. On NET, i have searched a lot in regards, but everytime i m getting the information on some kind of tools, not the exact information. Is there any book available to study about the Board Bring Up?

Please guide me..........

Thanks in advance Nutty

Vote

M

MK 19 years ago

Hello Nutty,

Assuming this is a commercial project (not hobby or school) then the first thing you need is a specification. If whoever gave you the job can't give you one you will need to write it yourself - then get them to approve it.

If it's a complex board there is no way you can write the BBU (new TLA everyone !!) without a spec. It sounds a big job - perhaps you're out of your depth here in which case you should bale out or ask for help before it's too late.

Good luck (you are going to need it !).

Michael Kellett

Vote

D

Dave Rooney 19 years ago

There is a free package called Micro Monitor that is boot code and some tools that have been used on a number of different micros. Whether you use it or not there is some good information on where to begin. Check at:

formatting link

Dave Rooney

Vote

L

larwe 19 years ago

Sounds like a school project to me. It's the usual "I need to build a space shuttle by next Wednesday, but I don't understand where to put the blue diodes" sort of question we get in here all too frequently.

Vote

P

Peter Bennett 19 years ago

I think that the "Board Bring Up" software would be a simple test program that will exercise each feature of the board in a controlled fashion.

I would write it in chunks - the first one might do a simple memory test, and flash a LED on each pass. Next, I'd try to write something ("Hello World", to be original) on the LCD. Then add a function to read the keyboard, and display characters on the LCD. Once you have the keyboard and display working, you can more easily test the remaining components.

Peter Bennett, VE7CEI peterbb4 (at) interchange.ubc.ca new newsgroup users info : http://vancouver-webpages.com/nnq GPS and NMEA info: http://vancouver-webpages.com/peter Vancouver Power Squadron: http://vancouver.powersquadron.ca

Vote

C

CBFalconer 19 years ago

< all too frequently.

That's easy. They belong next to the resistors with the yellow bands. The result is green and good. :-)

cbfalconer at maineline dot net

Vote

I

Ivanna Pee 19 years ago

1) Using a scope, check that all clocks and power are present. 2) Get your debugger/emulator working with the target. 3) Write asm code or debugger script to initialize the Memory controller 4) Used debugger memory window to test address and data lines to memory( if fail, goto 3) 5) Get your stack in place so you can write in a higher level language 6) Write memory address and data line tests, run them to check for proper timing of memory controller 7) Hack out code to interface with one peripheral at a time 8) Write asm boot code (vector tables and memory controller and stack intialization) 9) Write simple app(i.e. blink and LED) and burn it into the flash 10) Boot from flash

Your task is to wiggle all the signals on the board to show that the board was designed and manufactured correctly. If your code don't work, be sure to doubt the board. You'll be cutting and jumpering it along the way.

Vote

M

msg 19 years ago

An old friend used to subscribe to tech. journals and mags in the name of "Agato Geueue" (pronounce it in a sort of African fashion rather than in a Romance language fashion and you'll get the gist...)

Regards,

Michael

Vote

Board Bring Up Query

Join the Discussion

Didn't find your answer?