I guess the sequence of Cortex-A53 entering retention mode is that, firstly CA53 executes a WFI instruction to enter the standby mode, secondly power controller checks with CA53 logic by Q channel to make sure CA53 is ready, lastly power controller reduces the voltage of CA53. Is this sequence right? If it's right, most logic of CA53 is clock gated in standby mode, then what is the purpose of Q channel, can we only use WFI to enter rention mode? Thanks.
↧
A question about Cortex-A53 retention mode
↧
Re: Are there any ARM v8-based development boards available on the market yet? If not, when should we expect to see them?
Hi Joanna,
I believe the first ARMv8 development board will be available from Applied Micro - they have a pre-order page here X-C1 Server Development Platform | AppliedMicro
There is also a thread on the ARM Linked in channel (http://www.linkedin.com/groups/Any-information-regarding-availability-development-85447.S.277889064 ) with a number of links to ARMv8 development tools, fast models etc.
Hope this helps
Alan
↧
↧
Re: cortex m3 swd gecko
Hi James, Thanks for the reply. Even i'm following the same document. i'm following the same sequence that you specified above.
First 5 steps are getting executed with out any issue , but when i try to write (step 6) into AP register (ie csw), things get messed up.
We are suspecting an error related to write buffer.
other thing that could be suspected is any missing initialization or reset sequence that enables AHB-AP interface.
Regards
Venkat
↧
中文社区积极用户奖励方案(2014年3月1日至2014年6月30日）
各位用户大家好，
我是中文社区的管理员Song Bin 宋斌。
非常感谢大家一直以来对中文社区的支持和帮助。
为了鼓励大家在中文社区内发帖、回复、提问、分享。
我们特地设置了一个中文社区积极用户奖励方案。
具体细则如下：
参与对象： 2014年6月30日以前，关注中文社区，并且积极参与的ARM互联社区用户。
活动期间：2014年3月1日起 至 2014年6月30日 截止
活动方式： 凡在中文社区内用中文参与发帖，回复，提问，分享等活动，并获得社区积分者，我们会进行排序
在6月30日结束后，排名前两位的用户（管理员除外，也就是Song Bin 宋斌和 Jenny Su 苏琴不算） 即可获得一台新版Amazon Kindle Paperwhite。
如何获得积分，请参考这篇文档
积分计算区间为2014年3月1日0时起，至 2014年6月30日24时止。
我们会每个月月初定期公布论坛排名前十的用户积分情况。
欢迎大家积极参与。 有问题可以联系我Song Bin 宋斌。
此外，我们2014年全年度也会有相应的更大的奖励，请大家多多留意我们的活动通知。
以下是2014年3月1日至2014年3月31日的前10名用户情况，供大家参考，机会不容错过，大家抓紧啊
| 排名 | 用户 | 积分 |
|---|---|---|
| 1 | Xingguang Feng | 59 |
| 2 | yongfeng | 40 |
| 3 | 月之痕 | 18 |
| 4 | Lifeng Geng 耿立锋 | 15 |
| 5 | liuxingliang | 10 |
| 6 | zhangzheng | 8 |
| 7 | Wally Mao | 6 |
| 8 | George Wang | 6 |
| 9 | Bob Peng | 6 |
| 10 | Evens Pan | 5 |
↧
Re: DS-5 Debugger hang issue, while debugging c/c++ application on Baremetal cortex-A8 using RTSM model?
Are you running the DS-5 Debugger (red debug icon)? It might be worth double checking your debug configuration (by right clicking in the Debug Control view and selecting "Debug Configurations") to make sure that it's referencing the right executable.
The best thing to do might be to modify one of the example bare metal applications:
Hope this helps,
Joe
↧
↧
Re: A question about Cortex-A53 retention mode
For information on retention mode I suggest you contact ARM's support department.
↧
what is the risk of calling a non RAM function from a RAM function?
I got a code (work with IAR EWARM) that has some function defined as __ramfunc to do some writing in the flash.
When compiling I'm getting some warnings like:
Warning[Ta023]: Call to a non __ramfunc function (somefunction) from within a __ramfunc function
Warning[Ta022]: Possible rom access (<ptr>) from within a __ramfunc function
Warning[Ta021]: Library call (__aeabi_uidivmod) from within a __ramfunc function
I suppose the code is properly paged, so the area used as data flash has nothing to do with the code where the processor could fetch code, then the warning can be ignored if that is double checked. Is there any other hidden source of problems with this?
↧
Unable to Compile My First Project
I am a newbie in ARM programming and have installed Flash / KEIL E.
While trying to generate hex code for my MCU as mentioned in URL Lesson 2: LPC2148 GPIO (Basic Input and Output) > I am getting error during compilation:
GPIO0_IOCLR |= LED1; //GPIO0_IOCLR used of um-identified identifier..
How can I solve the issue and generate a hex file?
↧
Re: Unable to Compile My First Project
You are probably missing the definition of LED1:
#define LED1 ... some pin in your board....
or else you have the definition in some file.h and you are missing it to be included:
#include "file.h"
Don't desperate, even after many years it won't compile the first time.
↧
↧
Re: A question about Cortex-A53 retention mode
OK. I have already found Cortex-A53 TRM in ARM official website, but I can't find explicit explanation about this question from it.
↧
Proteus : Gives error for my first example
Below is my code for which I have generated the hex file:
#include "lpc214x.h"
#define LED1 (1 << 10)
#define LED2 (1 << 11)
#define BUTTON1 (1 << 15)
#define BUTTON2 (1 << 16)
// Method prototypes
int getPinState(int pinNumber);
int main(void)
{
// Set buttons as input
PINSEL0 &= ~(BUTTON1 | BUTTON2);
// Set LEDs as output
PINSEL0 |= (LED1 | LED2);
// Turn both LEDS off (set them 'high')
IO0SET |= (LED1 | LED2);
while (1)
{
// Check if button 1 is pressed
// Released = 'High' (1)
// Pressed = 'Low' (1)
if (getPinState(15))
{
// Button1 is currently 'high'
// Turn LED1 off
IO0SET |= LED1;
}
else
{
// Button1 is currently 'Low'
// Turn LED1 on
IO0CLR |= LED1;
}
}
}
int getPinState(int pinNumber)
{
// Read the current state of all pins in GPIO block 0
int pinBlockState = IO0PIN;
// Read the value of 'pinNumber'
int pinState = (pinBlockState & (1 << pinNumber)) ? 1 : 0;
// Return the value of pinState
return pinState;
}
Also attached is my PROTEUS simulation model. But in PROTEUS I am getting error?
↧
Re: Can't compile any shader with the OpenGL ES 2 Emulator
Hi degenerated,
Can you let us know the OS you're running under?
Thanks,
Chris
↧
Re: Some questions in Porting to ARM 64-bit White Paper
gcc 4.8.2 manual:
-mfpu = crypto-neon-fp-armv8, etc.
↧
↧
Re: Cache question about ARMv8's free licensed FVP model
hi, Martin:
Thanks a lot!
↧
Re: Can't compile any shader with the OpenGL ES 2 Emulator
Hi Chris,
I'm on Windows 8.1 64-Bit, using the newest stable Nvidia driver (Version 335.23).
The Mali-Offline-Compiler works fine by the way. Is there any way to see what the emulator does to make the shader compatible to OpenGL 2 in the glShaderSource-Call?
↧
Re: Re: Can't compile any shader with the OpenGL ES 2 Emulator
Okay, I used gDebugger to see what is getting passed to openGL, and there IS a makro, starting with GL_. This is the Vertex-Shader from the Cube-Example after it has gone through glShaderSource:
#version 120
#define GL_ES 1
#define gl_MaxFragmentUniformVectors (gl_MaxFragmentUniformComponents / 4)
#define gl_MaxVertexUniformVectors (gl_MaxVertexUniformComponents / 4)
#define gl_MaxVaryingVectors (gl_MaxVaryingFloats / 4)
#define gl_MaxCombinedTextureImageUnits (gl_MaxCombinedTextureImageUnits < 8 ? 8 : gl_MaxCombinedTextureImageUnits)
#define gl_MaxTextureImageUnits (gl_MaxTextureImageUnits < 8 ? 8 : gl_MaxTextureImageUnits)
attribute vec4 av4position;
attribute vec3 av3colour;
uniform mat4 mvp;
varying vec3 vv3colour;
void main() {
vv3colour = av3colour;
gl_Position = mvp * av4position;
}
Now how do I get rid of the "#define GL_ES 1" inserted by the emulator?
Edit: Used a Hex-Editor and tried to find that line in libGLESv2.dll. Found 2 of them and changed them to lower case. Now it's working. Still, why does the emulator put it there in the first place, if OpenGL complains afterwards?
↧
Re: Differences between ARMv7 to ARMv8?
Good question. I and probably most of the rest of the world thought ARMv8 meant the 64-bit version of the instruction set and some system changes to support it. However the 64 bit instruction set is described by Aarch64 or as Linus prefers to call it ARM64. And then ARMv8-R was announced and currently it only includes the 32 bit instructions. The defining part of ARMv8 seems to be all the new system stuff - things like how interrupts are handled and the support for controlling access to shared memory areas. It introduces Aarch64 but does not require it. That at least is my reading of it all now.
↧
↧
Where to find a simple example ready to compile and link?
Where can i find a simple example which is ready to compile and link?
I am using RVCT 4.0 (compiler) for an ARM AM3517 (processor) on a Zoom AM3517 EVM Development Kit (board)
↧
Re: OpenGL ES 2.0 Emulator: Strange behavior when using a varying
Hi Pete,
It fails with float3(0.0,0.0,1.0), too.
Anyways,hardcoding the normal value (which isn't used in the pixel shader) shouldn't corrupt the data for the texture coordinates, right?
I have yet to get this to break in a simple example, but I'm on it.
↧
Re: Distance measurement by ARM1176JZF-S(DS- 5 TOOLS) using ultrasonic sensor
The main problem is that I do not have any example project. I tried some experiments, I am not being able to change/modify the GPIO pins.
↧