I have a xilinx zynq board. I download file boot.bin and plug in the required cables. But i dont know how copy file boot.bin to SD card. I must use of ISE software?
Setting up the SD card to boot on a Zynq board is very straightforward and doesn't require putting the bootloader in the MBR or other fancy filesystem tricks. The ISE software is not required once you have the boot.bin file.
As other answers have said, you need to put the SD card into an SD card reader, and connect it to your computer.
You need the SD card formatted as a FAT partition (Windows would do this by default).
Simply copy the boot.bin to the card, as a normal file.
See http://www.wiki.xilinx.com/Prepare+Boot+Medium for detailed steps to do this in Linux.
If you're booting up an OS like Linux, you'll need extra files there too. See http://www.wiki.xilinx.com/Prepare+boot+image (the FSBL and u-boot are included in the boot.bin that you have).
Can't you just use an SD card reader? Laptops usually have them built in, or they make USB-to-SD converters that are cheap.
If you want to copy the boot.bin file to the SD card, you should have a card reader of some sort (They are usually integrated in recent laptops).
However, if you want a fast solution to check your application functionality other than JTag, and couldn't find an SD reader, you can always use your mcs file and boot from QSPI.
You can refer to ZedBoard Configuration and Booting Guide listed in this link
http://www.zedboard.org/support/design/1521/11
Related
https://github.com/microsoft/Windows-driver-samples/tree/master/input/moufiltr
The given .inx only prepares the installation files for PS/2 mice - how do I modify it to work with USB-mice?
I followed the links in the answer and the comment here, but I have no clue how to add HID_DEVICE_SYSTEM_MOUSE as a Hardware ID.
The examples and documentation for the Spresense have a lot of very clear information, yet I think there's something missing for using digital mics with the Arduino IDE. Modifications to the extension board for using digital mics are very clearly documented with nice pictures. The Arduino example projects are great, showing you to record, encode, etc. And I've also understood you must tell the recorder to use the digital microphones with the following:
theAudio->setRecorderMode(AS_SETRECDR_STS_INPUTDEVICE_MIC_D);
There are also nice details in the audio documentation explaining that CXD56_AUDIO_MIC_CHANNEL_SEL must be changed from the default value of 0xFFFF4321, which is for analog microphones, to values for digital microphones. I've been able to follow the instructions for rebuilding the Nuttx kernel and spresense SDK with a new value of 0xCBA98765 which should enable eight digital mics. The last piece that is not clear is what nuttx/sdk binary files now need to be copied over to the Arduino environment. I have a Windows PC for use with the Arduino IDE and I have a Linux PC for building Nuttx and those examples. Can you please list which files on the Linux machine that I need to copy over to the Windows PC for the Arduino IDE to use the SDK that enables the digital mics? Sorry if this is documented somewhere and I overlooked it!
The instructions provided by Sony to record using the digital mic work fine! It was a hardware problem with my microphones. I was able to use the nuttx example named audio_recorder. I haven't tried with Arduino and the process of copying files from a nuttx build to the arduino build folders is still not very clear, but that's a separate issue.
I am attempting to repair a bricked Asus X53SV notebook (Asus K53SV board) by reflashing with flashrom from a Raspberry Pi. I've got it all hooked up and flashrom recognizes and reads the chip. However, I cannot determine what type of file the BIOS update is that I downloaded from Asus support site. The update I'm using is K53SVAS.315 for Aptio's Easy Flash. How can I extract the raw BIOS from this file?
After further research, I've determined that the download offered by Asus is not a complete BIOS image file. It cannot be used to reflash the EEPROM directly as it does not contain all of the information required. The built in Easy Flash utility uses this file to update only a portion of the EEPROM. The only officially supported method of repairing a bricked Asus notebook is to send it back to Asus.
I just managed to fix my bricked Asus K53E using instructions from here, yours should be similar. It requires you to download the first part of the flash from the chip and hope that this part is not corrupted.
You have to first dump the bricked flash, then reconstruct the full image by merging it with update file from Asus website using a hex editor as follows:
Reconstructed_Image 0x0 - 0x17FFFF = Bricked_Image 0x0 - 0x17FFFF
Reconstructed_Image 0x180000 - 0x3FFFFF = Update_Image 0x0 - 0x27FFFF
I am about to forensics investigation of a linux physical memory. I have dumped an ARM Linux which the profile is not listed in Volatility, so I could find the process and the latest command using Hex Editor. here is the Question, how can I create Volatility profile, should I first find the offsets of the network connection, open ports , sockets..... then go for Volatility ? by the Hex Editor I could see some information in Memory Dump, is there anyone who can help me how can I find the rest. and is it necessary to find all the offsets and address space of each information before creating the Volatility profile?
For network related investigation, do file carving for pcap file. Using tshark to extract remnants from pcap file
Are there any known delphi components or code that creates a simple virtual drive that links to a single file. example ISO file? but this time, can be read and write.
Writing a "virtual drive" requires writing a kernel-level device emulation driver (a "SCSI miniport"-based drivers seem fairly popular), which generally means C/C++ -- and that is just the start ;-)
Not a trivial task. There may be some existing [open source] code solutions that get at least some of the way there...
Here are what I have been able to find with some quick google goggles:
Wikipedia article on ISO software
WinCDEmu
WinCDEmu is an open-source utility for mounting ISO image files in Microsoft Windows. It installs a Windows device driver which allows a user to mount an image of a CD or DVD ROM and access it as if it were a physical drive.
TrueCrypt
Virtual Floppy
However, if all you need is a tool to create an ISO/VHD from a directory and not a real "virtual drive" (or, at least a virtual driver someone else is providing), then that might be a far simpler integration task...
Happy coding.