I'm having a problem with AVRDUDE. It does not even attempt to write the hex file to the AVR. In WinAVR there is no problem. (I can't use WinAVR, because I've got only the hex file.)
L:\>avrdude -c SAJAT -p t2313 -P COM1 -U flash:w:main.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x1e910a
avrdude: safemode: Fuses OK (E:FF, H:DF, L:E0)
avrdude done. Thank you.
avrdude.exe, avrdude.conf and the main.hex files are located in the same folder.
SAJAT is my version of the DASA programmer (different pin assignment), and this works fine. The target is ATtiny2313 with an external 12 MHz clock. I am using AVRDUDE 6.1 on Windows 7 64-bit.
Writing fuse bits works.
What is the problem here?
I've only uploaded a hex file, but I don't know if this will work with EEPROM files as well or not.
Step 1:
Create a simple program in WinAVR, like an LED toggle.
Name it as you like. I named it 2313.c
Step 2:
Compile it in WinAVR.
Now you have not only the 2313.c file, also the 2313.hex and other files as well.
Step 3:
Burn this into the target device with WinAVR. This is important for future steps. Don't close the program after burning is completed.
Step 4:
Rename the hex file you want to burn to your AVR to 2313.hex (myhex_to_burn.hex -> 2313.hex). Copy the renamed hex and overwrite the complied one with it. Now copy all these files (makefile, .hex, .c, ... etc.) where your AVRDUDE is located.
Step 5:
Open AVRDUDE. (Start -> cmd - > go to AVRDUDE location.)
Open WinAVR and select the first line at its Output window. You should find something like this:
avrdude -p attiny2313 -P com1 -c sajat –U flash:w:2313.hex
Copy it and paste it into AVRDUDE with right click and insert.
Step 6:
Prepare your target AVR for programing (connect it to the ISP programmer, power, etc.)
Press Enter.
Related
I am trying to run a script which finds the pitch of a waveform, however I am getting an error that it cannot open a wav file, and I don't know why this is.
The code is:
../../SPTK-3.11/bin/pitch/pitch -a 0 -s 16.0 -p 80 -t0 0.0 -L 40 -H 150 -o 1 ../wav/*.wav > f0
And the error is:
Cannot open file ../wav/arctic_a0254.wav!
There are around 500 wav files in the folder, so I don't know why it doesn't list the first here if there is a problem with the path or the file
I have already tried doing ls ../wav which shows all the files as being in that directory, and did open ../wav/arctic_a0254.wav which also worked, so I don't know why there is an error here.
EDIT: I tried removing the wav file from the folder, and got the same error with the proceeding wav file (arctic_a0255.wav), so I don't think it is to do with the individual wav file.
EDIT2: The script lists the error as occurring when there is an error seeking the beginning of the audio container, but I'm not sure what this means
EDIT3: Solved! The issue was the file not being a float, so I converted the wav in audacity and the script worked as normal
I believe that the program you are executing, pitch, runs out of file descriptors.
I don't know whether it fails to close already used files, thus leaking file descriptors, or whether it really needs to keep all those files open for performing its task, which would be more difficult to fix.
You can try to strace it and see the exact error you get from the read() system call just before bailing out.
Do you have access to the source?
Can you run it in smaller batches?
I use UBIFS for rootfs on NAND.
When I edited a file like /etc/rc.local with nano command and saveed it,
"cat /etc/rc.local" shows the editted content, of course.
However after removing power supply (without reboot or poweroff command) and supply power again, the content of /etc/rc.local becomes empty.
I found that written data is not written to NAND straight away in UBIFS and written to cache. (refer: http://www.linux-mtd.infradead.org/faq/ubifs.html#L_empty_file)
I want to sync to NAND straightly after editting.
Only solution I found is fsync, but this should be called in C program and it requires file descripter. Nano command and so on does not give us file descripter. So I can not solve this sync problem.
How can I solve this not syncing to NAND problem?
Are there any command to sync?
Do I have to edit files with C program and use fsync if I want to edit and save a file in UBIFS?
You can use the 'sync' command. the system will flush all the cache to the disk.
I am doing a lab for my class using Code Composer Studio and the Tiva Launchpad. I am using a macbook and I have downloaded PuTTy using MacPorts. Now that PuTTy is running I have to type in the serial line to communicate with CCS and the Launchpad.
It is necessary to type in the serial line for connection to work,
PuTTy Serial line
Any help or direction is very appreciated! First time posting sorry if I am unclear at any point.
Here's an easy way to find the device special file for any device.
Unplug the device and reboot your system.
Get a list of all device special files in /tmp/a
ls /dev > /tmp/a
Now plug in your device and wait a few seconds, and get a list of the device special files again, this time in /tmp/b:
ls /dev > /tmp/b
Now compare /tmp/a with /tmp/b:
opendiff /tmp/a /tmp/b # Yes, you could use "opendiff /tmp/[ab]"
Whatever is new in file /tmp/b corresponds to what you plugged in.
I am trying to build installer using InstallShield's commandline tool IsCmdBld.exe. It builds something, but when I try to open it, it returns following error.
I have used
"C:\Program Files (x86)\InstallShield\2015\System\IsCmdBld.exe" -p "D:\Installation_Builds\MyInstallations\MyInstaller.ism" -r "Compressed EN Build" -c COMP -a "CompEN"
as a command. Seems very straight forward. In fact if I do not insert -c COMP and generate uncompressed installer, it has no problem. However, the size of installer over all becomes 23GB so it is not acceptable.
I do see ISDEV : fatal error 0: followed by nothing else. I googled a bit and found http://flexerasoftware.force.com/ka1G0000000TljoIAC but I cannot seem to understand why this is occuring when I can perfectly build it without the use of commandline tool.
Any inputs would be appreciated. Thank you.
EDIT : after adding -v to the building command, little bit more detailed error showed up.
1627: Error saving the changes to [XX.msi]
I do not know why it is erroring on saving the change.
make sure your .msi is not readonly.
the best way we found for using the isCmdBld is with this cmdline :
ISCmdBld.exe -p "%ProjectName%" -a "%Configuration%" -r "%ReleaseName%" -x -o "%MergeModulePath%" -prqpath "%PRQPath%"
you'll have to make sure the %Configuration% and %ReleaseName% are the exact same as those in the ism (case Sensitive) (Media|release).
I am successfully able to create and boot a little OS generated from buildroot on my embedded system.
Buildroot generates a cpio.
I decompress it (a working cpio, that boot with no problem )with
cpio -iv < ../rootfs.cpio
in a directory. After that I compress it again with
find . | cpio --quiet -o -H newc > ../rootfs.cpio
that is the command used in buildroot (in cpio.mk:31)
but at this point that cpio do not work anymore. If I compile my kernel with that file I get a kernel panic.
File persmission seems the same. With bcompare I saw that the "re-compressed" file has some additional zero at the end, just before the init script. I've tried to remove them, but at this point the system freeze, maybe there is some CRC check somewhere.
Any ideas?
the point is that I'd like to start from buildroot but I want to add my stuff to that rootfs and then embed it into my kernel.