From: robert.marshall@codethink.co.uk (Robert Marshall)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] B@D support Renesas iwg20m board - issue
Date: Thu, 05 Oct 2017 08:51:06 +0100 [thread overview]
Message-ID: <87mv568239.fsf@ctlt579.codethink.co.uk> (raw)
In-Reply-To: <59CB7424.3050202@codethink.co.uk> (Agustin Benito Bethencourt's message of "Wed, 27 Sep 2017 11:49:24 +0200")
Morning!
Agustin Benito Bethencourt <agustin.benito@codethink.co.uk> writes:
> Hi,
>
> On 27/09/17 07:35, Daniel Sangorrin wrote:
>> Agustin, Robert:
>>
>>> -----Original Message-----
>>> From: Agustin Benito Bethencourt [mailto:agustin.benito at codethink.co.uk]
>>> Sent: Tuesday, September 26, 2017 7:34 PM
>>> To: Daniel Sangorrin; 'cip dev'
>>> Cc: 'Binh Thanh. Nguyen'; 'Chris Paterson'; 'Robert Marshall'; 'O365-Toru Oishi'
>>> Subject: Re: [cip-dev] B at D support Renesas iwg20m board - issue
>>>
>>> Hi,
>>>
>>> On 26/09/17 11:49, Daniel Sangorrin wrote:
>>>> Hi Binh, Robert, Everyone
>>>>
>>>> I have Project-X for iwg20m working with LAVA 2017.7 (boot test and a simple uname test so far).
>>>> # I will send the patches another day.
>>>>
>>>> Robert: do you have plans to update to 2017.9?
>>>
>>> We will not before ELCE. We will concentrate on properly releasing what
>>> we currently have for the event.
>>
>> Alright, then I will prepare the demo for 2017.7.
>>
>> Robert: until now I was using lava-docker, is the 2017.7 version fully working now?
>> What branch should I use?
>
> Robert is on vacation until mid next week.
>
> From what I see in the project journal and the repo, there is a merge
> request approved for lava update and local initramfs.
Yes, the initramfs and lava to 2017-7 updates are in master, lava is
working fine, remaining issues are with a recent kernelci update to which the comment
below belongs
Robert
>
> Hi comment is: "B at D still hangs at the listening on port 8888 in
> install_backend.sh and needs a manual vm restart. But once that's done
> the rest of the kernelci provisioning works. "
>
> So I assume it is almost ready for the release, which will take place
> right after he comes back.
>
> Check:
> https://gitlab.com/rajm/board-at-desk-single-dev/tree/fix-new-kernelci
>
>>
>> Another question:
>> Is it possible to upload artifacts (CIP Core's ramdisk, uImage, devicetree etc) to
>> the AWS S3 storage so that we can share the same binaries for demos etc?
>
> Yes it is. I will add you as user so you can upload them.
>
>>
>> Thanks,
>> Daniel
>>
>>>>> -----Original Message-----
>>>>> From: Binh Thanh. Nguyen [mailto:binh.nguyen.uw at rvc.renesas.com]
>>>>> Sent: Wednesday, September 20, 2017 6:30 PM
>>>>> To: Chris Paterson; Daniel Sangorrin; 'cip dev'
>>>>> Cc: O365-Toru Oishi
>>>>> Subject: RE: [cip-dev] B at D support Renesas iwg20m board - issue
>>>>>
>>>>> Hi Daniel,
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Chris Paterson [mailto:Chris.Paterson2 at renesas.com]
>>>>>> Sent: Wednesday, September 20, 2017 3:29 PM
>>>>>> To: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>; Binh Thanh. Nguyen
>>>>>> <binh.nguyen.uw@rvc.renesas.com>; 'cip dev' <cip-dev@lists.cip-
>>>>>> project.org>
>>>>>> Cc: O365-Toru Oishi <toru.oishi.zj@renesas.com>
>>>>>> Subject: RE: [cip-dev] B at D support Renesas iwg20m board - issue
>>>>>>
>>>>>> Hello Daniel,
>>>>>>
>>>>>>> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-
>>>>>>> bounces at lists.cip-project.org] On Behalf Of Daniel Sangorrin
>>>>>>> Sent: 20 September 2017 08:14
>>>>>>>
>>>>>>> Hi Binh,
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: cip-dev-bounces at lists.cip-project.org
>>>>>>>> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Daniel
>>>>>>>> Sangorrin
>>>>>>>> Sent: Wednesday, September 20, 2017 3:40 PM
>>>>>>>> To: 'Binh Thanh. Nguyen'; 'cip dev'
>>>>>>>> Cc: 'O365-Toru Oishi'
>>>>>>>> Subject: Re: [cip-dev] B at D support Renesas iwg20m board - issue
>>>>>>>>
>>>>>>>> Hi Binh,
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Binh Thanh. Nguyen [mailto:binh.nguyen.uw at rvc.renesas.com]
>>>>>>>>> Sent: Friday, September 15, 2017 8:46 PM
>>>>>>>>> To: Daniel Sangorrin; 'cip dev'
>>>>>>>>> Cc: O365-Toru Oishi
>>>>>>>>> Subject: RE: [cip-dev] B at D support Renesas iwg20m board - issue
>>>>>>>>>
>>>>>>>>> Hello Daniel,
>>>>>>>>>
>>>>>>>>> Sorry for late reply. I got few days off for some reasons.
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp]
>>>>>>>>>> Sent: Tuesday, September 12, 2017 8:36 AM
>>>>>>>>>> To: Binh Thanh. Nguyen <binh.nguyen.uw@rvc.renesas.com>; 'cip
>>>>>> dev'
>>>>>>>>>> <cip- dev@lists.cip-project.org>
>>>>>>>>>> Cc: O365-Toru Oishi <toru.oishi.zj@renesas.com>
>>>>>>>>>> Subject: RE: [cip-dev] B at D support Renesas iwg20m board - issue
>>>>>>>>>>
>>>>>>>>>> Hi Binh,
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: Binh Thanh. Nguyen
>>>>>>> [mailto:binh.nguyen.uw at rvc.renesas.com]
>>>>>>>>>>> Sent: Monday, September 11, 2017 8:00 PM
>>>>>>>>>>>> Any updates on this topic?
>>>>>>>>>>> I have no update. I was busy with other tasks with high
>>>>>>>>>>> priority. I will
>>>>>>>>>> manage to back to this task from next week.
>>>>>>>>>>> I will let you know if there is any update.
>>>>>>>>>>
>>>>>>>>>> OK, I'm working on it now. There were several problems with your
>>>>>>>>>> patches and we are upgrading to LAVA 2017.7.
>>>>>>>>>> Before you start please let me know so we don't overlap.
>>>>>>>>>
>>>>>>>>> It is great to know that. Thank you for your work on Renesas board.
>>>>>>>>> I will back to this task next week, if possible please let me know
>>>>>>>>> your
>>>>>>> status, anything need my support please let me know.
>>>>>>>>
>>>>>>>> I am preparing the board to boot from the network (tftp), both the
>>>>>>>> kernel
>>>>>>> and the Project-X file system (a ramdisk).
>>>>>>>> Currently the kernel boots fine, but no login console appears.
>>>>>>>> # Note, the same file system installed on the SD Card has no
>>>>>>>> problems
>>>>>>>>
>>>>>>>> This are a few things I had to modify:
>>>>>>>> - kernel configuration
>>>>>>>> CONFIG_BLK_DEV_RAM=y
>>>>>>>> CONFIG_BLK_DEV_RAM_COUNT=8
>>>>>>>> CONFIG_BLK_DEV_RAM_SIZE=102400
>>>>>>>>
>>>>>>>> - ramdisk
>>>>>>>> # mkdir ramdisk
>>>>>>>> # cd ramdisk/
>>>>>>>> # tar xvf ../iwg20m/core-image-minimal-iwg20m.tar.gz
>>>>>>>> # ln -s /sbin/init .
>>>>>>>> # find . | cpio --create --format='newc' > /tmp/newinitrd
>>>>>>>> # gzip /tmp/newinitrd
>>>>>>>> # mkimage -A arm -T ramdisk -C gzip -d /tmp/newinitrd.gz uRamdisk
>>>>>>>> # mv uRamdisk /var/lib/tftpboot/
>>>>>>>>
>>>>>>>> - u-boot settings
>>>>>>>> iWave-G20M > setenv ramdisk_addr 0x41000000
>>>>>>>> iWave-G20M > setenv ramdisk_file uRamdisk
>>>>>>>> iWave-G20M > setenv bootm_low 0x44000000
>>>>>>>> iWave-G20M > setenv bootm_size 0x3000000
>>>>>>>> iWave-G20M > setenv bootargs_ramdisk setenv bootargs
>>>>>>> ${bootargs_base} root=/dev/ram rootwait rw
>>>>>>>> iWave-G20M > setenv bootcmd_tftpboot 'run bootargs_ramdisk;run
>>>>>>>> fdt_check;tftpboot ${loadaddr} ${kernel};tftpboot ${fdt_addr}
>>>>>>> ${fdt_file};tftpboot ${ramdisk_addr} ${ramdisk_file};bootm ${loadaddr}
>>>>>>> ${ramdisk_addr} ${fdt_addr}'
>>>>>>>> iWave-G20M > saveenv
>>>>>>>> iWave-G20M > run bootcmd_tftpboot
>>>>>>>>
>>>>>>>> I send you the bootlog attached as well.
>>>>>>>>
>>>>>>>> If you have any hint about the possible solution please let me know.
>>>>>>>
>>>>>>> OK, I solved it.
>>>>>>> It seems that the dev folder wasn't being populated properly on the
>>>>>>> ramdisk so I made it work with mdev.
>>>>>>>
>>>>>>> Now that I have a network deployment environment I will try running a
>>>>>>> test on LAVA and see if it works this time.
>>>>>
>>>>> It is great that you could fix the issue.
>>>>> Hope that your test run well. if you meet other issue and need my support, please let me know.
>>>>>
>>>>>>
>>>>>> I'm glad that you managed to resolve the problem. Thank you for the update.
>>>>>>
>>>>>> Kind regards, Chris
>>>>>
>>>>> Best regards,
>>>>> Binh Nguyen
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> cip-dev mailing list
>>>> cip-dev at lists.cip-project.org
>>>> https://lists.cip-project.org/mailman/listinfo/cip-dev
>>>>
>>>
>>> --
>>> Agustin Benito Bethencourt
>>> Principal Consultant - FOSS at Codethink
>>> agustin.benito at codethink.co.uk
>>
>>
>>
>>
next prev parent reply other threads:[~2017-10-05 7:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 12:22 [cip-dev] B@D support Renesas iwg20m board - issue Binh Thanh. Nguyen
2017-08-07 13:13 ` Robert Marshall
2017-08-10 13:53 ` Binh Thanh. Nguyen
2017-09-11 5:33 ` Daniel Sangorrin
2017-09-11 10:59 ` Binh Thanh. Nguyen
2017-09-12 1:36 ` Daniel Sangorrin
2017-09-15 11:46 ` Binh Thanh. Nguyen
2017-09-20 6:39 ` Daniel Sangorrin
2017-09-20 7:13 ` Daniel Sangorrin
2017-09-20 8:29 ` Chris Paterson
2017-09-20 9:30 ` Binh Thanh. Nguyen
2017-09-26 9:49 ` Daniel Sangorrin
2017-09-26 10:33 ` Agustin Benito Bethencourt
2017-09-27 5:35 ` Daniel Sangorrin
2017-09-27 9:49 ` Agustin Benito Bethencourt
2017-10-05 7:51 ` Robert Marshall [this message]
2017-10-02 11:14 ` Agustin Benito Bethencourt
2017-09-27 3:28 ` Binh Thanh. Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv568239.fsf@ctlt579.codethink.co.uk \
--to=robert.marshall@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox