arm9

S3c2440(ARM9) spi_read_write Flash Memory

时光毁灭记忆、已成空白 提交于 2020-01-06 13:04:50
问题 I am working on SPI communication.Trying to communicate SST25VF032B(32 MB microchip SPI Flash). When I am reading the Manufacturer Id it shows MF_ID =>4A25BF but originally it is MF_ID =>BF254A. I am getting it simply reverse, means first bite in 3rd and 3rd byte in first. What could be the possible reason for that? My SPI Init function is here: //Enable clock control register CLKCON 18 Bit enables SPI CLKCON |= (0x01 << 18);//0x40000; printk("s3c2440_clkcon=%08ld\n",CLKCON); //Enable GPG2

S3c2440(ARM9) spi_read_write Flash Memory

守給你的承諾、 提交于 2020-01-06 13:04:11
问题 I am working on SPI communication.Trying to communicate SST25VF032B(32 MB microchip SPI Flash). When I am reading the Manufacturer Id it shows MF_ID =>4A25BF but originally it is MF_ID =>BF254A. I am getting it simply reverse, means first bite in 3rd and 3rd byte in first. What could be the possible reason for that? My SPI Init function is here: //Enable clock control register CLKCON 18 Bit enables SPI CLKCON |= (0x01 << 18);//0x40000; printk("s3c2440_clkcon=%08ld\n",CLKCON); //Enable GPG2

U-boot在S3C2440上的移植详解(一) --- NOR FLASH 启动u-boot

喜你入骨 提交于 2019-12-01 23:35:37
一、移植环境 主 机:VMWare--Fedora 9 开发板:Mini2440--64MB Nand, Kernel:2.6.30.4 编译器: arm-linux-gcc-4.3.2.tgz u-boot: u-boot-2009.08.tar.bz2 二、移植步骤 1 . 了解u-boot主要的目录结构和启动流程,如下图。 u-boot 的 stage1 代码通常放在cpu/xxxx/ start.S 文件中,他用汇编语言写成; u-boot 的 stage2代码通常放在lib_xxxx/board.c 文件中,他用C语言写成。 各个部分的流程图如下: 2. 建立自己的开发板项目并测试编译。 目前u-boot对很多CPU直接支持,可以查看board目录的一些子目录,如:board/samsung/目录下就是对三星一些ARM处理器的支持,有smdk2400、smdk2410和smdk6400,但没有2440,所以我们就在这里建立自己的开发板项目。 1)因2440和2410的资源差不多,主频和外设有点差别,所以我们就在board/samsung/下建立自己开发板的项目,取名叫my2440 #tar -jxvf u-boot-2009.08.tar.bz2 //解压源码 #cd u-boot-2009.08/board/samsung/ //进入目录 #mkdir my2440 /

valgrind on the ARM9?

[亡魂溺海] 提交于 2019-11-30 07:29:12
问题 I see that valgrind has an ARM7 target, but I find conflicting information on whether valgrind has support for the ARM9. The ARM9 target I am working with is running linux. Has anyone specifically succeeded in using valgrind on an ARM9 target? If so, any pointers you can offer would be helpful, including "how did you build it?". Thanks -z 回答1: Valgrind runs on ARM-v7 (architecture name), not ARM7 (chip family name). ARM7 is a name of a fairly old chip family (which uses architecture ARM-v4),

valgrind on the ARM9?

☆樱花仙子☆ 提交于 2019-11-29 04:14:41
I see that valgrind has an ARM7 target, but I find conflicting information on whether valgrind has support for the ARM9. The ARM9 target I am working with is running linux. Has anyone specifically succeeded in using valgrind on an ARM9 target? If so, any pointers you can offer would be helpful, including "how did you build it?". Thanks -z Valgrind runs on ARM-v7 (architecture name), not ARM7 (chip family name). ARM7 is a name of a fairly old chip family (which uses architecture ARM-v4), as is ARM9 (ARM-v5). Are you sure that your chip is an ARM9 and not a Cortex-A9 (which uses the ARM-v7