I am trying to use TI-Editor as mentioned in this tutorial. I can write a program using this editor on my laptop, but in order to test can I use any emulator or app on my laptop or mobile.
Because as of now I don't have USB wire to the calculator. Which I will get in some period of time, but till then can I check the programs written by me.
I am aware of some emulators but in that I have to write the whole program again manually, is there any laptop emulator in which I can copy past my code and test it.
I am coding the programs as per TI-83 Plus calculator.
Related
I'm playing around with the board in the question and I'm struggling with it even though I'm fairly familiar with the F767 Nucleo. What I want:
to reprogram the demo that came on to the board for now, as I haven't managed to get the display on the board working at all since before then. I've downloaded the stm32f769 disco demo that includes the appropriate .HEX
What I've done:
I've upgraded st-link using the upgrade utility. Within STM32 Cube programmer, I've selected the appropriate External Loader for my disco board. My board is connected via st-link and is recognised by cube programmer.
On the erasing and Programming tab I've selected the correct .HEX file and the device begins to program. The file is about 120MB and so takes a good while to program.
Once the programming has complete, cube programmer tells me that it was successful. However the screen is just displays the blue ST logo on a white background and nothing else. Nothing changes when tapping the screen or pressing the reset button (apart from a reset of course).
Any help would be appreciated, something simple as programming the board shouldn't be this difficult so I'm clearly doing something wrong.
Have you read the readme.txt?
Did you click on "External Loader" from the bar menu then check "MX25L512G_STM32F769I-DISCO" box?
because you need to flash the QSPI together with the internal 2MB memory.
Taken from the readme.txt in the downloadable zip.
#par How to use it ?
The QSPI external flash loader is not integrated with supported toolchains, its only supported with STM32
ST-Link Utility V3.9 or later
To load the demonstration, use STM32 ST-Link Utility to program both internal Flash and external QSPI memory.
To edit and debug the demonstration you need first to program the external QSPI memory using STLink utility
and then use your preferred toolchain to update and debug the internal flash content.
In order to program the demonstration you must do the following:
1- Open STM32 ST-Link Utility, click on "External Loader" from the bar menu then check
"MX25L512G_STM32F769I-DISCO" box
2- Connect the 32F769IDISCOVERY board to PC with USB cable through CN16
3- Use "STM32769I-DISCO_DEMO_VX.Y.Z_FULL.hex" file provided under Binary with STM32 ST-Link Utility
to program both internal Flash and external QSPI memory. this demo to take benefit from Touch-GFX
and EmbeddedWizard third parties demonstrations modules replacing Gardening control and Home alarm modules.
4- copy the audio and video files provided under "Media/" in the USB key
5- Plug a USB micro A-Male to A-Female cable on CN15 connector
6- Plug a headphone into CN7 Connector.
-> The internal Flash and the external QSPI are now programmed and the demonstration is shown on the board.
So various people around my house have been stealing my mouse and I was wondering if I could store a program on the mouse which runs whenever it's plugged in, asking you for a password. I know you can run a program stored on a computer when a device is inserted into a USB slot but that means I can't stop people using my mouse if the specific laptop he's using hasn't got the program installed.
Also, if this was possible, what language would use? I would like it to work on windows, linux and OSX to cover all bases.
Thanks for any help!
I almost understand how to send message device to device.
But, I don't know how to do this with pc.
I tried to find it, but the most curious thing is,
'How can I make server side program on pc?'
I know how to provide web service by server, but for that, I have to make environment like APM on PC.
But, that's not what I want. Because it means, someone who want to use that program should make environment like that I have.
Actually, I tried to make remote controller application like X-remote...
That kind of applications, just download program and install it on pc, then pc act as a server.
what is it made from? C#? php? Java swing?? I have no idea about that...
Device is Tizen, so we will make a web app.
How can I make pc program like other remote application?
It seems that right now you cannot emulate Bluetooth on Emulator. As far as I remember when developing some sample applications, we have been using some fixed data. You could also write whole application using simple PHP server, and change the communication from HTTP to Bluetooth at the end of development.
Please analyze BluetootchChat sample application in the SDK, it should give you an overview about the BT communication in JavaScript.
Remember about the privileges in config.xml file.
I've received a project from someone that includes an Arduino (Uno) board with some sensors and lights with an USB cable and a documented protocol for communicating with this board through a COM port. It works fine with some existing code, but I need to port the whole project to a Windows RT environment using an ARM processor and including the Metro interface for the application. And it's going to be completely rewritten...
First of all, my Windows RT device does have an USB port so it can connect to the board. But the challenge is to communicate with the board to read out the sensors and manipulate the lights and I happen to have problems finding some useful libraries, tutorials or other information about how to make these work together.
This project works fine with other Windows versions, though. I just need something specific for Windows RT/ARM/Metro.
Currently it is not possible to do this on Windows RT, and here is an explanation why. As a work around I am using a standard full screen WPF application in combination with the Surface SDK for touch enable UI components. The obvious disadvantage here is that you cannot publish the app to the store.
I think that we should actually try it on a real machine instead of the rt. The surface rt is basically for documents and the internet.
You'd be better off trying all of this with a Toshiba 2032.
A PDA from about 2003.
We have some boxes running Windows XP for an automated production process. I (not me personally but a robot) connect new USB devices to these boxes. There is a device driver for this device type and it's loaded after connecting a device and running like a charm.
But ... it takes about 8 to 10 seconds after pluging in a new device until it is accessible. When I connect an already previously seen device again it only takes 3 seconds. The driver has a catalog file. It's not signed by Microsoft WHQL but uses a test certificate we have installed on the machines.
There is only one inf/pnf file to be considered and so I wonder why it takes so long to detect a new device, create the information in the registry and load the driver.
Time is money and so I need to speed up the process.
Any hints for me? Especially does somebody know that WHQL-certified drivers are recognized more quickly by Windows / device manager?
These devices have unique serial numbers, correct? That's part of what Windows uses to create the per-instance data necessary to track whether it's seen this device before. In the case where you plug in a device that's already seen before, Windows will pick up the old instance data and load the appropriate driver. If you plug in a device that Windows has never seen before (e.g. same VID/PID but different serial number), it needs to go through the process of creating registry entries, parsing the INFs to find the correct driver, etc.
Are you sure those devices that show up quickly with WHQL'd drivers have never been attached to the system before? Also, are these systems configured to connect to Windows Update to look for drivers when a new device is attached? It's definitely true that Windows will prefer a WHQL'd driver over an unsigned (or self signed) package, so it's possible that Windows is trying hard to find something else before defaulting to your self signed driver.
-scott