DM385/DM388 support

Hi sir,

1.We would like to get the IPNC SDK from 3rd party,Do we need to have IPNC license from TI first?

2.We would like to implement the "deep sleep mode" function on dm385/dm388,Do you have any software/hardware documents for us reference? thank's.

Best Regards,

Byron

Byron Tien said:

1.We would like to get the IPNC SDK from 3rd party,Do we need to have IPNC license from TI first?

I will notify the IPNC RDK team to comment here.

BR
Pavel

Byron Tien said:

It seem to have support OSC_WAKE  pin on DM385/DM388 to control DeepSleep mode.Is it right?

Right, the physical pin is U28/DEVOSC_WAKE controlled by PINCNTL7/0x48140818

Byron Tien said:

How about the software side?How do we control this pin for this mode?

Refer to the wiki page below:

See also:

Regards,
Pavel

Hi Pavel,

Any update on above post ?thank's.

Best Regards,

Byron

Hi Sir,

Thank's. for your description.So if we would like to control deep sleep mode.

1.Enter deep sleep mode

>>triggers suspend through sysfs entry - /sys/power/state.

 means that input the parameter into /sys/power/state by s/w?What the parameters we need to input?

2.Wake up

>>OSC_WAKE switch pressed - User enable the OSC clock by pressing OSC_WAKE.

 means that pin has to be wired to a button . When you need to wake it up, push that button.??

BTW,how about the IPNC license issue?

thank's.

Best Regards,

Byron

Byron Tien said:

Any update on above post ?

What kind of update on which post exactly?

Byron,

Byron Tien said:

if we would like to control deep sleep mode.

1.Enter deep sleep mode

>>triggers suspend through sysfs entry - /sys/power/state.

means that input the parameter into /sys/power/state by s/w?What the parameters we need to input?

You need to input "mem"

# echo -n "mem" > /sys/power/state

But before to pass "mem" parameter to /sys/power/state, you need to change from the StandBy mode (default mode) to DeepSleep mode, using the
enable_deep_sleep flag. 

The steps are:
1.Mount debugfs
2. set to 1 enable_deep_sleep flag
3. pass "mem" to /sys/power/state

More info you can find in the below wiki:

Byron Tien said:
2.Wake up
 
 >>OSC_WAKE switch pressed - User enable the OSC clock by pressing OSC_WAKE.
 
 means that pin has to be wired to a button . When you need to wake it up, push that button.??

Correct

Byron Tien said:
BTW,how about the IPNC license issue?If we would like to get the IPNC rdk code from 3rd party,do we need to have IPNC license from TI first?


I have never heard about IPNC license, but I am not IPNC expert. You can check this with your local TI FAE.

 

Pavel

Byron Tien said:

BTW,how about the IPNC license issue?If we would like to get the IPNC rdk code from 3rd party,do we need to have IPNC license from TI first?

Even there is license requirement, this should be handled with TI FAE or sale representative. I do not see how license can be handle over public forum!

Regards,
Pavel

Hi Pavel,

Thank's for your reply.We still have some questions on this topic.Please help,thank's.

1.

You mean that  Deep Sleep Mode is defined to be the same as Standby Mode, with the addition of gating the crystal oscillator to further eliminate all active power. The device core voltages can be reduced for optimal power savings.

So if we enter this mode,Will those behaviors("the addition of gating the crystal oscillator to further eliminate" and "device core voltages can be reduced") be activated by system automatically without adjusting any hardware design?or we need to adjust our hardware design?

2.

Yesterday we got a DM385 IPNC EVM board.we found that the OSC_WAKE pin on EVM seem to tie with PullUp directly not  wire to a button.We are so confused.Why are they different? Is it  just the potential changed(high or low)? Do we need to adjust our hardware design?or we also tie it with PullUp?

Do you have any hardware design with OSC_WAKE pin for our reference? 

thank's a lot.

Best Regards,

Byron

Byron Tien said:

You mean that  Deep Sleep Mode is defined to be the same as Standby Mode, with the addition of gating the crystal oscillator to further eliminate all active power. The device core voltages can be reduced for optimal power savings.

So if we enter this mode,Will those behaviors("the addition of gating the crystal oscillator to further eliminate" and "device core voltages can be reduced") be activated by system automatically without adjusting any hardware design?or we need to adjust our hardware design?

If DeepSleep is enabled, suspend sequence will cut the Cortex-A8 ARM clock, else (in StandBy mode) Cortex-A8 ARM will remain active and will enter idle state.

Then to be able to wake-up from DeepSleep, you will need to adjust your custom board to have button to enable the OSC clock.

DeepSleep suspend/resume is handled by SW, you will only need to have button for the Wake-up.

Byron Tien said:

Yesterday we got a DM385 IPNC EVM board.we found that the OSC_WAKE pin on EVM seem to tie with PullUp directly not  wire to a button.We are so confused.Why are they different? Is it  just the potential changed(high or low)? Do we need to adjust our hardware design?or we also tie it with PullUp?

Do you have any hardware design with OSC_WAKE pin for our reference? 

Regarding DM385 IPNC EVM questions, you can ask your DM385 IPNC EVM supplier. Check for the latest version of the EVM.

The DM814x TI EVM has OSC_WAKE button only in the latest version of the board (rev D). You can get the latest documents for DM814x TI EVM from the Mistral web site:

HARDWARE -> Downloads for TMDXEVM8148 – Base Board -> Rev - D -> Schematics -> PDF Format

Hi Pavel,

thank you.

How about the power consumption?When we enter the deep sleep mode,how much power consumption per component??

Best Regards,

Byron