Programming HC05 - bluetooth

HC05 comprises of BL417 and a flash memory. I want to program BL417 to use its IO pins.
can you help me with the BC417 coding. I read its datasheet and found that I can get the software from http://dev.protonbasic.co.uk/Crownhill%20QuickBlue/bluetooth_project/bluecore/CSR%20Support%20-%20BlueLab%20SDK.htm here but when I tried it wanted to create an account on qualcomm. and when I created it said 404 error.
So basically right now I need Bluelab SDK to program the BC417 of HC05.
Also if you have done any coding with that in past please share the sample code.
Thanks in advance.

Related

Make a minifilter like driver for linux

I'm new to the Linux file system. I wanted to use a mini filter like the driver for Linux, I came across various options like Hooks,DazukoFS(not used nowadays) fanotify. So I chose fanotify.
I want to modify a file before opening it. The similar work is performed by antiviruses they scan each file before opening.I'm not getting any method to do this task. Even not getting any proper documentation of fanotify using which I will be able to achieve this. I came across FAN_OPEN_PERM, again there was no example. Any help will be appreciated.
Thanks in advance.

Is it possible to make a excel-window run in the background?

I'm starting a project at work where the workers are supposed to get a scanner to scan barcodes on the vares that they use. Optimaly we would have a system supporting this, but we don't.
My thought is to be able to have excel running in the background on the computer they use to several other things, like reading newspapers and looking up todays weather etc. My understading of scanners is that they work just like a keyboard when connected to a computer, problems may then arise if someone is scanning barcodes, and another one is reading the newspaper in internet explorer, maybe the barcodes pops-up as a number in the URL(?), when it really should go to a specific cell in excel.
My question: Is it possible to make a scanner always return its values(scanned barcodes) to excel, EVENTHOUGH the computer may be used to something else at the same time?
Thanks for every thought and comment!
Have a nice weekend!
I do not think Excel would be the best solution to achieve this. It may be possible to achieve by linking to the scanner API and leveraging external libraries to listen for the scanner port etc. However, these kind of applications best be installed as system services e.g. Windows Service or as any other background application in .NET, Java, Python whatever. Excel is not the first choice technology to do these sort of things. Excel, however, can well be used for outputing this data.
What is more, honestly, the solution and feasibility will depend on the scanner API or driver.

How are low level device drivers written for Linux?

I remember reading some books about Linux Device drivers around the end of my university education for Comp. Science. Soon there-after I got a job and haven't really worked much with Linux/Embedded (I do mostly java stuff now). However it's something I want to look into.
Anyways I recall reading an online article (ill edit post if I can find it) about writing a USB Driver for Linux for a Little "USB Missile Turret" similar to this:
http://www.thinkgeek.com/geektoys/warfare/8a0f/
Anyways it went into detail about how to write the driver without a driver being provided (the guy just found a generic one on ebay....and figured out how to like...write the driver just by looking at the components and such). ANYWAYS it was pretty amazing.
I have a pretty good clue about how low level embedded stuff works, but thats for stuff like AVR's/PIC Microcontrollers, I have no idea how something like this would be written for like a Normal processor in a PC.
Anyways I guess what Im asking is.....how do you figure out this kinda stuff, where would I find such information.
edit: found the link
http://matthias.vallentin.net/blog/2007/04/writing-a-linux-kernel-driver-for-an-unknown-usb-device/
(It's way more confusing then I thought, I didn't realize he reverse engineered a Windows USB driver..im guessing it'd be impossible to figure out without snooping through a windows driver?)
The Linux kernel and drivers are GDFL source. You can read the code, change them, compile them, and experiment to your heart's delight with them. That is a pretty good way to learn.

TI-99 speech effect?

I want to make a program that takes recorded speech and transforms it so it sounds like it's coming from a Texas TI-99. Do you have any good ideas and resources for how to go about that?
Most of those old speech synthesizers were build directly in-chip. Perhaps you could find a synthesizer that sounds like the chip, but if you really want the original sound, you would either have to simulate the chip (I don't know if it's a simple matter, perhaps the chip internals aren't published).
I only know because I burnt out a number of the Radio Shack speech synthesizer ICs before I managed to get a SP0256-AL2 working.
If you're more of a do-it yourself type guy, you need to find out which IC actually drove the speech synthesis in a TI-99, and then build the chip up on a bread board. That's what I was trying to do back then, and I managed to get the chip to speak, but lost patience after I fried my third chip due to a mis-wiring issue when I attempted to attach it to my PC's parallel port. I think this was the book I was using back then, but there's no cover art featured so it's hard to know for sure.
If you are familiar with how to use ROM images, there seems to be a gentleman that has managed to refeverse engineer the ROM image out of a SP0256-AL2. Look here for the image and the incredible granted permission to do the work and distribute the results.
You could start with open source that does something similar: Adding Robotic/Vocoder effect to your song using Audacity

New to Linux Kernel/Driver development

Recently, i began developing a driver of an embedded device running linux.
Until now i have only read about linux internals.
Having no prior experience in driver devlopment, i am finding it a tad difficult to land my first step.
I have downloaded the kernel source-code (v2.6.32).
I have read (skimped) Linux Device Drivers (3e)
I read a few related posts here on StackOverflow.
I understand that linux has a "monolithic" approach.
I have built kernel (included existing driver in menuconfig etc.)
I know the basics of kconfig and makefile files so that should not be a problem.
Can someone describe the structure (i.e. the inter-links)
of the various directories in the kernel-source code.
In other words, given a source-code file,
which other files would it refer to for related code
(The "#include"-s provide a partial idea)
Could someone please help me in getting a better idea?
Any help will be greatly appreciated
Thank You.
Given a C file, you have to look at the functions it calls and data structures it uses, rather than worrying about particular files.
There are two basic routes to developing your own device driver:
Take a driver that is similar to yours; strip out the code that isn't applicable to your device, and fill in new code for your device.
Start with the very basic pieces of a device driver, and add pieces a little at a time until your device begins to function.
The files that compose your driver will make more sense as you complete this process. Do consider what belongs in each file, but to some extent, dividing a driver among files is more an art than a science. Smaller drivers often fit into just one or two files.
A bit of design may also be good. Consider what you device does, and what your driver will need to do. Based on that, you should be able to map out what functions a device driver will need to have.
I also believe Linux Device Drivers, Third Edition may help you get on your way to driver development.
Linux files themselves include files based on what they do, what layer they are in, and what layer they access of the call stack. The Big Picture truly informs how each file is related to the next.
I had to fix a kernel driver once. My biggest tip (if you use vim) is to set it up with ctags so you can jump around the kernel source with ctrl-] every time you see a function you don't understand.

Resources