[VxW] RE: Writing a flash driver in vxworks (tom pynadath)

GANESH KUMAR MURUGESAN ganesh.murugesan at wipro.com
Thu Jul 10 12:07:26 PDT 2003


Hi Tom,
> hi all,
>  
>  right now i am writing a  flash driver ( AM29F040B (AMD chip)) in
> VxWorks   on a MBX860 board ( socketed flash)      . I have some basic
> questions..
> 
>  1, How should i implement my flash driver  ? As a character or a
> block device?
Since you need to download MP3 files to flash, it would be better to
expose your flash as "Block device" which sits under VxDos File system.

>  2, How should i add my driver as a part of vxworks Kernel. 
To add your driver as a part of vxDos FS: Fill the "BLK_DEV" structure
with appropriate parameters/handlers and pass it's pointer to
"dosFsMkfs". This should be done "onetime".

>  3, During bootup time , how would my driver initialised? 
If you use the flash device just as a storage space for MP3 files, you
can call your "drive init" function either in usrAppInit or  HwInit. 

> 4,finally i have to copy one mp3 file from the mbx860 bord ram to the
> flash .how can i do it ?
If you have attached your flash device with vxDos FS, copying files
become very easy. You can use standard the FS calls like Copy command or
Move command. You can also use file system APIs like "fopen, fclose".
The user can view flash just as RAM disk.

Don't forget to add vxDos component to your project.

Regards
Ganesh

> -----Original Message-----
> From: vxwexplo-request at csg.lbl.gov 
> [mailto:vxwexplo-request at csg.lbl.gov] 
> Sent: Thursday, July 10, 2003 12:45 AM
> To: vxwexplo at csg.lbl.gov
> Subject: VxWexplo Digest, Vol 6, Issue 9
> 
> 
> Send VxWexplo mailing list submissions to
> 	vxwexplo at csg.lbl.gov
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www-csg.lbl.gov/mailman/listinfo/vxwexplo
> or, via email, send a message with subject or body 'help' to
> 	vxwexplo-request at csg.lbl.gov
> 
> You can reach the person managing the list at
> 	vxwexplo-owner at csg.lbl.gov
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of VxWexplo digest..."
> 
> 
> Today's Topics:
> 
>    1. RE: Max HD sizes for dosfs and dosfs2 in VxWorks 2.0.2?
>        (Robert L. Perry)
>    2. Re: one stupid question (linux guy)
>    3. Re: one stupid question (linux guy)
>    4. [SUSPECTED SPAM] Re: Application
>    5. Re: BIOS reads and writes... (Michael Lawnick)
>    6. Debug sysInit and romInit using ICE and VisionClick (Rikard)
>    7. Is there a tool which can transfer coff to elf? (Bryan)
>    8. system clock interrupt (yueshi)
>    9. Re: system clock interrupt (Joseph Hadzima)
>   10. Re: MPC8260 Cache  problem (Dan Gold)
>   11. Re: MPC8260 Cache  problem (Shawn McFarr)
>   12. Re: system clock interrupt (Chris Hann)
>   13. Identifying a target by its BSP (CASH)
>   14. Writing a flash driver in vxworks (tom pynadath)
>   15. MMU in X86 (biju k)
>   16. sysMmuMapAdd corresponding function in PowerePc (gopan)
> 
> 
> ----------------------------------------------------------------------
> 
> Date: Tue, 8 Jul 2003 20:59:01 -0400
> From: "Robert L. Perry" <bobPerry at randdgroup.com>
> To: "VxWorks Users Group List" <vxwexplo at csg.lbl.gov>
> Subject: RE: [VxW] Max HD sizes for dosfs and dosfs2 in VxWorks 2.0.2?
> Message-ID: <NGBBIBLMHBDEKCMFIBKJOEIDCCAA.bobPerry at RandDgroup.com>
> In-Reply-To: 
> <97AD70A848712741860C76A8F884D92201DB74D3 at ati-exchg2.asyst.com>
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 1
> 
> Under dosFs2.x I've been able to format & use just less than 
> 1 terabyte.
> 
> Bob Perry
> The R&D Group, LLC.
> 
> -----Original Message-----
> From: vxwexplo-bounces at csg.lbl.gov
> [mailto:vxwexplo-bounces at csg.lbl.gov]On Behalf Of Beck, Richard
> Sent: Wednesday, July 02, 2003 11:11 PM
> To: 'vxwexplo at lbl.gov'
> Subject: [VxW] Max HD sizes for dosfs and dosfs2 in VxWorks 2.0.2?
> 
> 
> Does anyone know what the limits are for dosfs and dosfs2 for 
> hard disk
> size?  I'm trying to install an ATA drive under VxWorks 2.0.2 
> with dosfs and
> the total size of the file system comes out far short of the defined
> sectors, bytes per sector, and cylinders.  I'm sure there's a 
> limit, but
> haven't found spec anywhere.  If I go to dosfs2, does that 
> increase? --RB
> 
> _______________________________________________
> VxWorks Users Group mailing list
> VxWexplo at lbl.gov
> http://www-csg.lbl.gov/vxworks/
> 
> ------------------------------
> 
> Date: Wed, 09 Jul 2003 10:03:08 +0800
> From: "linux guy" <linuxguy at linuxmail.org>
> To: "VxWorks Users Group List" <vxwexplo at csg.lbl.gov>
> Subject: Re: [VxW] one stupid question
> Message-ID: <20030709020308.21934.qmail at linuxmail.org>
> Content-Type: text/plain; charset="iso-8859-1"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 2
> 
> yes,we r using TMS 2.0.2 now
> ----- Original Message -----
> From: Junichiro Hamaguchi <hamajun at sbcglobal.net>
> Date: Tue, 08 Jul 2003 10:48:18 -0700
> To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Subject: Re: [VxW] one stupid question
> 
> > Yes.  How did you get them?  Did you buy the source code?
> > 
> > -hama
> > 
> > >r files below under $WIND_BASE/target/src/netinet  the 
> source code of TCP/
> > >IP Protocol stack?
> > >[.]             [..]            Makefile        if.c       
>      if_ether.c
> > >if_subr.c       igmp.c          in.c            in_cksum.c 
>      in_pcb.c
> > >in_proto.c      ip_icmp.c       ip_input.c      
> ip_mroute.c     ip_output.c
> > >[ppp]           radix.c         raw_cb.c        raw_ip.c   
>      raw_usrreq.c
> > >route.c         rtsock.c        sl_compress.c   
> sys_socket.c    tcp_debug.c
> > >tcp_input.c     tcp_output.c    tcp_subr.c      
> tcp_timer.c     tcp_usrreq.c
> > >udp_usrreq.c    uipc_dom.c      uipc_mbuf.c     
> uipc_sock.c     uipc_sock2.c
> > >unixLib.c
> > >-- 
> > >______________________________________________
> > 
> > _______________________________________________
> > VxWorks Users Group mailing list
> > VxWexplo at lbl.gov
> > http://www-csg.lbl.gov/vxworks/
> 
> -- 
> ______________________________________________
> http://www.linuxmail.org/
> Now with e-mail forwarding for only US$5.95/yr
> 
> Powered by Outblaze
> ------------------------------
> 
> Date: Wed, 09 Jul 2003 10:18:54 +0800
> From: "linux guy" <linuxguy at linuxmail.org>
> To: "VxWorks Users Group List" <vxwexplo at csg.lbl.gov>
> Subject: Re: [VxW] one stupid question
> Message-ID: <20030709021854.32488.qmail at linuxmail.org>
> Content-Type: text/plain; charset="iso-8859-1"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 3
> 
> thx:)
> ----- Original Message -----
> From: Junichiro Hamaguchi <hamajun at sbcglobal.net>
> Date: Tue, 08 Jul 2003 10:48:18 -0700
> To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Subject: Re: [VxW] one stupid question
> 
> > Yes.  How did you get them?  Did you buy the source code?
> > 
> > -hama
> > 
> > >r files below under $WIND_BASE/target/src/netinet  the 
> source code of TCP/
> > >IP Protocol stack?
> > >[.]             [..]            Makefile        if.c       
>      if_ether.c
> > >if_subr.c       igmp.c          in.c            in_cksum.c 
>      in_pcb.c
> > >in_proto.c      ip_icmp.c       ip_input.c      
> ip_mroute.c     ip_output.c
> > >[ppp]           radix.c         raw_cb.c        raw_ip.c   
>      raw_usrreq.c
> > >route.c         rtsock.c        sl_compress.c   
> sys_socket.c    tcp_debug.c
> > >tcp_input.c     tcp_output.c    tcp_subr.c      
> tcp_timer.c     tcp_usrreq.c
> > >udp_usrreq.c    uipc_dom.c      uipc_mbuf.c     
> uipc_sock.c     uipc_sock2.c
> > >unixLib.c
> > >-- 
> > >______________________________________________
> > 
> > _______________________________________________
> > VxWorks Users Group mailing list
> > VxWexplo at lbl.gov
> > http://www-csg.lbl.gov/vxworks/
> 
> -- 
> ______________________________________________
> http://www.linuxmail.org/
> Now with e-mail forwarding for only US$5.95/yr
> 
> Powered by Outblaze
> ------------------------------
> 
> Date: Wed, 9 Jul 2003 12:05:34 +0800
> From: <dc8 at lucent.com>
> To: <vxwexplo at lbl.gov>
> Subject: [VxW] [SUSPECTED SPAM] Re: Application
> Message-ID: <200307090407.h6947X3X015703 at mta1.lbl.gov>
> Content-Type: multipart/mixed;
> 	boundary="CSmtpMsgPart123X456_000_03276145"
> MIME-Version: 1.0
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 4
> 
> This is a multipart message in MIME format
> 
> --CSmtpMsgPart123X456_000_03276145
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> ------ NOTICE ------------ NOTICE ------------ NOTICE ------
> 
> 1. The LBNL VirusWall REMOVED a virus from this message.
>    The message is now safe to open.
> 
> 2. If you need help or have questions, contact the
>    Help Desk at 510-486-HELP.
> 
> 3. For information, please visit:
>    http://www.lbl.gov/ITSD/Security/vulnerabilities/virus.html
> 
> ------------------------------------------------------------
> 
> Found virus WORM_SOBIG.E in file details.pif (in your_details.zip)
> The uncleanable file your_details.zip is moved to 
> /etc/iscan/virus_quarantine/virDTETSbiIp.
> 
> ---------------------------------------------------------
> 
> --CSmtpMsgPart123X456_000_03276145
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
> 
> Please see the attached zip file for details.
> --CSmtpMsgPart123X456_000_03276145
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> 
> ------ NOTICE ------------ NOTICE ------------ NOTICE ------
> 
> 1. The LBNL VirusWall REMOVED a virus from this message.
>    The message is now safe to open.
> 
> 2. If you need help or have questions, contact the
>    Help Desk at 510-486-HELP.
> 
> 3. For information, please visit:
>    http://www.lbl.gov/ITSD/Security/vulnerabilities/virus.html
> 
> ------------------------------------------------------------
> 
> your_details.zip is removed from here because it contains a virus.
> 
> ---------------------------------------------------------
> --CSmtpMsgPart123X456_000_03276145--
> 
> ------------------------------
> 
> Date: Wed, 9 Jul 2003 08:07:41 +0200
> From: "Michael Lawnick" <michael.lawnick at no_spam_pls.kontron.com>
> To: vxwexplo at csg.lbl.gov
> Subject: [VxW] Re: BIOS reads and writes...
> Message-ID: <3f0bb12b_2 at news.arcor-ip.de>
> References: <eb3954b.0307081323.39026573 at posting.google.com>
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 5
> 
> Hi Chris,
> 
> > "The JEDEC ID registers for the boot device appear at
> > FFBC0000H and FFBC0001H in the 4 GByte system
> > memory map"
>  This are *2* bytes, so you'll have to do
> short ID = (short *)0xFFBC0000;
> otherwise you try to read out two more bytes, of which you 
> don't know what's
> their definition.
> 
> If this doesn't work, try it with byte access.
> 
> HTH
> --
> 
> Regards,
> Michael
> 
> 21 is only half the truth.
> 
> FAQ  - "http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html"
> Wiki -
> "http://www.bluedonkey.org/cgi-bin/twiki/bin/view/Books/VxWork
> sCookBook"
> "Chris" <spame at chrisd.info> schrieb im Newsbeitrag
> news:eb3954b.0307081323.39026573 at posting.google.com...
> > I am tring to read the JEDEC ID Register for the firmware hub (FWH)
> > that stores the BIOS... The FWH documentation states the following:
> >
> > "The JEDEC ID registers for the boot device appear at
> > FFBC0000H and FFBC0001H in the 4 GByte system
> > memory map"
> >
> > So I take this to mean that all I have to do is read 0xFFBC0000 as
> > follows:
> >
> > int ID = (int*)0xFFBC0000;
> >
> > after which ID should magically contain the Manufacturer's 
> ID and the
> > Device ID for this FWH... However I get a page fault exception right
> > when it tries to move data from 0xFFBC0000! What am I missing?
> >
> > Note: This is an Intel Xeon based system with VxWorks 5.5.
> 
> 
> ------------------------------
> 
> Date: 9 Jul 2003 02:13:23 -0700
> From: andreas_lindell75 at hotmail.com (Rikard)
> To: vxwexplo at csg.lbl.gov
> Subject: [VxW] Debug sysInit and romInit using ICE and VisionClick
> Message-ID: <5947a04.0307090113.40a26e78 at posting.google.com>
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 8bit
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 6
> 
> Hello Everyone
> 
> I have PPC860 target with wrMdpBasic860 BSP from WR. Now I want to
> debug romInit(romInit.s) and sysInit(sysALib.s) using ICE and
> VisionClick. What I have done is to build my bootrom with: make
> bootrom_uncmp and the use the convert utility in VisionClick to
> convert my bootrom_uncmp to *.ab file and *.bdx file which I can
> download to the RAM memory. As reset symbol I started of with
> specifying: sysHwInit (sysLib.c), this works fine and I get the C
> source (sysLib.c) file which I can step through.
> 
> Now I want to change my reset symbol to either romInit or sysInit and
> after setting it to romInit I reload the RAM with my code and when
> executing it the debugger stops at the romInit symbol and I can step
> using F2 key. Now the problem is that here I see pure assemble code,
> not the contents of romInit.s which is where the romInit "function" is
> declared and thus is what I want to see when I step through the code.
> I assumed that when debugging a function declared/defined in a *.s I
> would see the contents of the *.s and not the pure assemble in the
> same way as I see the C source file when breaking in a function
> declared/defined in a C source file.
> 
> I hope that I have explained my problem in a clear way and if anyone
> knows how to get VisionCLICK to display the contents of *.s when
> debugging instead of the pure assemble pls provide me with some
> pointers.
> 
> Regards
> Andreas
> ------------------------------
> 
> Date: 9 Jul 2003 02:38:41 -0700
> From: hotJacky at 163.net (Bryan)
> To: vxwexplo at csg.lbl.gov
> Subject: [VxW] Is there a tool which can transfer coff to elf?
> Message-ID: <8f77d4a.0307090138.6d83cd0c at posting.google.com>
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 8bit
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 7
> 
> Hello,
> 
> With ccarm (gcc2.79),I get a coff output,With ccarm (gcc 
> 2.9),I get a elf output.
> My question is :
> 1)Can I change the coff format to elf?
> 2)Can I adjust the gcc2.79 options to produce a elf 
> output,not a coff output?
> 
> Sincerely
> Bryan
> ------------------------------
> 
> Date: 9 Jul 2003 07:22:38 -0700
> From: shenyueshi at yahoo.com.au (yueshi)
> To: vxwexplo at csg.lbl.gov
> Subject: [VxW] system clock interrupt
> Message-ID: <447b3d86.0307090622.79dc087b at posting.google.com>
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 8bit
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 8
> 
> Hi,
> 
> I am using VxWorks 5.5 on PC Pentium III target.  My question is how
> can I make use of the system clock to do something regularly.
> 
> For example, the target computer will receive a command from other
> machine which indicates the start of such a function that to read a
> board every, say, 0.001 second.
> 
> So, what's the usual way to realize that on VxWorks, is it relavent to
> some routines in sysLib, for instance, sysAuxClkConnect() etc.?
> 
> Also, if I wish to read the system clock, is that such a function
> availabe in VxWorks API library?
> 
> Thank you very much!
> 
> Sincerely
> Yueshi
> ------------------------------
> 
> Date: Wed, 9 Jul 2003 09:46:55 -0700 (PDT)
> From: Joseph Hadzima <josef508 at yahoo.com>
> To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Subject: Re: [VxW] system clock interrupt
> Message-ID: <20030709164655.32978.qmail at web41506.mail.yahoo.com>
> In-Reply-To: <447b3d86.0307090622.79dc087b at posting.google.com>
> Content-Type: text/plain; charset=us-ascii
> MIME-Version: 1.0
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 9
> 
> HI Yueshi:
> 
> There are several common methods used to do something
> periodically.
> 
> 1) // to do something and can tolorate +/- clk tick drift.
>    // taskDelay uses sysClk to monitor time.
> myTask1()
> {
>   for(;;)
>   {
>     taskDelay( NUM_SECONDS * sysClkRateGet() );
>     doSomething( doSomethingArg1 );
>   }
> }
> 
> 2)// to do something after N clk ticks and minimize drift
>   // also uses system clock to monitor time to call
> WatchDog
> doSomething()
> {
>     myWDID = wdCreate();
>     mySemID = smeBCreate( SEM_Q_PRIORITY, SEM_EMPTY );
>     for(;;)
>     {
>        wdStart( myWDID, NUM_CLK_TICKS, semGive, mySemID );
>        semTake( mySemID, WAIT_FOREVER );
>        actuallyDoSomething()
>     }
> }
> 
> 3)
> // to do something at a fast rate (i.e. > 500 Hz) .
> // use Aux Clk so can set rate independent of sysClk rate
> // CAUTION: doSomething() in this case is an ISR, 
> // and must comply with ISR design rules 
> // (no blocking calls, and no IO).
> myTask3()
> {
>   sysAuxClkRateSet( NUM_TICS_PER_SECOND );
>   sysAuxClkConnect( doSomething, doSomethingArg );
>   sysAuxClkEnable();
>   taskDelay( NUM_SECONDS * sysClkRateGet() );
>   sysAuxClkDisable();
> }
> 
> 
> those are the basics ... play with them to get a better
> feel.  BTW you can also use the wd timers to detect missed
> dead-lines if you design yuor task to reload the timer
> (call wdStart()) before the deadline occurs.  If it does
> occur then run code to handle the missed dead-line.
> 
> HTH and happy coding!
> 
> --- yueshi <shenyueshi at yahoo.com.au> wrote:
> > Hi,
> > 
> > I am using VxWorks 5.5 on PC Pentium III target.  My
> > question is how
> > can I make use of the system clock to do something
> > regularly.
> > 
> > For example, the target computer will receive a command
> > from other
> > machine which indicates the start of such a function that
> > to read a
> > board every, say, 0.001 second.
> > 
> > So, what's the usual way to realize that on VxWorks, is
> > it relavent to
> > some routines in sysLib, for instance, sysAuxClkConnect()
> > etc.?
> > 
> > Also, if I wish to read the system clock, is that such a
> > function
> > availabe in VxWorks API library?
> > 
> > Thank you very much!
> > 
> > Sincerely
> > Yueshi
> > _______________________________________________
> > VxWorks Users Group mailing list
> > VxWexplo at lbl.gov
> > http://www-csg.lbl.gov/vxworks/
> 
> 
> =====
> HADZ.
> 
> Never be afraid to try something new. Remember, amateurs 
> built the ark. Professionals built the Titanic. 
> 
> (this Email sent using 100% recycled electrons)
> 
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> ------------------------------
> 
> Date: Wed, 9 Jul 2003 09:41:44 -0700
> From: "Dan Gold" <gold at ensemble.com>
> To: vxwexplo at csg.lbl.gov
> Subject: Re: [VxW] MPC8260 Cache  problem
> Message-ID: <behgkj$jld$1 at newsreader.mailgate.org>
> References: <mailman.90.1057078570.1554.vxwexplo at csg.lbl.gov>
> 	<f2494051.0307011902.52798114 at posting.google.com>
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 10
> 
> "Wenzhong Liu" <wenzhongliu at yahoo.com> wrote in message
> news:f2494051.0307011902.52798114 at posting.google.com...
> > Prashant,
> >
> > If I remember correctly, the Rev A and Rev B silicon of 
> MPC8260 have bugs
> with
> > their  MMU, so you need to check if you are using the Rev A 
> or Rev B CPU
> chip.
> > If so, you can't expect the cacheEnble function works for you.
> 
> What sort of bugs do you remember ?  I have HiP3 (Rev A, B 
> and C) and HiP4
> (Rev A and B) running by themselves with cache/MMU (and CPM snooping)
> enabled, and coupled to other PPCs,  and haven't had any 
> problems.  I also
> haven't seen anything in the chip or UM errata, and I checked 
> with our Mot
> rep.  No one has seen/heard of any MMU problems.  The only 
> possibility that
> comes to mind is the ARTRY* not working with a pipeline depth 
> of 0, but
> that's documented in the chip errata.
> 
>   Dan Gold    gold-AT-no.spam.please.ensemble.com
> 
> 
> ------------------------------
> 
> Date: Wed, 9 Jul 2003 10:25:36 -0700 (PDT)
> From: Shawn McFarr <smcfarr at yahoo.com>
> To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Subject: Re: [VxW] MPC8260 Cache  problem
> Message-ID: <20030709172536.93531.qmail at web11907.mail.yahoo.com>
> In-Reply-To: <behgkj$jld$1 at newsreader.mailgate.org>
> Content-Type: text/plain; charset=us-ascii
> MIME-Version: 1.0
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 11
> 
> Hey Dan, 
>  
> Don't you have work to do man? :) I am looking for work any 
> kind of work as long as
> it pays. :) 
>  
> -Shawn
>  
> Dan Gold <gold at ensemble.com> wrote:
> "Wenzhong Liu" wrote in message
> news:f2494051.0307011902.52798114 at posting.google.com...
> > Prashant,
> >
> > If I remember correctly, the Rev A and Rev B silicon of 
> MPC8260 have bugs
> with
> > their MMU, so you need to check if you are using the Rev A 
> or Rev B CPU
> chip.
> > If so, you can't expect the cacheEnble function works for you.
> 
> What sort of bugs do you remember ? I have HiP3 (Rev A, B and 
> C) and HiP4
> (Rev A and B) running by themselves with cache/MMU (and CPM snooping)
> enabled, and coupled to other PPCs, and haven't had any 
> problems. I also
> haven't seen anything in the chip or UM errata, and I checked 
> with our Mot
> rep. No one has seen/heard of any MMU problems. The only 
> possibility that
> comes to mind is the ARTRY* not working with a pipeline depth 
> of 0, but
> that's documented in the chip errata.
> 
> Dan Gold gold-AT-no.spam.please.ensemble.com
> 
> 
> _______________________________________________
> VxWorks Users Group mailing list
> VxWexplo at lbl.gov
> http://www-csg.lbl.gov/vxworks/
> 
> ---------------------------------
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!From 
> chann94501 at yahoo.com Wed Jul  9 10:38:21 2003
> Received: from web14707.mail.yahoo.com (web14707.mail.yahoo.com
> 	[216.136.224.124])
> 	by csg.lbl.gov (8.11.6/8.11.6) with SMTP id h69HcK721701
> 	for <vxwexplo at csg.lbl.gov>; Wed, 9 Jul 2003 10:38:20 -0700
> Message-ID: <20030709173820.66386.qmail at web14707.mail.yahoo.com>
> Received: from [63.145.233.34] by web14707.mail.yahoo.com via HTTP;
> 	Wed, 09 Jul 2003 10:38:20 PDT
> Date: Wed, 9 Jul 2003 10:38:20 -0700 (PDT)
> From: Chris Hann <chann94501 at yahoo.com>
> Subject: Re: [VxW] system clock interrupt
> To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> In-Reply-To: <447b3d86.0307090622.79dc087b at posting.google.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> X-BeenThere: vxwexplo at csg.lbl.gov
> X-Mailman-Version: 2.1
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> List-Id: VxWorks Users Group List <vxwexplo.csg.lbl.gov>
> List-Unsubscribe: <http://www-csg.lbl.gov/mailman/listinfo/vxwexplo>,
> 	<mailto:vxwexplo-request at csg.lbl.gov?subject=unsubscribe>
> List-Archive: <http://csg.lbl.gov/pipermail/vxwexplo>
> List-Post: <mailto:vxwexplo at csg.lbl.gov>
> List-Help: <mailto:vxwexplo-request at csg.lbl.gov?subject=help>
> List-Subscribe: <http://www-csg.lbl.gov/mailman/listinfo/vxwexplo>,
> 	<mailto:vxwexplo-request at csg.lbl.gov?subject=subscribe>
> 
> Back in 1980 I used the sysAuxClock() on a 25MHz 68040 to run a 1ms
> message timing loop, I checked it with a logic analyzer and it was
> accurate to a few tens of microseconds. If you are doing something
> relatively simple this is a better way than giving a 
> semaphore and then
> praying that the tasking systems lets you in.
> 
> The first thing we did to any vxWorks system was always to change the
> clock to 100 or 200Hz so the system timings were in whole numbers of
> milliseconds. The 60Hz system clock is an anachronism.
> 
> Chris
> 
> --- yueshi <shenyueshi at yahoo.com.au> wrote:
> > Hi,
> > 
> > I am using VxWorks 5.5 on PC Pentium III target.  My question is how
> > can I make use of the system clock to do something regularly.
> > 
> > For example, the target computer will receive a command from other
> > machine which indicates the start of such a function that to read a
> > board every, say, 0.001 second.
> > 
> > So, what's the usual way to realize that on VxWorks, is it relavent
> > to
> > some routines in sysLib, for instance, sysAuxClkConnect() etc.?
> > 
> > Also, if I wish to read the system clock, is that such a function
> > availabe in VxWorks API library?
> > 
> > Thank you very much!
> > 
> > Sincerely
> > Yueshi
> > _______________________________________________
> > VxWorks Users Group mailing list
> > VxWexplo at lbl.gov
> > http://www-csg.lbl.gov/vxworks/
> 
> ------------------------------
> 
> Date: Wed, 9 Jul 2003 10:47:25 -0700 (PDT)
> From: Chris Hann <chann94501 at yahoo.com>
> To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Subject: Re: [VxW] system clock interrupt
> Message-ID: <20030709174725.88907.qmail at web14710.mail.yahoo.com>
> In-Reply-To: <20030709173820.66386.qmail at web14707.mail.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
> MIME-Version: 1.0
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 12
> 
> Oops. 1990. In 1980 I was using a 1MHz 6502 in highschool :-\
> 
> > Back in 1980 I used the sysAuxClock() on a 25MHz 68040 to run a 1ms
> 
> ------------------------------
> 
> Date: Wed, 09 Jul 2003 10:00:24 +0530
> From: "CASH" <c_sh at indiatimes.com>
> To: <vxwexplo at csg.lbl.gov>
> Subject: [VxW] Identifying a target by its BSP
> Message-ID: <200307090443.KAA27571 at WS0005.indiatimes.com>
> Content-Type: text/plain; charset=us-ascii
> MIME-Version: 1.0
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 13
> 
> Hi,
> 
> 
> well this is a kind of a stupid question, actually my company 
> used to work on Vxworks some 3-4 years back, &amp; we have a 
> BSP an Intel 486 machine, now I'd like to know, (how) can I 
> find out the mother board configurations of the target from 
> the BSP(so as to give the specs for its purchase)?
> 
> 
> The boss wants me to do some initial research before the 
> company reviews its contract with the Wind River, &amp; I'm a 
> total newbie to this RTOS, I need help here,
> 
> 
> thanks in advance,
> 
> 
> CA$H 
> I was born intelligent 
> education ruined me. 
> 
> 
> Get Your Private, Free E-mail from Indiatimes at  
> http://email.indiatimes.com
> Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com
> Bid for Air Tickets @ Re.1 on Air Sahara Flights. Just log on 
> to http://airsahara.indiatimes.com and Bid Now !
> ------------------------------
> 
> Date: 9 Jul 2003 02:13:39 -0700
> From: thomaspoly at hotmail.com (tom pynadath)
> To: vxwexplo at csg.lbl.gov
> Subject: [VxW] Writing a flash driver in vxworks
> Message-ID: <f9fa98a7.0307090113.750c5cdf at posting.google.com>
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 8bit
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 14
> 
> hi all,
>  
>  right now i am writing a  flash driver ( AM29F040B (AMD chip)) in
> VxWorks   on a MBX860 board ( socketed flash)      . I have some basic
> questions..
> 
>  1, How should i implement my flash driver  ? As a character or a
> block device?
> 
>  2, How should i add my driver as a part of vxworks Kernel. 
> 
>  3, During bootup time , how would my driver initialised? 
> 
> 4,finally i have to copy one mp3 file from the mbx860 bord ram to the
> flash .how can i do it ?
> 
>                      Pheew... too many questions .  hope u guys can
> help me .
> 
> 
>                                                              WIth Luv,
>                                                              Tom.
> ------------------------------
> 
> Date: 9 Jul 2003 03:28:25 -0700
> From: biju080 at yahoo.com (biju k)
> To: vxwexplo at csg.lbl.gov
> Subject: [VxW] MMU in X86
> Message-ID: <eb8c6529.0307090228.3686bbac at posting.google.com>
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 8bit
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 15
> 
> hello everybody,
> 
> can anyone tell me vxworks memory management model for x86 machines
> i  found very little or no document related to memory management in
> wrs documents.
> 
> 
> Is it paging or segmentation and does vxworks facilitates all the
> protection provided by MMU in x86,considering the fact that it works
> in common address space,
> 
> i am using vxworks 5.4 version
> 
> thanks in advance
> 
> biju
> ------------------------------
> 
> Date: 9 Jul 2003 05:34:21 -0700
> From: gop_kumar at hotmail.com (gopan)
> To: vxwexplo at csg.lbl.gov
> Subject: [VxW] sysMmuMapAdd corresponding function in PowerePc
> Message-ID: <cd5b2d94.0307090434.15cb98f8 at posting.google.com>
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 8bit
> Precedence: list
> Reply-To: VxWorks Users Group List <vxwexplo at csg.lbl.gov>
> Message: 16
> 
> Dear All,
> 
> I want to port x86 PCI device driver on PowerPc. In x86, after getting
> the physical address for my device we add the device address space to
> the MMU table using "sysMmuMapAdd()" and "usrMmuInit()". what are the
> corresponding function to do the same on PowerPc.
> 
> Thanks and regards
> GopaKumar
> ------------------------------
> 
> _______________________________________________
> VxWorks Users Group mailing list
> VxWexplo at lbl.gov
> http://www-csg.lbl.gov/vxworks/
> 
> 
> End of VxWexplo Digest, Vol 6, Issue 9
> **************************************
> 

**************************Disclaimer************************************

Information contained in this E-MAIL being proprietary to Wipro Limited is 
'privileged' and 'confidential' and intended for use only by the individual
 or entity to which it is addressed. You are notified that any use, copying 
or dissemination of the information contained in the E-MAIL in any manner 
whatsoever is strictly prohibited.

***************************************************************************


More information about the VxWexplo mailing list