MIPS core support for ARTIK 1

[seanshpark]

We need to prepare ARTIK 1, https://www.artik.io/, which uses two MIPS core.

• Nucleus OS
• C/C++
• ...

I'll add more informations as it arrives.

[egavrin]

@seanshpark I have several questions:

• how soon it is needed?
• can we get access to SDK?
• should we support more then 256k of ram?
• should we support multithreading, since artik has two cores?

[seanshpark]

@egavrin , good questions.

• how soon it is needed?: something like when requirements are available.
• can we get access to SDK?: have to check, I think I can get the answer in this week.
• should we support more then 256k of ram? : may be not.
• should we support multithreading, since artik has two cores?: may be not

[zherczeg]

These are design weaknesses which we can avoid at the moment, but they will backfire in the future.

[egavrin]

@zherczeg which ones?

P. S. You're always welcome to list current pitfalls here and provide your ideas on how improve the situation.

[zherczeg]

Single threaded approach with global constants and limited memory

[egavrin]

@zherczeg our primary target is a constrained device with a very limited memory, which is usually a single-core microcontroller with less than 192kb of ram. We're are going to remove memory limit within further activities.

[zherczeg]

I am sorry. Since I read about the announcement of ARTIK 1, I expected that we need to support it in Jerry, and we are not fully prepared for it. Other JS engines with "context" object support can run on multicore systems with only 64K ram, and it would be good if we could do that as well. Personally I would like Jerry as the best choice for ARTIK 1.

[egavrin]

Personally I would like Jerry as the best choice for ARTIK 1.

@zherczeg me too. I think we should prioritise features that'd be important for that target. I'll rise a separate discussion for that. Currently, I plan that we'll start enhancement of Jerry since July and removing of memory limit would be one the activities.