TI E2E Community

Forum Post: RE: #pragma DATA_SECTION and .cinit

Georgem — Wed, 16 May 2012 19:48:00 GMT

[quote user="Paul P. (P Squared)"]The problem with marking the array const is that the values cannot be changed during runtime[/quote]

You made that point earlier. Sorry I overlooked it.

[quote user="Paul P. (P Squared)"]The real issue here is that moving data with a #pragma statement should prevent the data from ending up in the ".cinit" section[/quote]

Such is not the case. The initialization records contained within .cinit can initialize data that resides in any uninitialized section, anywhere in memory. This is the only mechanism the compiler has for initializing global variables. Note .cinit is a read-only section. Thus it can be placed in flash.

If you still want the initialization of your #pragma DATA_SECTION array to be done outside of .cinit, then I suggest this ... Do not initialize the array at all. Define yet another array called "for_init". Mark it const, and use #pragma DATA_SECTION on it. Initialize for_init with the initial values for your array. In the link command file, place the for_init section in flash. At the appropriate time, use memcpy to initialize your array with the contents of for_init.

Thanks and regards,

-George

Forum Post: RE: I2C system test mode

Rodrigo Castaneda — Wed, 16 May 2012 19:48:00 GMT

Hi Ketan:

Just to clarify, If I understood you well you want to know if I2C_DATA registry is been reseted for the short period of time in between transmission and reception. Am I right?

Regards,

Rodrigo

Forum Post: RE: hyperlink example hangs DSP core(s)

Joel Keller — Wed, 16 May 2012 19:45:00 GMT

Hi Chad,

I have a question related to this issue: Hyperlink has two sides (local and remote), and the hyperlink peripheral has access to to remote side's registers as well. This can be used to configure both sides address translation units. Is it also possible (and advisable) to reset the remote side peripheral using the remote registers, or will that cause problems?

In other words, can I assert and deassert reset on the remote side's hyperlink peripheral? Or will remote register access not work correctly when the remote side is in reset?

Thanks,

Joel

Forum Post: RE: How to address messages in SImpliciTI.

Andy Yang — Wed, 16 May 2012 19:43:00 GMT

[quote user="lhend"]

You can have only one active Token at a time (Token is implemented as single variable in the stack - look for sLinkToken and sJoinToken in the stack code), but of course you can change it at run time by using SMPL_Ioctl() function with the object IOCTL_OBJ_TOKEN.

[/quote]

Unfortunately I can not find anywhere something like IOCTL_OBJ_TOKEN.
I mean it is not declared anywhere.
When I compiling code (I try to use this: http://yawing.googlecode.com/svn/trunk/yawing/Projects/Examples/Applications/main_AP_RE.c ) I get an error:
identifier "IOCTL_OBJ_TOKEN" is undefined

I found the function SMPL_Ioctl and indeed it has no support IOCTL_OBJ_TOKEN:

[quote]

smplStatus_t SMPL_Ioctl(ioctlObject_t object, ioctlAction_t action, void *val)
{
smplStatus_t rc;

switch (object)
{
case IOCTL_OBJ_CONNOBJ:
rc = nwk_connectionControl(action, val);
break;

case IOCTL_OBJ_ADDR:
if ((IOCTL_ACT_GET == action) || (IOCTL_ACT_SET == action))
{
rc = nwk_deviceAddress(action, (addr_t *)val);
}
else
{
rc = SMPL_BAD_PARAM;
}
break;

case IOCTL_OBJ_RAW_IO:
if (IOCTL_ACT_WRITE == action)
{
rc = nwk_rawSend((ioctlRawSend_t *)val);
}
else if (IOCTL_ACT_READ == action)
{
rc = nwk_rawReceive((ioctlRawReceive_t *)val);
}
else
{
rc = SMPL_BAD_PARAM;
}
break;

case IOCTL_OBJ_RADIO:
rc = nwk_radioControl(action, val);
break;

#ifdef ACCESS_POINT
case IOCTL_OBJ_AP_JOIN:
rc = nwk_joinContext(action);
break;
#endif
#if defined( FREQUENCY_AGILITY )
case IOCTL_OBJ_FREQ:
rc = nwk_freqControl(action, val);
break;
#endif
case IOCTL_OBJ_FWVER:
if (IOCTL_ACT_GET == action)
{
memcpy(val, nwk_getFWVersion(), SMPL_FWVERSION_SIZE);
rc = SMPL_SUCCESS;
}
else
{
rc = SMPL_BAD_PARAM;
}
break;

case IOCTL_OBJ_PROTOVER:
if (IOCTL_ACT_GET == action)
{
*((uint8_t *)val) = nwk_getProtocolVersion();
rc = SMPL_SUCCESS;
}
else
{
rc = SMPL_BAD_PARAM;
}
break;

case IOCTL_OBJ_CRYPTKEY:
default:
rc = SMPL_BAD_PARAM;
break;
}

return rc;
}

[/quote]

Do I have inappropriate SimpliciTI code?

Forum Post: RE: RM48 - EMIF - Async Connection to FPGA - 3rd nWE pulse!

Anthony F. Seely — Wed, 16 May 2012 19:40:00 GMT

Stomp,

Hi, this might be something different then. I'm wondering about alignment for example. What address are you writing to ?

If you don't mind posting the snippett of disassembly and the key CPU register values (i.e. the one being used for the pointer to EMIF memory, and the CPU instruction type that does the store (is it STR, STRB etc... ) this might give some clue.

Have to check on the errata... but sounds like you may have the workaround for the other issue already in your app.

Best Regards,

-Anthony

Forum Post: RE: Problem: Fatal Error[e72] ZIGNV_ADDRESS_SPACE

Sam Elia — Wed, 16 May 2012 19:38:00 GMT

This project compiled and functioned correctly in the past. Try to compile it a year later with the new Z-stack and IAR and I get this error all of a sudden. I even tried to use Zstack 2.4 linker and the old IAR device file for cc2530 but no luck.

From reading the forums, it is suggested to define MAKE_CRC_SHDW in the compiler options but this creates more errors.

Any help is appreciated!

Forum Post: RE: is qmssIpcBenchmark really a Monolithic qpend example?

Justin32 — Wed, 16 May 2012 19:38:00 GMT

At the start of the example QMSS and CPPI are initialized (via qmss_init and cppi_init, respectively). Then a chunk of memory is provided to the Qmss_insertMemoryRegion function for the descriptors that will be initialized and used by the IPC QMSS transport. When the init code is complete Ipc_attach() is called. Ipc_attach() calls the IPC QMSS transport initialization code. The IPC QMSS transport initialization code that gets called is located in the TransportQmssSetup.c and TransportQmss.c files.

Ipc_attach() will invoke TransportQmssSetup_attach() which calls TransportQmss_create().

TransportQmss_create() invokes TransportQmss_Instance_init().

TransportQmss_Instance_init() is the "transport instance initialization code" i referred to before. This code allocates queues, initializes the descriptors as monolithic, and sets up the interrupt mechanisms between the cores. The monolithic descriptors that were initialized will be located in the memory block provided to Qmss_insertMemoryRegion prior to calling Ipc_attach().

Justin

Forum Post: RE: DAC1220 EVM Board Startup Difficulties

Michael Lindemann — Wed, 16 May 2012 19:36:00 GMT

In my first post I bolded the following: SDIEN: connected to ground (only write to device) in hopes to call attention to it. Is this statement correct? When I see my output as it is and understanding that this is a tristated line to accomodate both data input and data output I wonder if my present problem is related to this? What do you think/

Forum Post: RE: RS485 common mode disturbances

Julio Mano — Wed, 16 May 2012 19:35:00 GMT

Hi Thomas,

I really appreciate your support. Considering the results of your last test, I presume the problem has been because of higher, eventual voltage peaks in the change to signal mode, when the impedance decreases. The problem is we cannot record the signal during say 1 whole day because the analyzer we are using, Fluke Scopemeter 225C, hasn't got this function.

Thanks again for your kind help.

Julio.

Forum Post: DLP programming for control of micro-mirror array

Alonzo Espinoza — Wed, 16 May 2012 19:35:00 GMT

Hello I am a new fresh student still trying to learn more about programming the DLP Pico 2.0 kit. I have a beagleboard to communicate with the DLP projector and I am mostly interested in learning how to get the 8-bit monochrome setting, and eventually I will want to be able to manipulate the micro-mirror array. I am hoping someone can lead me in the right direction or provide me with any guides online. Please forgive me for my lack of searching the web, I have done some research and am reading through Programmer's Guide and the Application report: Using the DLP Pico 2.0 kit for structured Light Applications.

Again any help would be most helpful and I thank you for your time and patience in dealing with a "newbie" like me.

-Alonzo Espinoza

Forum Post: RE: Output current during Disable mode -on REG102(NA-3.3V) LDO Regulator

Chris Glaser — Wed, 16 May 2012 19:33:00 GMT

The 10uA spec for the TPS60151 is shutdown current. This is the current drawn by the IC when EN is low. The corresponding spec for the Reg102 is ground pin current. It is specified as 0.2uA max.

Forum Post: RE: Basic Getting Started guide

Lisa TI — Wed, 16 May 2012 19:32:00 GMT

Hi David,

I am still waiting on feedback from a few more expert colleagues. However in the mean time, do you think this thread I found might help ...

http://groups.google.com/group/pandaboard/browse_thread/thread/742d9a25743a0352?pli=1

Best Regards,
Lisa

Forum Post: RE: CDC72010EVM

Matt Sunna — Wed, 16 May 2012 19:31:00 GMT

Hi Wenjun,

VCXO typically have very tight tuning ranges, so it is important to buy a VCXO for the specific frequency desired. The CDCE72010 will tune the VCXO in order to lock to the input clock. The 491.52MHz VCXO is a very common frequency for clocking ADCs in wireless communications systems. This can be changed to 200MHz as mentioned by replacing the VCXO. The loop bandwidth sets the characteristics of the low-pass filter applied to the VCXO tuning voltage. A narrow loop bandwidth is helpful when the input reference clock needs to be cleaned as the output phase noise will be dominated by the VCXO. For a wide loop bandwidth, the output phase noise will be similar to that of the input, so this is okay when the input reference is a very clean clock.

The attached GUI (not yet released to the web) has a new loop filter tool that helps to select components and simulate the loop filter.

Best regards,

Matt

(Please visit the site to view this file)

Forum Post: AND Gate Power - SN74AHC1G09

Anthony Berwin — Wed, 16 May 2012 19:31:00 GMT

When Pin 5 (Vcc) of SN74AHC1G09 is low (or connected to ground), what happens when an external high is put on the inputs or the output?

Regards, Anthony

Forum Post: RE: error connecting to target

Lisa TI — Wed, 16 May 2012 19:30:00 GMT

Hi Kaumil,

could you please send detailed information on your settings and the steps you take? Is your project a CCS project? Could you double check you get no build errors. What do you see if you go to Window->Preferences->Code Composer Studio->Build->Code Generation Tools .... Could you send a screenshot?

Are you simply trying an example application? Which one? Do you get any error logs?

Best Regards,
LIsa

Forum Post: BLE Central Role Connect Timeout / Power Consumption

Eng351 — Wed, 16 May 2012 19:26:00 GMT

Can anyone advise what the GAP_EstablishLinkReq() timeout is for a failed connection (peripheral out of range or not advertising)?

I am working on a data concentrator which is to poll several peripheral devices at a regular interval. The data concentrator is battery powered so power consumption must be kept to a minimum.

Thanks

Forum Post: RE: Infinite loops after restarting or resetting a F28335

Lori Heustess — Wed, 16 May 2012 19:24:00 GMT

[quote user="rmb_vector"]

i'm debugging/experiencing a similar problem on the 28335 EZDSP board where i end up in the same endlesss loop after executing a few calls in main()

3FF3E6 761F MOVW DP,#0x0180
3FF3E8 060C MOVL ACC,@12
3FF3E9 ECFD SBF -3,EQ

i suspect this is some exception trap but i also don't know where i can find what gets built into the BOOTROM or examine any boot ROM .map file. Perhaps the #180 is some error code indication for the user to know what caused the exception?

[/quote]

These are the same addresses as in the first post - which is in the eCAN loader. Is your processor set to boot to eCAN?

[quote user="rmb_vector"]Is there some documentation about the code that is built in the BOOTROM in this board that might shed some light on this?[/quote]

The boot ROM guide is here:

The boot ROM source code along with map file etc is in controlSUITE (www.ti.com/controlsuite). In the default install it will be here:

C:\ti\controlSUITE\libs\utilities\boot_rom\2833x

[quote user="rmb_vector"]i'm debugging/experiencing a similar problem on the 28335 EZDSP board where i end up in the same endlesss loop after executing a few calls in main()[/quote]

Have you stepped through the calls to see where the code ends up back into the boot ROM? I suspect you are taking an illegal trap which will put you into the boot ROM where the watchdog is enabled. If this is the case, the watchdog will reset the device and if your boot mode is eCAN, you will endup in that loader.

Forum Post: RE: TPS7A4101 EN pin

Anthony Berwin — Wed, 16 May 2012 19:23:00 GMT

Hi Darwin,

Vin=12-30V, Vout=10V

Lets assume Iout=20mA. (This is an estimate.)

Thanks, Anthony

Forum Post: RE: Questions on QMSS-monolithic-qpend Core to Core Communication

Justin32 — Wed, 16 May 2012 19:23:00 GMT

I'll look into 1. and 4.

For 3. see http://e2e.ti.com/support/embedded/bios/f/355/p/188541/678107.aspx#678107

Justin

Forum Post: RE: MSP430f5510 crystal drive strength

Sylwester Nowocien — Wed, 16 May 2012 19:22:00 GMT

Hi Jens-Michael,

You have right with CMOS technology, this is obvious. I'm not quite clearly in the words (it's still my problem with the language - I'm sorry).

I know that this is real engeener work, this is not my first time:)... But in that project I need very high long term clock stability and I'm trying minimalize all factor which increase aging efects include "too much power". Since it is difficult to reasonably measure and I don't have much time, hence my question.

I see you're an engineer with a reasonable, rational approach. Have you any idea how can I speed up that process? I mean crystal aging process associated with the excessive power? Of course drive them more much power but this is bad idea because relationship between power and long term crystal stability isn't linear and as You also noticed, much power increase crystal mechanical damage faster than in normal works (let we say by 10 years) so I'm afraid that get any reasonable results in 3-4 weeks are impossible:(...

Thak you for your interest and comprehensive posts.