Re: [HELP] Barebox porting

2019-01-28 Thread Sascha Hauer
On Fri, Jan 25, 2019 at 05:11:01PM +0300, Seraphim Dolbilov wrote: > Hello, friends! > > I'm interested if there is any internal Barebox convention about > return types and values of initcall functions. What shall return > my initcall if I want to stop booting and display error message? An error

Re: [HELP] Barebox porting

2019-01-28 Thread Sascha Hauer
On Fri, Jan 25, 2019 at 03:18:04PM +0300, Seraphim Dolbilov wrote: > Hello Sascha, > > 23.01.2019, 13:17, "Sascha Hauer" : > > How is the integrity checked? Some md5sum or something? Anyway, you're > > better off doing that in C. > > Well, how can I call C functions from shell without

Re: [HELP] Barebox porting

2019-01-25 Thread Seraphim Dolbilov
Hello, friends! I'm interested if there is any internal Barebox convention about return types and values of initcall functions. What shall return my initcall if I want to stop booting and display error message? --  Yours sincerely, Seraphim Dolbilov

Re: [HELP] Barebox porting

2019-01-25 Thread Seraphim Dolbilov
Hello Sascha, 23.01.2019, 13:17, "Sascha Hauer" : > How is the integrity checked? Some md5sum or something? Anyway, you're > better off doing that in C. Well, how can I call C functions from shell without implementing own shell command? --  Yours sincerely, Seraphim Dolbilov

Re: [HELP] Barebox porting

2019-01-23 Thread Sascha Hauer
On Wed, Jan 23, 2019 at 01:01:46PM +0300, Seraphim Dolbilov wrote: > 23.01.2019, 12:11, "Sascha Hauer" : > > What are you trying to archieve? > > My board contains mcp79411 - it's an I2C RTC with EEPROM, which contains > global-registered MAC address. I want this MAC address to be read by Barebox

Re: [HELP] Barebox porting

2019-01-23 Thread Seraphim Dolbilov
23.01.2019, 12:11, "Sascha Hauer" : > What are you trying to archieve? My board contains mcp79411 - it's an I2C RTC with EEPROM, which contains global-registered MAC address. I want this MAC address to be read by Barebox and passed to Linux kernel FEC driver through bootargs. I was trying to find

Re: [HELP] Barebox porting

2019-01-23 Thread Sascha Hauer
On Tue, Jan 22, 2019 at 07:12:16PM +0300, Seraphim Dolbilov wrote: > How can I get an output of a shell command in hush shell? > Backticks and $() cannot do not work :( You can't get the output of a command, that's not implemented. Some commands work around this in the way that you can pass a

Re: [HELP] Barebox porting

2019-01-22 Thread Seraphim Dolbilov
How can I get an output of a shell command in hush shell? Backticks and $() cannot do not work :( --  Yours sincerely, Seraphim Dolbilov ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox

Re: [HELP] Barebox porting

2019-01-22 Thread Sascha Hauer
On Tue, Jan 22, 2019 at 05:07:23PM +0300, Seraphim Dolbilov wrote: > Hi, Sascha > > 22.01.2019, 09:33, "Sascha Hauer" : > > This only works when you want to add something to the environment for > > all boards. When you only want to change the environment for a single > > board then

Re: [HELP] Barebox porting

2019-01-22 Thread Seraphim Dolbilov
Hi, Sascha 22.01.2019, 09:33, "Sascha Hauer" : > This only works when you want to add something to the environment for > all boards. When you only want to change the environment for a single > board then defaultenv_append_directory() is the right choice. Thanks, did so! However, environment is

Re: [HELP] Barebox porting

2019-01-21 Thread Sascha Hauer
On Mon, Jan 21, 2019 at 05:35:03PM +0100, Sam Ravnborg wrote: > On Mon, Jan 21, 2019 at 04:12:32PM +0100, Sascha Hauer wrote: > > On Mon, Jan 21, 2019 at 03:34:49PM +0300, Seraphim Dolbilov wrote: > > > Hi friends, > > > > > > I need some help with barebox environment management. I've added > >

Re: [HELP] Barebox porting

2019-01-21 Thread Seraphim Dolbilov
21.01.2019, 19:35, "Sam Ravnborg" : > Or even better I think to add the path to: > DEFAULT_ENVIRONMENT_PATH Got that. However this option seems to be not so universal as if env is linked straight to binary image. --  Yours sincerely, Seraphim Dolbilov

Re: [HELP] Barebox porting

2019-01-21 Thread Sam Ravnborg
On Mon, Jan 21, 2019 at 04:12:32PM +0100, Sascha Hauer wrote: > On Mon, Jan 21, 2019 at 03:34:49PM +0300, Seraphim Dolbilov wrote: > > Hi friends, > > > > I need some help with barebox environment management. I've added env/config > > file > > to arch/arm/myboard/ directory, fixed Makefile with

Re: [HELP] Barebox porting

2019-01-21 Thread Seraphim Dolbilov
21.01.2019, 18:12, "Sascha Hauer" : > with bbenv-y it is only compiled it, but remains unused. You have to add > it using defaultenv_append_directory(). Well, it seems, I've solved this problem by adding path to my board's env to CONFIG_DEFAULT_ENVIRONMENT_PATH (without bbenv-y entry in

Re: [HELP] Barebox porting

2019-01-21 Thread Sascha Hauer
On Mon, Jan 21, 2019 at 03:34:49PM +0300, Seraphim Dolbilov wrote: > Hi friends, > > I need some help with barebox environment management. I've added env/config > file > to arch/arm/myboard/ directory, fixed Makefile with `bbenv-y += env` string, > but > this config file doesn't apply on

Re: [HELP] Barebox porting

2019-01-21 Thread Seraphim Dolbilov
Dear friends, Still cannot make my environment be compiled into barebox final image. Maybe I missed something? Which config parameters should be set to do this?.. --  Yours sincerely, Seraphim Dolbilov ___ barebox mailing list

Re: [HELP] Barebox porting

2019-01-21 Thread Seraphim Dolbilov
Hi friends, I need some help with barebox environment management. I've added env/config file to arch/arm/myboard/ directory, fixed Makefile with `bbenv-y += env` string, but this config file doesn't apply on barebox boots. What can be the reason for such a problem? -- Yours sincerely, Seraphim

Re: [HELP] Barebox porting

2019-01-18 Thread Seraphim Dolbilov
18.01.2019, 18:14, "Sascha Hauer" : > Note for device tree based boards you should turn off > CONFIG_CONSOLE_ACTIVATE_FIRST as the console will be activated by the > /chosen/stdout-path property. So I need to chose CONFIG_CONSOLE_ACTIVATE_NONE parameter? 18.01.2019, 18:14, "Sascha Hauer" :

Re: [HELP] Barebox porting

2019-01-18 Thread Sascha Hauer
Hi Seraphim, On Fri, Jan 18, 2019 at 06:01:28PM +0300, Seraphim Dolbilov wrote: > Dear friends, > I faced a strange problem with serial ports on my board. I have 4 imx-uart's > enabled with DT, > and barebox console is available on all of them even when: > - CONFIG_CONSOLE_ACTIVATE_FIRST is set

Re: [HELP] Barebox porting

2019-01-18 Thread Seraphim Dolbilov
Dear friends, I faced a strange problem with serial ports on my board. I have 4 imx-uart's enabled with DT, and barebox console is available on all of them even when: - CONFIG_CONSOLE_ACTIVATE_FIRST is set Y, - CONFIG_CONSOLE_ACTIVATE_ALL is set N - `chosen` section of my DTS contains

Re: [HELP] Barebox porting

2019-01-17 Thread Sascha Hauer
On Thu, Jan 17, 2019 at 05:26:18PM +0100, Sam Ravnborg wrote: > Hi Serapim > > > BTW, am I right to suppose that all functions in `obj-y` marked > > as `initcall` and `exitcall` are invoked in the beginning and in the > > end of barebox main code respectively? > Enabel initcall debug - then you

Re: [HELP] Barebox porting

2019-01-17 Thread Sam Ravnborg
Hi Serapim > BTW, am I right to suppose that all functions in `obj-y` marked > as `initcall` and `exitcall` are invoked in the beginning and in the > end of barebox main code respectively? Enabel initcall debug - then you can see when they are called. It is a very usefull debug tool. Use the .map

Re: [HELP] Barebox porting

2019-01-17 Thread Серафим Долбилов
17.01.2019, 16:28, "Sascha Hauer" : > This is what barebox does by default. Happy ya! Thanx :) > PBL is for PreBootLoader. Yes, it's a self extracting image. During > building of barebox a single barebox binary and one to many PBL images > are built. Each PBL image is for one specific board.

Re: [HELP] Barebox porting

2019-01-17 Thread Roland Hieber
On Thu, Jan 17, 2019 at 02:28:45PM +0100, Sascha Hauer wrote: > On Thu, Jan 17, 2019 at 03:44:22PM +0300, Серафим Долбилов wrote: > > Reading Barebox's source code I found that `examle.dts` (e.g.) becomes > > `example.dtb`, then `example.dtb.o`, and is finally linked into PBL, > > being "catched"

Re: [HELP] Barebox porting

2019-01-17 Thread Sascha Hauer
On Thu, Jan 17, 2019 at 03:44:22PM +0300, Серафим Долбилов wrote: > 17.01.2019, 10:59, "Sascha Hauer" : > > You can have any devicetree by adding it to arch/arm/dts/Makefile: > > > > pbl-dtb-$(CONFIG_MACH_FREESCALE_MX51_PDK) += imx51-babbage.dtb.o > > > > Then add a declaration for it (replace

Re: [HELP] Barebox porting

2019-01-17 Thread Серафим Долбилов
17.01.2019, 10:59, "Sascha Hauer" : > You can have any devicetree by adding it to arch/arm/dts/Makefile: > > pbl-dtb-$(CONFIG_MACH_FREESCALE_MX51_PDK) += imx51-babbage.dtb.o > > Then add a declaration for it (replace beginning of filename with > __dtb_, .dtb.o with _start and '-' with '_'): > >

Re: [HELP] Barebox porting

2019-01-17 Thread Sascha Hauer
On Wed, Jan 16, 2019 at 06:59:46PM +0300, Серафим Долбилов wrote: > Is there any another way to link DT to the image besides > imx*_barebox_entry(void *boarddata) functions? You can have any devicetree by adding it to arch/arm/dts/Makefile: pbl-dtb-$(CONFIG_MACH_FREESCALE_MX51_PDK) +=

Re: [HELP] Barebox porting

2019-01-16 Thread Antony Pavlov
On Wed, 16 Jan 2019 18:28:06 +0100 Sam Ravnborg wrote: Hi! > On Wed, Jan 16, 2019 at 06:14:03PM +0300, Серафим Долбилов wrote: > > > > A new portion of questions is ready:) > > 1. dlmalloc or tlsf - what are pros and cons of each of them? > > Looking at the history I could see that dlmalloc

Re: [HELP] Barebox porting

2019-01-16 Thread Sam Ravnborg
Hi Серафим On Wed, Jan 16, 2019 at 06:37:08PM +0300, Серафим Долбилов wrote: > Moreover, it seems that I need some reference about functions I can call from > the ENTRY_FUNCTION code... There is no such reference, but look at what other DT enabled board support packages do. And check if the

Re: [HELP] Barebox porting

2019-01-16 Thread Sam Ravnborg
Hi Серафим. On Wed, Jan 16, 2019 at 06:14:03PM +0300, Серафим Долбилов wrote: > > A new portion of questions is ready:) > 1. dlmalloc or tlsf - what are pros and cons of each of them? Looking at the history I could see that dlmalloc was present since barebox was forked from U-boot. So and old

Re: [HELP] Barebox porting

2019-01-16 Thread Серафим Долбилов
Is there any another way to link DT to the image besides imx*_barebox_entry(void *boarddata) functions? --  Regards, Seraphim Dolbilov +7 (977) 818-10-50 s.dl...@ya.ru ___ barebox mailing list barebox@lists.infradead.org

Re: [HELP] Barebox porting

2019-01-16 Thread Серафим Долбилов
Moreover, it seems that I need some reference about functions I can call from the ENTRY_FUNCTION code... --  Regards, Seraphim Dolbilov +7 (977) 818-10-50 s.dl...@ya.ru ___ barebox mailing list barebox@lists.infradead.org

Re: [HELP] Barebox porting

2019-01-16 Thread Серафим Долбилов
A new portion of questions is ready:) 1. dlmalloc or tlsf - what are pros and cons of each of them? 2. Does barebox apply IMX's pinctrl settings if they are present in DT? If yes, why do we need setup_uart() function in pbl code? --  С уважением, Долбилов Серафим +7 (977) 818-10-50

Re: [HELP] Barebox porting

2019-01-09 Thread Sascha Hauer
Hi, On Wed, Jan 09, 2019 at 03:40:37PM +0300, Серафим Долбилов wrote: > Hi, I'm trying to add my own custom board support to barebox. It's based on > i.MX6ULL CPU. > So, I have the following questions: > > * Why does the config parameter IMX_MULTI_BOARDS exist? Why such > boards as EUKREA

[HELP] Barebox porting

2019-01-09 Thread Серафим Долбилов
Hi, I'm trying to add my own custom board support to barebox. It's based on i.MX6ULL CPU. So, I have the following questions: * Why does the config parameter IMX_MULTI_BOARDS exist? Why such boards as EUKREA CPUIMX35 and i.MX53 SMD are isolated from the others? So, if I add custom board, which