superboot

Mini2440 use jlink to burn superboot to norflash, jlinksuperbootJlink version: J-flash ARM V4.12J-Flash ARM configuration.Generally, some configuration files *. jflash can be found in file --> open project and loaded. However, the configuration files suitable for S3C2440 are not found. Therefore, you have created a mini2440.jflash and configured it manually:J-link settings1. Open J-Flash ARM and choose Options> Project settings.2. Set CPU options and

0x48000024 0x008e0459; DRAM/SDRAM refresh 21) Write 32bit 0x48000028 0x00000032; flexible bank size 22) Write 32bit 0x481_2c 0x00000030; Mode register set for SDRAM 23) Write 32bit 0x48000030 0x00000030; Mode register set for SDRAM 3. Flash Cancel "automatically detect flash memory" and then "select flash device ". The Flash model of mini2440 is am29lv160db or sst39vf1601. Do not rewrite any value after selection. If there is no corresponding flash model, select automatically detect flash

1. View SD card sudo fdisk-l (I'm here for the SDD don't make a mistake or you're miserable)2. Uninstalling the SD card3. Delete SD card partition FDISK/DEV/SDD D (delete) p (view)3. New Partition reserve 100M to Supperboot (that is, when the partition starts sector backward move 100M)4. Set the partition format T format L to see what format B represents FAT32 Supperboot needs to be in the FAT32 partition format5.W Saving partition content6.mkfs.vfat-n sdcar-f 32/DEV/SDD1 (formatted)7. Write the

, as shown in the figure below. 9. Several more files will be added to the temp folder. Continue! Bootimg -- Unpack-ramdisk, as shown in the figure! 10 after a few steps, an initrdfile folder and a cpiolist.txt file are generated. This is what we want to do. 11 download the rootfile superboot.zip and decompress it into the D: empinitrd folder. The files required by root include a superboot folder, which contains four files The

Problem encountered: The brush failed, the screen is not lit.Resolution: Found the embedded video to watch and solve.The reason for the original failure is. One is to choose the wrong file system of the corresponding file. SLC is the corresponding 256M Nandflash, and MLC is the corresponding 2G Nandflash. The second is to copy the superboot to the image directory. The third is the choice of Friendlyarm.ini. (For me, choose to correspond to the SLC).He

Reprint: http://www.arm9home.net/read.php?tid-83474.htmlI am the first time in this post, I hope you have a lot of support, posting purpose is to share, the purpose of sharing is to pass the spirit of open source. Tiny4412 Development Board just got hand is, read the next introduction, found that superboot is a good thing, but not open source, this serious and open source thinking does not meet. Preface:according to the CD-ROM introduction compilation

First of all, I would like to strongly condemn the friendly arm manufacturers of irresponsible behavior, the CD-ROM "Superboot-6410.bin" is not used 、、、、As a dingding well-known genuine manufacturers, buy your products with the CD-ROM contained in the file incredibly can not be used, so that a beginner of all kinds of suspicious life, doubt their IQ also forget, incredibly even my beloved memory card is I hit the label seems to be pirated. Spit Groove

Dnw application and driver compilation Instructions 1. modify the ID number: 1. make sure that the ID number enters Uboot or Superboot when the development board is powered on. Insert the USB cable to the U port of the host and use dmesg to check the connection status of the USB device. if a new device is connected to the USB device, indicates that the development board is connected... dnw application and driver compilation Instructions 1. modify the

First, make the SD boot card (install Linux) step:Burn-Write principle: Superboot-6410.bin (bootloader) + kernel image file + root file system1. Insert the SD card into the USB interface card reader and plug it into the USB port of the PC.2. Create a new "images" directory under the SD card directory3, copy "Superboot-6410.bin" to "Images" directory4. Create a new "Linux" subdirectory in the "Images" direct

, superboot, etc., you need to implement the following preparation actions. This refers to the concept of description and does not involve code.the bootloader we use in Project X projects is Uboot, and the specific code references the fourth section, "Kernel the implementation of the prepare action in Uboot" 1. Kernel image to the appropriate location of the DDR Kernel images typically exist on storage devices, such as Flash\emmc\sdcard.Therefore, the

/modules_install Restart and use Minitools to quickly start the system. Now, you can say that your basic Debian system has been completed. you can install the required utility using Aptitude, all the changes will be saved in the fs_debian_mini folder of your development host (do you know why you want to start nfs ?). After DIY, the system can create a file system image on the development host using tools provided by the friendly arm, then, according to the introduction in the Tiny210 User Manual

LCD can finally be loaded with a full screen, filled with joy, the result began on a large area of black screen, the original is part of the new board burned to write the old superboot, re-burn write new after the problem solved.LCD display principle is from point to line, the line to the surface of the continuous scanning principle, the specific design to the left and right margin of the timing of the relevant data, here will not repeat. Here is the

One. Use the Sd-flasher tool to burn superboot to sd card.1.sd-flasher.exe will partition the SD card, the first partition is 130M for storing Superboot4412, the remaining space is formatted as FRIENDLYARM partition for storing system file images.Some SD cards less than 256M are not available and we recommend using at least 4G SD cards.2. Open the CD \tools\ directory, unzip sd-flasher-1327.7z get Sd-flasher.exe burn write software, start it, please n

superboot and supported UBI, but it is not open source and never used. Then there is the Apsara stack OK6410, which uses the U-Boot provided by Samsung and does not support UBI. So come up with another method to burn the data. They used their own SD card burning tool: SD_Writer, which first burned an mmc. bin and a zImage-sd file to the sd card, the former mmc. bin is actually used for sd card startup. The latter zImage-sd is a kernel file. First, le

this case, the value of wtdat will be automatically loaded into wtcnt. The wtdatregister is used to specify the time-out duration. The content of wtdat cannotbe automatically loaded into the timer counter at initial watchdog timeroperation. However,Using 0x8000 (Initial Value of wtcnt) will drive the firsttime-out. Then, the value of wtdat will be automatically reloaded into wtcnt. 3. watchdog timer count (wtcnt) Register The wtcnt register contains the current count values for the watchdogtim

used the bin file provided by tekkamanninja (searched on the Internet), but it seems that its burning position is obviously wrong (0x30008000).Specifically, please see the two articles, the two Daniel on the burning of the location of the study, want to know the truth on the look at it:The http://blog.csdn.net/coolbacon/article/details/6262776 of CedarA leaf http://blog.csdn.net/rickleaf/article/details/6260292 in the autumn of knowingThe author finally decided to refer to the method of autumn

information for the deviceFdisk-p 0Fdisk-p 1Device MMC1 partition information, that is, EMMC analysis, note that this is the Superboot partition information, we use this partition.Partition 1 is the FAE partition, partition 2 is for system, Partition 3 is User-data, Partition 4 is cache.(3) Formatting eMMCEnter the following instruction in U-boot mode to format the EMMC device.#uboot: Fdisk-c 1 320 2057 520The partition information is returned after

tiny6410 for running? I am using the minitool tool, Preparations:1. Use the SD-flasher tool to burn the superboot into the SD card.2. Copy the images/friendlyarm. ini file on the CD to the images directory on the SD card.3. Edit the images/friendlyarm. ini file in the SD card and add the following content: USB-mode = Yes Connection steps:1. Switch the S2 switch on the development board to the SD card or nor flash start

"$ (bsp_kitl)" = "serial_uart2"Cdefines = $(cdefines)-dkitl_serial_uart2! Endif! If "$ (bsp_kitl)" = "serial_uart3"Cdefines = $(cdefines)-dkitl_serial_uart3! Endif! If "$ (bsp_kitl)" = "usbserial"Cdefines = $ (cdefines)-dkitl_usbserial! EndifPlatform \ smdk6410 \ SRC \ oal \ oallib \ sourcesAdd:--------------------------------------------------------------------------------! If "$ (bsp_debugport)" = "serial_uart0"Cdefines = $ (cdefines)-ddebug_port = 0! Endif! If "$ (bsp_debugport)" = "serial_u

This article introduces Live555 as RTSP client, s5pv210 do media terminal, hard decode NV12 image sequence.MPlayer Play YUV Command:Mplayer-demuxer Rawvideo-rawvideo W=700:H=480/SDCARD/RESOURCE/IMG_700_480.YUVCoding:1) or the same as the code superboot, indispensable, u-boot not2) Be sure to call SSBSIPMFCDECGETINBUF () before calling Ssbsipmfcdecinit () and then fill in the header (Sps/pps/sei) information. 3) Ssbsipmfcdecgetoutbuf () The status retu