|
I am working on a Silicon Labroratories F340, and in my KEIL uVision3 I
have found it in the "device database". I can make a project with this
chip set. But when I compile the project, it showed error message "path
for toolset undefined".
I checked the tools.ini, it only contains my email address.
Thanks.
|
|
|
|
|
Problem solved. Set up in the enviornment.
|
|
|
|
|
I have an annoying problem with my Windows Advanced Server 2000 locking up - no keyboard or mouse input.
I am now running standard PS2 mouse "in parallel" with my wireless mouse and when it locks up neither mouse will move the cursor.
The only way to recover is to turn the power off which creates havoc with my RAID!
Is it possible that the battery in MS keyboard / mouse is getting weak and causing this?
I have replaced battery in keyboard - and it seems to "solve " the problem.
Anybody else with similar experience?
|
|
|
|
|
receive a interrupt for a device -> tell the cpu that there is a interrupt ->
the cpu ask 8259 the interrupt number -> 8259 tells it
I don't think it's necessary to divide it into 2 parts, 8259 could tell the interrrupt number directly. I doubt whether it is the original design goal.
Any explain? Thanks.
|
|
|
|
|
Hi,
a lot of peripherals work this way; they basically connect to the CPU using an address bus,
a data bus and one interrupt line (plus maybe a clock, a read, a write, a chip select).
The address and data bus (and control lines) are shared, the interrupt line is individual.
When they want the attention of the CPU they signal an interrupt; then the CPU, when it
chooses to do so, interrogates the chip to find out the exact cause for the interrupt.
Such peripherals are slave devices, they cannot grab the address and/or data bus,
they can only request the CPU's attention. It is the same for simple parallel port adapters,
for simple serial ports, etc.
The address and/or data bus (and the control lines: read, write, ...) is "owned" by the
bus master, which is either the CPU or some other rather comples device (typically
with DMA capabilities, such as a disk controller, a network controller, ...).
Luc Pattyn [Forum Guidelines] [My Articles]
this months tips:
- use PRE tags to preserve formatting when showing multi-line code snippets
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
I see it. Thanks.
I think if the interrupt pin can carry interrupt no. infomation, it'll be much more efficient.
|
|
|
|
|
followait wrote: I think if the interrupt pin can carry interrupt no. infomation, it'll be much more efficient.
Sorry to state the obvious but ....
It's a pin - it can only be on or off. It is physically impossible to show more information than active or inactive
Judy
|
|
|
|
|
No, it is not physically impossible to transmit data over 1 pin (+gnd, obviously). The interrupt line just never was designed to carry more information. (It would, however, be one-way only and require some synching via alternating the line first).
Cheers,
Sebastian
--
"If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
|
|
|
|
|
I agree. However, my statement was that the pin can only be active or inactive which is true. Your solution requires the addition of either an implicit timing element or an explicit additional line for synchronization to toggle the line in a meaningful way. I've seen both in proprietary buses. I got the impression from the OP's post that he wanted "the interrupt pin to carry the interrupt number" instead of just signalling an interrupt occured. I was pointing out that the interrupt "section" of the bus is only a single pin as compared to the data "section" which is a set of pins.
Judy
|
|
|
|
|
Ah, misunderstood you.
Sorry, I am not a native speaker of English. Please, bear with me 
And of course, signalling an interrupt number does not make sense. Reading it would take way too long to keep the line useful.
Cheers,
Sebastian
--
"If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
|
|
|
|
|
Hi all,
I have a P4 System . I have a problem of Date and Time of my System, when I save
the Date and Time in Bios it saved , But After a restart ,it come back in his previous state .
I've tried resetting the CMOS using the jumper on the motherboard, and I
replaced the Bios battery . But it still won't save the changes .
Plz sugess me If have you any Idea .
Thanks alot for this .
nilesh
|
|
|
|
|
Was the battery "socketed" or soldered? If you just removed one and inserted another one, check the contacts/wiring.
Otherwise: Do you have a "fallback"-BIOS? If so, make sure it is not active - these sometimes are not backed up with a battery.
Cheers,
Sebastian
--
"If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
|
|
|
|
|
I want to develop an application which will use a cash-dispenser to distribute money for the labour on basis for how many days they have worked at the company . i need to know abt the cash-dispensers, can u connect it to my pc? will i programe it myself? any price information (i need the cheapest 1). and any extra help/information ll b appritiated!!!
thanx in advance
(Jameel)
|
|
|
|
|
Try Wincor-Nixdorf or any local banking hardware provider. You will probably need a system capable of dispensing coins AND paper, so the "cheapest one" won't do.
They usually offer a SDK which reduces the work in your software to a few simple steps.
If I was you, I'd go with automated cheque printing or wire transfer, though... it is easier to be sure that the right amount was printed than being sure the right amount was COUNTED.
Cheers,
Sebastian
--
"If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
|
|
|
|
|
Actually i want my application to give money to the labour right on the spot as our labour is 99% un-educated and dont have any back accounts etc... that y i need a dispenser to give then money to avoid large-queues to give them money by hand!!! and thats what the core problem and core-requiremnt of my application to satisfy!!! any help plzzz
(Jameel)
|
|
|
|
|
Yeah, but you need to buy a dispenser first. And if you have, give the model number, so people know what hardware you are talking about. They are all different. As I said, Wincor-Nixdorf builds he kind of hardware you are looking for (ATM, etc.)
As for the requirements:
You know, the first thing they will do (even before making room for the next person in the queue) is counting their money. They will not trust the system, because they cannot watch the system count (closed flaps and high speed).
Also, I see your problem now: They labour won't trust cheques and wire-transfer. I missed that part somehow, mainly because employers only need to offer wire-transfer here in Germany. Everything else is optional - and the Employer might even choose to charge for other modes of payment.
Hmm...
Interesting problem. Let me think about it some more....
Cheers,
Sebastian
--
"If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
|
|
|
|
|
excuse for my english........i am from mexico
CAN I obtain the characteristics of my PC by means of assembly language?
and....give me the code please !!!!!!!!!!
can i help me??? Thanks !!!
|
|
|
|
|
Hi,
a lot of the PC characteristics (amount of RAM, disk size, USB devices, ...)
can be obtained WITHOUT assembly, assembly code does not help here at all.
some of the CPU characteristics (cache sizes, supported instructions, ...) can be
obtained with assembly, in particular by executing the CPUID instruction.
Intel offers an entire Application Note on that. Google it!
In order to run the CPUID from .NET, you would need a C/C++ native code DLL, and do
some PInvoke.
Luc Pattyn [Forum Guidelines] [My Articles]
this months tips:
- use PRE tags to preserve formatting when showing multi-line code snippets
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
Hi guys,
I had it with this laptop, I have no clue why this Compaq Presario V3000 w/WinXP Home SP2 won't recognize the CD/DVD drive. 
I looked at the BIOS, and it doesn't show up there.
I looked at the Device Manager, and it doesn't show up there. (Yes, I scanned for new hardware too...)
At least, the Disk Management will sometimes list it, but not this time.
So, I am open for ideas. What do you suggest to do?
BTW, the CD/DVD drive works, so if I put a CD or DVD the disk spins, and the light flashes and all...but WinXP won't show anything.
Any help is appreciated.
Thanks,
...neualex
|
|
|
|
|
Sounds like the connection is loose or the drive hardware is on the way out. Many many problems are blamed on the software, but it can't do anything if the hardware doesn't respond to the messages sent.
Get it repaired/replaced.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
|
Worst thing is that this drive is not removable, so I cannot check the IDE connection 
|
|
|
|
|
All storage devices are removable. Your choice is to send it back to Compaq for repair or do it yourself (and void your warranty).
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
John,
Yes, I agree. All drives are removable; however, what I meant was this drive cannot be removed without actually opening the laptop.
I'd love to send it to Compaq, but warranty expired already for it.
|
|
|
|
|
See what happens if you try booting off a live linux CD. IF you have trouble doing this consistently it's probably a hardware issue, if it works flawlessly every time it's probably software.
--
If you view money as inherently evil, I view it as my duty to assist in making you more virtuous.
|
|
|
|
|
I tried to boot it up from a live Ubuntu CD (I changed the BIOS), and it didn't do it.
So, I guess the drive is broken 
Thanks for your help.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
